View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050527160200

BUILD FAILED
Ant Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/
Date of build: 05/27/2005 16:02:00
Time to build: 11 minutes 13 seconds
Last changed: 05/27/2005 15:54:05
Last log entry: Fix the eclipse build.We managed to go two weeks without webservices refactoring their codebase, again... :-)

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

 Modifications since last build:  (62)
1.23modifiedadrianbuild/eclipse.psfFix the eclipse build.We managed to go two weeks without webservices refactoring their codebase, again... :-)
1.36modifiedadriantestsuite/.classpathFix the eclipse build.We managed to go two weeks without webservices refactoring their codebase, again... :-)
1.27modifiedadrianvaria/.classpathFix the eclipse build.We managed to go two weeks without webservices refactoring their codebase, again... :-)
1.18modifiedadrianwebservice/.classpathFix the eclipse build.We managed to go two weeks without webservices refactoring their codebase, again... :-)
1.2modifiedadriandependency/src/main/org/jboss/dependency/plugins/AbstractController.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.2modifiedadriandependency/src/main/org/jboss/dependency/plugins/AbstractControllerContext.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.2modifiedadriandependency/src/main/org/jboss/dependency/plugins/AbstractDependencyInfo.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.2modifiedadriandependency/src/main/org/jboss/dependency/plugins/AbstractDependencyItem.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.2modifiedadriandependency/src/main/org/jboss/dependency/spi/ControllerContext.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.2modifiedadriandependency/src/main/org/jboss/dependency/spi/DependencyInfo.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.3modifiedadriankernel/src/main/org/jboss/kernel/plugins/registry/AbstractKernelRegistryEntry.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.4modifiedadriankernel/src/main/org/jboss/beans/metadata/plugins/AbstractDemandMetaData.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.6modifiedadriankernel/src/main/org/jboss/beans/metadata/plugins/AbstractDependencyValueMetaData.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.12modifiedadriankernel/src/main/org/jboss/kernel/plugins/dependency/basic/BasicKernelController.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.4deletedadriankernel/src/main/org/jboss/kernel/plugins/dependency/spi/DependencyInfo.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.3deletedadriankernel/src/main/org/jboss/kernel/plugins/dependency/spi/DependencyItem.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.2deletedadriankernel/src/main/org/jboss/kernel/plugins/dependency/spi/package.htmlMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.4modifiedadriankernel/src/main/org/jboss/kernel/spi/dependency/KernelController.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.2deletedadriankernel/src/main/org/jboss/kernel/spi/dependency/KernelControllerAction.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.5modifiedadriankernel/src/main/org/jboss/kernel/spi/dependency/KernelControllerContext.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.5deletedadriankernel/src/main/org/jboss/kernel/spi/dependency/KernelControllerState.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.2modifiedadriankernel/src/main/org/jboss/kernel/spi/registry/KernelRegistryEntry.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/dependency/support/TestUtil.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.9modifiedadriankernel/src/tests/org/jboss/test/kernel/xml/test/XMLTestCase.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.10modifiedadriankernel/.classpathMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.3modifiedadriankernel/build-test.xmlMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.13modifiedadriankernel/build.xmlMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.8modifiedadriankernel/jbossbuild.xmlMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.4modifiedadriankernel/src/main/org/jboss/beans/metadata/spi/DemandMetaData.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.3modifiedadriankernel/src/main/org/jboss/beans/metadata/spi/DependencyValueMetaData.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.8deletedadriankernel/src/main/org/jboss/kernel/plugins/dependency/AbstractControllerContext.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.3deletedadriankernel/src/main/org/jboss/kernel/plugins/dependency/AbstractDependencyInfo.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.5deletedadriankernel/src/main/org/jboss/kernel/plugins/dependency/AbstractDependencyItem.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.17modifiedadriankernel/src/main/org/jboss/kernel/plugins/dependency/AbstractKernelController.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.2deletedadriankernel/src/main/org/jboss/kernel/plugins/dependency/AbstractKernelControllerAction.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.1addedadriankernel/src/main/org/jboss/kernel/plugins/dependency/AbstractKernelControllerContext.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.3modifiedadriankernel/src/main/org/jboss/kernel/plugins/dependency/DemandDependencyItem.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.1addedadriankernel/src/main/org/jboss/kernel/plugins/dependency/KernelControllerContextActions.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.22modifiedadriankernel/src/main/org/jboss/kernel/plugins/deployment/xml/BeanSchemaBinding.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.19modifiedadriankernel/src/main/org/jboss/kernel/plugins/deployment/xml/XMLKernelDeployer.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.2modifiedadriankernel/src/main/org/jboss/kernel/plugins/registry/basic/BasicKernelRegistryFactory.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/dependency/test/AbstractKernelDependencyTest.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.4modifiedadriankernel/src/tests/org/jboss/test/kernel/dependency/test/ConstructorDependencyTestCase.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.4modifiedadriankernel/src/tests/org/jboss/test/kernel/dependency/test/DemandDependencyTestCase.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.3modifiedadriankernel/src/tests/org/jboss/test/kernel/dependency/test/GenericBeanFactoryDependencyTestCase.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.2modifiedadriankernel/src/tests/org/jboss/test/kernel/dependency/test/LifecycleDependencyTestCase.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.7modifiedadriankernel/src/tests/org/jboss/test/kernel/dependency/test/PlainDependencyTestCase.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.17modifiedadrianaspects/.classpathMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.7modifiedadrianaspects/build-test.xmlMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.39modifiedadrianaspects/build.xmlMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.9modifiedadrianaspects/src/test/org/jboss/test/kernel/AspectTestCase.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.4modifiedadrianaspects/src/test/org/jboss/test/kernel/KernelTestCase.javaMake the kernel use the controller model from dependency.This still needs completing to "internalize" the controller actionsinto the BeanMetaData model rather than extending the controller.In particular, the access of the dependencies registered directly in KernelRegistry (+ other registries) needs sorting out.
1.63modifiedtdieslertestsuite/imports/test-jars.xmlRemove HandlerTracker from war
1.60modifiedtdieslerwebservice/build.xmlInclude axis-ws4ee.jar from thirdparty in jboss-ws4ee.sar
1.466modifiedtdieslertestsuite/build.xmlUse axis-ws4ee.jar binary from jboss-4.0.2.Retire module jaxrpc.
1.1addedtdieslerthirdparty/jboss/axis/lib/axis-ws4ee.jarbranches: 1.1.2;Use axis-ws4ee.jar binary from jboss-4.0.2.Retire module jaxrpc.
1.39modifiedtdieslertools/etc/buildmagic/modules.entUse axis-ws4ee.jar binary from jboss-4.0.2.Retire module jaxrpc.
1.24modifiedtdieslertools/etc/buildmagic/modules.xmlUse axis-ws4ee.jar binary from jboss-4.0.2.Retire module jaxrpc.
1.65modifiedtdieslertools/etc/buildmagic/libraries.entUse axis-ws4ee.jar binary from jboss-4.0.2.Retire module jaxrpc.
1.21modifiedtdieslertools/etc/buildmagic/libraries.xmlUse axis-ws4ee.jar binary from jboss-4.0.2.Retire module jaxrpc.
1.59modifiedtdieslerwebservice/build.xmlUse axis-ws4ee.jar binary from jboss-4.0.2.Retire module jaxrpc.
1.404modifiedtdieslerbuild/build.xmlUse axis-ws4ee.jar binary from jboss-4.0.2.Retire module jaxrpc.

Reply via email to