AccessControlTestCase

[kconner]

The above test case is currently failing within the kernel module when executed under maven.

The reason for the failure is the name of the directory containing the test classes. :)

There is a security policy in effect for the tests, TestsPolicyPlugin, which is responsible for assigning the permissions based on the code source. This policy class allows the permissions to be configured via a property file (not used in this case) if it believes that the code source represents a test location.

How does it determine whether the code source represents tests? Simple, it looks for 'tests' or '-test.jar' in the name of the code source (last directory/file only). If the code source represents a test location then it is given a specific set of permissions plus the ones specified in the property file. If it does not represent a test location then it defaults to all permissions.

If this is run in the current eclipse setup then it works, the final directory is tests-classes (almost certainly a typo of mine). If this is run via maven then it fails as the final directory is test-classes. :(

[adrian.brock]

You solved the problem for the eclipse build
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034519#4034519
but not for the maven build.

[kconner]

ROFL, I forgot about that entry.

Of course you were only complaining about the test failing within eclipse at the time ;)

I will also fix it for the main build :)

[adrian.brock]

I don't suppose you know why I needed the HACK mentioned on here:
http://jira.jboss.com/jira/browse/JBMICROCONT-185
to make some tests work with Maven?

They work fine in eclipse.

I tried debugging it, but obviously the JDK source doesn't match the binary.
If you use the URL class from src.zip in the JDK then I don't need this hack. :-)