View results here -> http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite-14?log=log20061110113401

BUILD FAILED
Ant Error Message: /services/cruisecontrol/work/scripts/build-microcontainer-head-testsuite.xml:70: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-microcontainer-head-testsuite.xml:87: exec returned: 1
Date of build: 11/10/2006 11:34:01
Time to build: 9 minutes 24 seconds
Last changed: 11/10/2006 05:41:12
Last log entry: A JNDI binding aspect that creates bindings on interception of the kernel setKernelControllerContext callback, and removes them on any other method. The expectation is that this is applied to the org.jboss.kernel.spi.dependency.KernelControllerContextAware interface so that unbinding occurs on the unsetKernelControllerContext method.

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

 Modifications since last build:  (first 50 of 25)
58245addedscott.stark@jboss.org//projects/microcontainer/trunk/aop-mc-int/src/tests/org/jboss/test/microcontainer/support/jndi/MockJndiProvider.javaA JNDI binding aspect that creates bindings on interception of the kernel setKernelControllerContext callback, and removes them on any other method. The expectation is that this is applied to the org.jboss.kernel.spi.dependency.KernelControllerContextAware interface so that unbinding occurs on the unsetKernelControllerContext method.
58245addedscott.stark@jboss.org//projects/microcontainer/trunk/aop-mc-int/src/tests/org/jboss/test/microcontainer/test/JndiDecoratedTestCase.javaA JNDI binding aspect that creates bindings on interception of the kernel setKernelControllerContext callback, and removes them on any other method. The expectation is that this is applied to the org.jboss.kernel.spi.dependency.KernelControllerContextAware interface so that unbinding occurs on the unsetKernelControllerContext method.
58245addedscott.stark@jboss.org//projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/aspects/jndi/JndiIntroduction.javaA JNDI binding aspect that creates bindings on interception of the kernel setKernelControllerContext callback, and removes them on any other method. The expectation is that this is applied to the org.jboss.kernel.spi.dependency.KernelControllerContextAware interface so that unbinding occurs on the unsetKernelControllerContext method.
58245addedscott.stark@jboss.org//projects/microcontainer/trunk/aop-mc-int/src/tests/org/jboss/test/microcontainer/support/jndi/SimpleBean.javaA JNDI binding aspect that creates bindings on interception of the kernel setKernelControllerContext callback, and removes them on any other method. The expectation is that this is applied to the org.jboss.kernel.spi.dependency.KernelControllerContextAware interface so that unbinding occurs on the unsetKernelControllerContext method.
58245addedscott.stark@jboss.org//projects/microcontainer/trunk/aop-mc-int/src/tests/org/jboss/test/microcontainer/support/jndi/SimpleBeanAnnotatedImpl.javaA JNDI binding aspect that creates bindings on interception of the kernel setKernelControllerContext callback, and removes them on any other method. The expectation is that this is applied to the org.jboss.kernel.spi.dependency.KernelControllerContextAware interface so that unbinding occurs on the unsetKernelControllerContext method.
58245addedscott.stark@jboss.org//projects/microcontainer/trunk/aop-mc-int/src/tests/org/jboss/test/microcontainer/support/jndiA JNDI binding aspect that creates bindings on interception of the kernel setKernelControllerContext callback, and removes them on any other method. The expectation is that this is applied to the org.jboss.kernel.spi.dependency.KernelControllerContextAware interface so that unbinding occurs on the unsetKernelControllerContext method.
58245addedscott.stark@jboss.org//projects/microcontainer/trunk/aop-mc-int/src/tests/org/jboss/test/microcontainer/support/jndi/MockInitialContextFactory.javaA JNDI binding aspect that creates bindings on interception of the kernel setKernelControllerContext callback, and removes them on any other method. The expectation is that this is applied to the org.jboss.kernel.spi.dependency.KernelControllerContextAware interface so that unbinding occurs on the unsetKernelControllerContext method.
58245modifiedscott.stark@jboss.org//projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/junit/AOPMicrocontainerTestDelegate.javaA JNDI binding aspect that creates bindings on interception of the kernel setKernelControllerContext callback, and removes them on any other method. The expectation is that this is applied to the org.jboss.kernel.spi.dependency.KernelControllerContextAware interface so that unbinding occurs on the unsetKernelControllerContext method.
58245addedscott.stark@jboss.org//projects/microcontainer/trunk/aop-mc-int/src/resources/tests/org/jboss/test/microcontainer/test/JndiDecoratedTestCase.xmlA JNDI binding aspect that creates bindings on interception of the kernel setKernelControllerContext callback, and removes them on any other method. The expectation is that this is applied to the org.jboss.kernel.spi.dependency.KernelControllerContextAware interface so that unbinding occurs on the unsetKernelControllerContext method.
58245addedscott.stark@jboss.org//projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/aspects/jndi/JndiBinding.javaA JNDI binding aspect that creates bindings on interception of the kernel setKernelControllerContext callback, and removes them on any other method. The expectation is that this is applied to the org.jboss.kernel.spi.dependency.KernelControllerContextAware interface so that unbinding occurs on the unsetKernelControllerContext method.
58245addedscott.stark@jboss.org//projects/microcontainer/trunk/aop-mc-int/src/tests/org/jboss/test/microcontainer/support/jndi/MockNameParser.javaA JNDI binding aspect that creates bindings on interception of the kernel setKernelControllerContext callback, and removes them on any other method. The expectation is that this is applied to the org.jboss.kernel.spi.dependency.KernelControllerContextAware interface so that unbinding occurs on the unsetKernelControllerContext method.
58245addedscott.stark@jboss.org//projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/aspects/jndiA JNDI binding aspect that creates bindings on interception of the kernel setKernelControllerContext callback, and removes them on any other method. The expectation is that this is applied to the org.jboss.kernel.spi.dependency.KernelControllerContextAware interface so that unbinding occurs on the unsetKernelControllerContext method.
58245addedscott.stark@jboss.org//projects/microcontainer/trunk/aop-mc-int/src/tests/org/jboss/test/microcontainer/support/jndi/ISimpleBean.javaA JNDI binding aspect that creates bindings on interception of the kernel setKernelControllerContext callback, and removes them on any other method. The expectation is that this is applied to the org.jboss.kernel.spi.dependency.KernelControllerContextAware interface so that unbinding occurs on the unsetKernelControllerContext method.
58238modifiedkabir.khan@jboss.com//projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/integration/AOPDependencyBuilder.javaFixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names"
58238modifiedkabir.khan@jboss.com//projects/microcontainer/trunk/container/src/main/org/jboss/repository/spi/MetaDataContextFactory.javaFixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names"
58238addedkabir.khan@jboss.com//projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/integration/AOPMetaDataContextFactoryDelegate.javaFixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names"
58238addedkabir.khan@jboss.com//projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/integration/AOPDeployedChecker.javaFixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names"
58238modifiedkabir.khan@jboss.com//projects/microcontainer/trunk/kernel/src/main/org/jboss/kernel/plugins/dependency/DescribeAction.javaFixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names"
58238modifiedkabir.khan@jboss.com//projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/integration/AOPMetaDataContextFactory.javaFixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names"
58238modifiedkabir.khan@jboss.com//projects/microcontainer/trunk/aop-mc-int/build.xmlFixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names"
58238modifiedkabir.khan@jboss.com//projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/integration/AOPConstructorJoinpoint.javaFixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names"
58238addedkabir.khan@jboss.com//projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/integration/AOPDependencyBuilderDelegate.javaFixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names"
58238modifiedkabir.khan@jboss.com//projects/microcontainer/trunk/container/src/main/org/jboss/repository/plugins/basic/BasicMetaDataContextFactory.javaFixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names"
58238modifiedkabir.khan@jboss.com//projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/integration/AOPJoinpointFactory.javaFixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names"
58238modifiedkabir.khan@jboss.com//projects/microcontainer/trunk/aop-mc-int/src/main/org/jboss/aop/microcontainer/beans/AspectBeanMetaDataFactory.javaFixes to include the aop/mc integration into jboss 5Split jboss-aop-mc-int.jar into jboss-aop-mc-int.boot (for jboss/lib/) and jboss-aop-mc-deployer.jar (for jboss/server/xxx/deployers/jboss-aop-jboss5-deployer/). The boot jar contains the hooks (AOPJoinpointFactory, AOPMetaDataContextFactory, AOPDependencyBuilder and the xml stuff) into the mc for AOP, but does not call through to the AOP layer until the classes in the deployer jar become available.Modify MetaDataContextFactory to take an additional classloader parameter.Remove hard references to deployer.jar classes from classes in the boot jar.Only check dependencies and attempt to create proxies for classes that have "advisable names"