BUILD FAILED

Ant Error Message: /services/cruisecontrol/work/scripts/build-microcontainer-head-testsuite.xml:61: Exit code: 1 See build.log in Build Artifacts for details.

Date of build: 07/25/2007 01:10:49

Time to build: 2 minutes 54 seconds

Last changed: 07/24/2007 13:48:23

Last log entry: Include the cause in the RuntimeException

Unit Tests: (0)  Total Errors and Failures: (0)

Modifications since last build:  (first 50 of 46)
64258	modified	genman	//projects/microcontainer/trunk/kernel/src/main/org/jboss/kernel/plugins/metadata/basic/BasicKernelMetaDataRepository.java	Include the cause in the RuntimeException
64256	added	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/inject/test/AbstractManualInjectTest.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/deployment/test/ScopingShutdownTestCase.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/deployment/test/ScopingTestDelegate.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/main/org/jboss/beans/metadata/plugins/AbstractFeatureMetaData.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/inject/test/SimpleCallbackTestCase.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/deployment/test/IgnoredAnnotatedLifecycleTestCase.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	added	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/deployment/test/AbstractManualDeploymentTest.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/deployment/test/IgnoredLifecycleTestCase.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/inject/test/CardinalityCallbackTestCase.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/main/org/jboss/kernel/plugins/deployment/AbstractKernelDeployer.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/inject/test/BadCardinalityCallbackTestCase.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	deleted	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/main/org/jboss/test/kernel/junit/MicrocontainerShutdownTestDelegate.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	deleted	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/main/org/jboss/test/kernel/junit/ManualMicrocontainerTestDelegate.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/config/support/UnmodifiableGetterBean.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/deployment/test/MixedLifecycleTestCase.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/main/org/jboss/test/kernel/junit/MicrocontainerTestDelegate.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/main/org/jboss/beans/metadata/plugins/AbstractTypeMetaData.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/deployment/xml/test/AbstractXMLTest.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/inject/test/InjectionValueCallbackTestCase.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	deleted	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/main/org/jboss/test/kernel/junit/ManualMicrocontainerTest.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/inject/test/ContextualInjectionAdapter.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	deleted	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/main/org/jboss/test/kernel/junit/ModeMicrocontainerTestDelegate.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/main/org/jboss/test/kernel/junit/MicrocontainerTest.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64256	modified	adrian@jboss.org	//projects/microcontainer/trunk/kernel/src/tests/org/jboss/test/kernel/deployment/test/AnnotatedLifecycleTestCase.java	Cleanup the tests again!1) MicrocontainerTest is not a part of the testsuite it is a part of theMicrocontainer that can be consumed by others. There should be onlyone MicrocontainerTest class, extends MicrocontainerTest should be in thetestsuite.2) The MicrocontainerTestDelegate is the place to parameterize testsnot subclassing. All relevant features should be in this class.3) You shouldn't have to access the delegate to do reasonable operations.4) Tests should not fix problems in the main code by subclassing.5) All tests should be run with a security manager enabled. The easiset wayto do this is to always extend an Abstract class specific to thosetests that enable the security manager on the test delegate.This Abstract class is also a good place to put common helpers for related tests.
64255	added	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/tests/org/jboss/test/classloader/junit/support/Support.java	Add an abstract isolated classloader test support classthat can be used to control classloading inside a unit test.
64255	added	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/tests/org/jboss/test/classloader/junit/notsupport/NotSupport.java	Add an abstract isolated classloader test support classthat can be used to control classloading inside a unit test.
64255	modified	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/main/org/jboss/classloader/test/support/MockClassLoaderPolicy.java	Add an abstract isolated classloader test support classthat can be used to control classloading inside a unit test.
64255	added	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/tests/org/jboss/test/classloader/junit/support	Add an abstract isolated classloader test support classthat can be used to control classloading inside a unit test.
64255	added	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/tests/org/jboss/test/classloader/junit/test/IsolatedClassLoaderUnitTestCase.java	Add an abstract isolated classloader test support classthat can be used to control classloading inside a unit test.
64255	added	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/tests/org/jboss/test/classloader/junit/notsupport	Add an abstract isolated classloader test support classthat can be used to control classloading inside a unit test.
64255	added	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/tests/org/jboss/test/classloader/junit/test	Add an abstract isolated classloader test support classthat can be used to control classloading inside a unit test.
64255	added	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/tests/org/jboss/test/classloader/junit	Add an abstract isolated classloader test support classthat can be used to control classloading inside a unit test.
64255	modified	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/tests/org/jboss/test/classloader/domain/test/ParentPolicyUnitTestCase.java	Add an abstract isolated classloader test support classthat can be used to control classloading inside a unit test.
64255	added	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/tests/org/jboss/test/classloader/junit/JUnitTestSuite.java	Add an abstract isolated classloader test support classthat can be used to control classloading inside a unit test.
64255	modified	adrian@jboss.org	//projects/microcontainer/trunk/classloader/pom.xml	Add an abstract isolated classloader test support classthat can be used to control classloading inside a unit test.
64255	added	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/main/org/jboss/classloader/test/support/IsolatedClassLoaderTest.java	Add an abstract isolated classloader test support classthat can be used to control classloading inside a unit test.
64255	modified	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/tests/org/jboss/test/classloader/ClassLoaderAllTestSuite.java	Add an abstract isolated classloader test support classthat can be used to control classloading inside a unit test.
64255	modified	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/tests/org/jboss/test/classloader/AbstractClassLoaderTest.java	Add an abstract isolated classloader test support classthat can be used to control classloading inside a unit test.
64254	modified	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/main/org/jboss/classloader/plugins/jdk/AbstractJDKChecker.java	Allow tests to say they are not part of the JDK even though theyare outside the classloading system.
64253	modified	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/main/org/jboss/classloader/spi/filter/PackageClassFilter.java	Add an easy way for the package class filter to include standard java classesas well.
64252	modified	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/main/org/jboss/classloader/spi/base/BaseClassLoaderSystem.java	Add support for Translator - used by Legacy AOP tests in JBossAS testsuite
64252	modified	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/main/org/jboss/classloader/spi/base/BaseClassLoaderDomain.java	Add support for Translator - used by Legacy AOP tests in JBossAS testsuite
64252	modified	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/main/org/jboss/classloader/spi/ClassLoaderSystem.java	Add support for Translator - used by Legacy AOP tests in JBossAS testsuite
64252	modified	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/main/org/jboss/classloader/spi/base/BaseClassLoader.java	Add support for Translator - used by Legacy AOP tests in JBossAS testsuite
64252	modified	adrian@jboss.org	//projects/microcontainer/trunk/classloader/src/main/org/jboss/classloader/spi/base/BaseClassLoaderPolicy.java	Add support for Translator - used by Legacy AOP tests in JBossAS testsuite