View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-aop-testsuite?log=log20070217002915

TESTS FAILED
Ant Error Message: /services/cruisecontrol/work/scripts/build-aop-head-testsuite.xml:91: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.
Date of build: 02/17/2007 00:29:15
Time to build: 51 minutes 28 seconds
Last changed: 02/16/2007 08:14:59
Last log entry: [JBAOP-356] Ability to attach a .aop deployment to a particular scoped classloader.Register ScopedClassLoaderDomains per LoaderRepository instead of per (scoped) classloader.When adding PER_INSTANCE, PER_JOINPOINT and PER_CLASS AspectDefinitions to the advisor register the Advisor with the AspectDefinition so that it can be cleaned up when we undeploy the AspectDefinition, otherwise the wrong (old) classloader is used when we redeploy the .aop file we are attaching to a deployment

Unit Tests: (2495) Total Errors and Failures: (20)
testDeclaredMethodHashing org.jboss.test.aop.methodhashing.MethodHashingTestCase(jdk14)
testMethodHashing org.jboss.test.aop.methodhashing.MethodHashingTestCase(jdk14)
testWovenNamedDomains org.jboss.test.aop.nameddomain.NamedDomainTestCase(non-optimized-precompiled-tests-jdk14)
testProxiedNamedDomains org.jboss.test.aop.nameddomain.NamedDomainTestCase(non-optimized-precompiled-tests-jdk14)
testNativeMethod org.jboss.test.aop.regression.jbaop279native.NativeMethodTestCase(bootclasspath-genadvisor-tests-jdk14)
testNativeMethod org.jboss.test.aop.regression.jbaop279native.NativeMethodTestCase(bootclasspath-tests-jdk14)
testNativeMethod org.jboss.test.aop.regression.jbaop279native.NativeMethodTestCase(javaagent-genadvisor-tests)
testNativeMethod org.jboss.test.aop.regression.jbaop279native.NativeMethodTestCase(javaagent-tests)
testNativeMethod org.jboss.test.aop.regression.jbaop279native.NativeMethodTestCase(non-optimized-precompiled-tests-jdk14)
testNativeMethod org.jboss.test.aop.regression.jbaop279native.NativeMethodTestCase(non-optimized-precompiled-tests)
testNativeMethod org.jboss.test.aop.regression.jbaop279native.NativeMethodTestCase(precompiled-genadvisor-tests-jdk14)
testNativeMethod org.jboss.test.aop.regression.jbaop279native.NativeMethodTestCase(precompiled-genadvisor-tests)
testNativeMethod org.jboss.test.aop.regression.jbaop279native.NativeMethodTestCase(precompiled-tests-jdk14)
testNativeMethod org.jboss.test.aop.regression.jbaop279native.NativeMethodTestCase(precompiled-tests)
testProxy org.jboss.test.aop.serialization.simple.SimpleSerialiizationTestCase(non-optimized-precompiled-tests-jdk14)
testProxy org.jboss.test.aop.serialization.simple.SimpleSerialiizationTestCase(precompiled-genadvisor-tests-jdk14)
testProxy org.jboss.test.aop.serialization.simple.SimpleSerialiizationTestCase(precompiled-tests-jdk14)
testPrecedence org.jboss.test.aop.jdk15annotated.AnnotatedTestCase(non-optimized-precompiled-tests-jdk14)
testPrecedence org.jboss.test.aop.jdk15annotated.AnnotatedTestCase(precompiled-genadvisor-tests-jdk14)
testPrecedence org.jboss.test.aop.jdk15annotated.AnnotatedTestCase(precompiled-tests-jdk14)

Modifications since last build: (first 50 of 5)
60587 modified kabir.khan@jboss.com //projects/aop/trunk/aop/src/main/org/jboss/aop/Advisor.java [JBAOP-356] Ability to attach a .aop deployment to a particular scoped classloader.Register ScopedClassLoaderDomains per LoaderRepository instead of per (scoped) classloader.When adding PER_INSTANCE, PER_JOINPOINT and PER_CLASS AspectDefinitions to the advisor register the Advisor with the AspectDefinition so that it can be cleaned up when we undeploy the AspectDefinition, otherwise the wrong (old) classloader is used when we redeploy the .aop file we are attaching to a deployment
60587 modified kabir.khan@jboss.com //projects/aop/trunk/aop/src/main/org/jboss/aop/AspectXmlLoader.java [JBAOP-356] Ability to attach a .aop deployment to a particular scoped classloader.Register ScopedClassLoaderDomains per LoaderRepository instead of per (scoped) classloader.When adding PER_INSTANCE, PER_JOINPOINT and PER_CLASS AspectDefinitions to the advisor register the Advisor with the AspectDefinition so that it can be cleaned up when we undeploy the AspectDefinition, otherwise the wrong (old) classloader is used when we redeploy the .aop file we are attaching to a deployment
60587 modified kabir.khan@jboss.com //projects/aop/trunk/aop/src/main/org/jboss/aop/classpool/AOPScopedClassLoaderHelper.java [JBAOP-356] Ability to attach a .aop deployment to a particular scoped classloader.Register ScopedClassLoaderDomains per LoaderRepository instead of per (scoped) classloader.When adding PER_INSTANCE, PER_JOINPOINT and PER_CLASS AspectDefinitions to the advisor register the Advisor with the AspectDefinition so that it can be cleaned up when we undeploy the AspectDefinition, otherwise the wrong (old) classloader is used when we redeploy the .aop file we are attaching to a deployment
60587 modified kabir.khan@jboss.com //projects/aop/trunk/aop/src/main/org/jboss/aop/AspectManager.java [JBAOP-356] Ability to attach a .aop deployment to a particular scoped classloader.Register ScopedClassLoaderDomains per LoaderRepository instead of per (scoped) classloader.When adding PER_INSTANCE, PER_JOINPOINT and PER_CLASS AspectDefinitions to the advisor register the Advisor with the AspectDefinition so that it can be cleaned up when we undeploy the AspectDefinition, otherwise the wrong (old) classloader is used when we redeploy the .aop file we are attaching to a deployment
60587 modified kabir.khan@jboss.com //projects/aop/trunk/aop/src/main/org/jboss/aop/advice/AspectDefinition.java [JBAOP-356] Ability to attach a .aop deployment to a particular scoped classloader.Register ScopedClassLoaderDomains per LoaderRepository instead of per (scoped) classloader.When adding PER_INSTANCE, PER_JOINPOINT and PER_CLASS AspectDefinitions to the advisor register the Advisor with the AspectDefinition so that it can be cleaned up when we undeploy the AspectDefinition, otherwise the wrong (old) classloader is used when we redeploy the .aop file we are attaching to a deployment

Modifications since last build: (first 50 of 5)
60587	modified	kabir.khan@jboss.com	//projects/aop/trunk/aop/src/main/org/jboss/aop/Advisor.java	[JBAOP-356] Ability to attach a .aop deployment to a particular scoped classloader.Register ScopedClassLoaderDomains per LoaderRepository instead of per (scoped) classloader.When adding PER_INSTANCE, PER_JOINPOINT and PER_CLASS AspectDefinitions to the advisor register the Advisor with the AspectDefinition so that it can be cleaned up when we undeploy the AspectDefinition, otherwise the wrong (old) classloader is used when we redeploy the .aop file we are attaching to a deployment
60587	modified	kabir.khan@jboss.com	//projects/aop/trunk/aop/src/main/org/jboss/aop/AspectXmlLoader.java	[JBAOP-356] Ability to attach a .aop deployment to a particular scoped classloader.Register ScopedClassLoaderDomains per LoaderRepository instead of per (scoped) classloader.When adding PER_INSTANCE, PER_JOINPOINT and PER_CLASS AspectDefinitions to the advisor register the Advisor with the AspectDefinition so that it can be cleaned up when we undeploy the AspectDefinition, otherwise the wrong (old) classloader is used when we redeploy the .aop file we are attaching to a deployment
60587	modified	kabir.khan@jboss.com	//projects/aop/trunk/aop/src/main/org/jboss/aop/classpool/AOPScopedClassLoaderHelper.java	[JBAOP-356] Ability to attach a .aop deployment to a particular scoped classloader.Register ScopedClassLoaderDomains per LoaderRepository instead of per (scoped) classloader.When adding PER_INSTANCE, PER_JOINPOINT and PER_CLASS AspectDefinitions to the advisor register the Advisor with the AspectDefinition so that it can be cleaned up when we undeploy the AspectDefinition, otherwise the wrong (old) classloader is used when we redeploy the .aop file we are attaching to a deployment
60587	modified	kabir.khan@jboss.com	//projects/aop/trunk/aop/src/main/org/jboss/aop/AspectManager.java	[JBAOP-356] Ability to attach a .aop deployment to a particular scoped classloader.Register ScopedClassLoaderDomains per LoaderRepository instead of per (scoped) classloader.When adding PER_INSTANCE, PER_JOINPOINT and PER_CLASS AspectDefinitions to the advisor register the Advisor with the AspectDefinition so that it can be cleaned up when we undeploy the AspectDefinition, otherwise the wrong (old) classloader is used when we redeploy the .aop file we are attaching to a deployment
60587	modified	kabir.khan@jboss.com	//projects/aop/trunk/aop/src/main/org/jboss/aop/advice/AspectDefinition.java	[JBAOP-356] Ability to attach a .aop deployment to a particular scoped classloader.Register ScopedClassLoaderDomains per LoaderRepository instead of per (scoped) classloader.When adding PER_INSTANCE, PER_JOINPOINT and PER_CLASS AspectDefinitions to the advisor register the Advisor with the AspectDefinition so that it can be cleaned up when we undeploy the AspectDefinition, otherwise the wrong (old) classloader is used when we redeploy the .aop file we are attaching to a deployment