Re: [GUMP@vmgump]: Project fulcrum-security-memory (in module turbine-fulcrum) failed
Hi General Gump, On 23.08.12 02:08, fulcrum-security-memory development wrote: Tests run: 12, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.82 sec FAILURE! Results : Tests in error: testGetGroup(org.apache.fulcrum.security.memory.basic.MemoryGroupManagerTest) testGetGroupByName(org.apache.fulcrum.security.memory.basic.MemoryGroupManagerTest) Tests run: 118, Failures: 0, Errors: 17, Skipped: 0 Any chance to get access to the target directory of the build? No idea why the tests fail. Bye, Thomas. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: [GUMP@vmgump]: Project fulcrum-parser (in module turbine-fulcrum) failed
Hi General Gump, On 23.08.12 04:00, fulcrum-parser development wrote: Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.223 sec FAILURE! Results : Tests in error: testAddPathInfo(org.apache.fulcrum.parser.ParameterParserTest) Tests run: 59, Failures: 0, Errors: 1, Skipped: 0 Any chance to get access to the target directory of the build? No idea why the test fails. Bye, Thomas. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: [GUMP@vmgump]: Project fulcrum-quartz-test (in module turbine-fulcrum) failed
Hi Stefan, On 20.11.11 06:59, Stefan Bodewig wrote: If it works for a local build then the most likely reason is some sort of change in SLF4J that it now requires one of the bindings to be available and didn't require it in the version you get locally. Well the build works fine locally, including tests and such. After all, I made release based on this code level. Not sure, it depends on whether you want to take explicit control over logging (I think you should, but don't know enough about fulcrum or even fulcrum-quartz) and provide some sort of slf4j binding (as optional dependency, I guess). If you don't want to do that then I currently don't see what you could do. I don't like meddling with transitive dependencies. Probably I'll disable the fulcrum-quartz-test project in Gump. Bye, Thomas. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: [GUMP@vmgump]: Project fulcrum-quartz-test (in module turbine-fulcrum) failed
Hi General Gump, On 19.11.11 05:33, fulcrum-quartz development wrote: The following work was performed: http://vmgump.apache.org/gump/public/turbine-fulcrum/fulcrum-quartz-test/gump_work/build_turbine-fulcrum_fulcrum-quartz-test.html Work Name: build_turbine-fulcrum_fulcrum-quartz-test (Type: Build) Work ended in a state of : Failed Elapsed: 6 secs Command Line: /opt/maven2/bin/mvn --batch-mode --settings /srv/gump/public/workspace/turbine-fulcrum/quartz/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/turbine-fulcrum/quartz] M2_HOME: /opt/maven2 - at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) Caused by: java.lang.IllegalStateException: org.slf4j.LoggerFactory could not be successfully initialized. See also http://www.slf4j.org/codes.html#unsuccessfulInit at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:275) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) at org.quartz.impl.StdSchedulerFactory.init(StdSchedulerFactory.java:274) at org.apache.fulcrum.quartz.impl.QuartzSchedulerImpl.initialize(QuartzSchedulerImpl.java:114) at org.apache.fulcrum.yaafi.framework.component.AvalonServiceComponentImpl.initialize(AvalonServiceComponentImpl.java:404) at org.apache.fulcrum.yaafi.framework.component.AvalonServiceComponentImpl.incarnateInstance(AvalonServiceComponentImpl.java:106) at org.apache.fulcrum.yaafi.framework.component.ServiceComponentImpl.getInstance(ServiceComponentImpl.java:139) at org.apache.fulcrum.yaafi.framework.component.ServiceComponentImpl.incarnate(ServiceComponentImpl.java:154) ... 31 more Tests run: 6, Failures: 0, Errors: 6, Skipped: 0, Time elapsed: 0.636 sec FAILURE! Could some kind soul enlighten me, WTF is going on here again? Is this a topic we can fix? Bye, Thomas. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Fwd: [GUMP@vmgump]: Project turbine-core (in module turbine-core) failed
On 01.04.11 06:05, Stefan Bodewig wrote: Burn a few goats. Done. Big stench. Nothing changed. What now? ;-) OK, the way Gump works it means Turbine must be built before Torque, so we must make torque-generator depend on turbine-core (and obviously remove the torque dependencies from turbine-core). We'll also need to check whether any of Turbine's dependencies depend on Torque themselves. I'll take care of this. I'm not a big fan of this solution. Such helper constructs tend to complicate things and some day nobody will remember what it was meant for in the first place. There used to be a commons-xxx-2.x dependency in Gump where some incompatible change had been circumvented. Couldn't we do the something similar here? Secondly this means Torque 3.x will be downloaded from Maven central and put into the local repository. Given that Torque4 seems to be known to be incompatible to 3.x (I assume this is intentional) this may be a good It sure is. What is the general idea of Gump to handle incompatible API changes? thing so I'd live with it (the alternative would be to use a separate local repository). How would the local repository help here? I guess it could help me with fulcrum-quartz as well. Bye, Thomas. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Fwd: [GUMP@vmgump]: Project turbine-core (in module turbine-core) failed
Hi General Gump, This problem started all of a sudden. I hoped it would vanish the same way. Unfortunately it doesn't. I have no idea what is going on here. The plugin used to work just fine. Any ideas? (Please copy d...@turbine.apache.org) Bye, Thomas. Original Message Subject: [GUMP@vmgump]: Project turbine-core (in module turbine-core) failed Date: Wed, 30 Mar 2011 12:42:54 UTC From: d...@turbine.apache.org Reply-To: Turbine Developers List d...@turbine.apache.org To: d...@turbine.apache.org To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at general@gump.apache.org. Project turbine-core has an issue affecting its community integration. This issue affects 2 projects, and has been outstanding for 64 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - turbine-core : A servlet based framework. - turbine-core-test : A servlet based framework. Full details are available at: http://vmgump.apache.org/gump/public/turbine-core/turbine-core/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Optional dependency commons-fileupload prerequisite failed with reason build failed -INFO- Optional dependency httpunit failed with reason build failed -DEBUG- (Apache Gump generated) Apache Maven Settings in: /srv/gump/public/workspace/turbine-core/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/turbine-core/pom.xml -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/turbine-core/turbine-core/gump_work/build_turbine-core_turbine-core.html Work Name: build_turbine-core_turbine-core (Type: Build) Work ended in a state of : Failed Elapsed: 30 secs Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true --settings /srv/gump/public/workspace/turbine-core/gump_mvn_settings.xml package [Working Directory: /srv/gump/public/workspace/turbine-core] M2_HOME: /opt/maven2 - urls[19] = file:/srv/gump/public/workspace/mvnlocalrepo/shared/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar urls[20] = file:/srv/gump/public/workspace/mvnlocalrepo/shared/commons-configuration/commons-configuration/1.4/commons-configuration-1.4.jar urls[21] = file:/srv/gump/public/workspace/mvnlocalrepo/shared/commons-logging/commons-logging-api/1.0.4/commons-logging-api-1.0.4.jar urls[22] = file:/srv/gump/public/workspace/mvnlocalrepo/shared/commons-digester/commons-digester/1.8/commons-digester-1.8.jar urls[23] = file:/srv/gump/public/workspace/mvnlocalrepo/shared/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar urls[24] = file:/srv/gump/public/workspace/mvnlocalrepo/shared/commons-beanutils/commons-beanutils-core/1.7.0/commons-beanutils-core-1.7.0.jar urls[25] = file:/srv/gump/public/workspace/mvnlocalrepo/shared/commons-codec/commons-codec/1.3/commons-codec-1.3.jar urls[26] = file:/srv/gump/public/workspace/mvnlocalrepo/shared/commons-jxpath/commons-jxpath/1.2/commons-jxpath-1.2.jar urls[27] = file:/srv/gump/public/workspace/mvnlocalrepo/shared/xerces/xerces/1.2.3/xerces-1.2.3.jar urls[28] = file:/srv/gump/public/workspace/mvnlocalrepo/shared/ant/ant-optional/1.5.1/ant-optional-1.5.1.jar urls[29] = file:/srv/gump/public/workspace/mvnlocalrepo/shared/jdom/jdom/b9/jdom-b9.jar Number of imports: 10 import: org.codehaus.classworlds.Entry@a6c57a42 import: org.codehaus.classworlds.Entry@12f43f3b import: org.codehaus.classworlds.Entry@20025374 import: org.codehaus.classworlds.Entry@f8e44ca4 import: org.codehaus.classworlds.Entry@92758522 import: org.codehaus.classworlds.Entry@ebf2705b import: org.codehaus.classworlds.Entry@bb25e54 import: org.codehaus.classworlds.Entry@bece5185 import: org.codehaus.classworlds.Entry@3fee8e37 import: org.codehaus.classworlds.Entry@3fee19d8 this realm = plexus.core urls[0] = file:/opt/maven2/lib/maven-2.2.1-uber.jar Number of imports: 10 import: org.codehaus.classworlds.Entry@a6c57a42 import: org.codehaus.classworlds.Entry@12f43f3b import: org.codehaus.classworlds.Entry@20025374 import: org.codehaus.classworlds.Entry@f8e44ca4 import: org.codehaus.classworlds.Entry@92758522 import: org.codehaus.classworlds.Entry@ebf2705b import: org.codehaus.classworlds.Entry@bb25e54 import: org.codehaus.classworlds.Entry@bece5185 import: org.codehaus.classworlds.Entry@3fee8e37 import: org.codehaus.classworlds.Entry@3fee19d8 - [INFO] [ERROR] BUILD ERROR [INFO] [INFO]
Re: Fwd: [GUMP@vmgump]: Project turbine-core (in module turbine-core) failed
CCed to torque-dev for Thomas Fox to know. On 31.03.11 16:32, Stefan Bodewig wrote: Gump will hand out the latest Torque jars, i.e. torque-runtime-4.0-alpha1-SNAPSHOT.jar, torque-generator-4.0-alpha1-SNAPSHOT.jar and torque-templates-4.0-alpha1-SNAPSHOT.jar when asked for Torque. Does the plugin work with these versions? Which of the jars contains org.apache.torque.task.TorqueDataModelTask It used to be in the Torque generator jar but the Torque generator has been rewritten from the ground up by Thomas Fox and probably the plugin doesn't know about that. Anyhow, Turbine needs the Torque plugin/generator/templates/runtime Version 3.3. The current version is not backwards compatible. What do I have to do to achieve this? Bye, Thomas. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: [g...@vmgump]: Project db-torque-parent-test (in module db-torque) failed
general@gump.apache.org wrote: Running org.apache.torque.avalon.AvalonTest [DEBUG] Starting container... [DEBUG] Loading the service container class org.apache.fulcrum.yaafi.framework.container.ServiceContainerImpl [DEBUG] Instantiating the service container class org.apache.fulcrum.yaafi.framework.container.ServiceContainerImpl Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.179 sec FAILURE! This boils down to ---8--- java.lang.NoClassDefFoundError: org/apache/xml/serializer/OutputPropertiesFactory at org.apache.xalan.templates.OutputProperties.init(OutputProperties.java:83) ---8--- I see xalan and the serializer in the bootpath, however. What am I supposed to do? Bye, Thomas. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: [g...@vmgump]: Project fulcrum-pool (in module turbine-fulcrum) failed
Stefan Bodewig wrote: OTOH, classpath is completely irrelevant when you use mvn, only the stuff that is in your POM matters. I don't see a dependency on Avalon in http://svn.apache.org/viewvc/turbine/fulcrum/trunk/pool/pom.xml or http://svn.apache.org/viewvc/turbine/fulcrum/trunk/parent/pom.xml which makes me wonder why fulcrum-pool would build for you locally. Because it gets the avalon-api as a transient dependency for example from YAAFI or from fulcrum-factory. Wonder why that doesn't work with Gump? In any case, you are completely right. I need to add the dependency. Will commit soon. Thanks for the support, Bye, Thomas. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: [g...@vmgump]: Project fulcrum-pool (in module turbine-fulcrum) failed
fulcrum-pool development wrote: The following work was performed: http://vmgump.apache.org/gump/public/turbine-fulcrum/fulcrum-pool/gump_work/build_turbine-fulcrum_fulcrum-pool.html [...] CLASSPATH: /usr/lib/jvm/java-6-sun/lib/tools.jar:/srv/gump/public/workspace/turbine-fulcrum/pool/target/classes:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/excalibur/framework/api/target/excalibur-framework-api-02062009.jar:/srv/gump/public/workspace/excalibur/framework/impl/target/excalibur-framework-impl-02062009.jar:/srv/gump/public/workspace/turbine-fulcrum/yaafi/target/fulcrum-yaafi-1.0.7-SNAPSHOT.jar:/srv/gump/public/workspace/turbine-fulcrum/testcontainer/target/fulcrum-testcontainer-1.0.7-SNAP SH OT.jar:/srv/gump/public/workspace/junit/dist/junit-02062009.jar:/srv/gump/public/workspace/turbine-fulcrum/factory/target/fulcrum-factory-1.0.4-SNAPSHOT.jar - public class DefaultPoolService extends AbstractLogEnabled implements PoolService, Serviceable, Disposable, Initializable, Configurable /srv/gump/public/workspace/turbine-fulcrum/pool/src/java/org/apache/fulcrum/pool/DefaultPoolService.java:[55,83] cannot find symbol symbol: class Serviceable public class DefaultPoolService extends AbstractLogEnabled implements PoolService, Serviceable, Disposable, Initializable, Configurable /srv/gump/public/workspace/turbine-fulcrum/pool/src/java/org/apache/fulcrum/pool/DefaultPoolService.java:[55,96] cannot find symbol symbol: class Disposable public class DefaultPoolService extends AbstractLogEnabled implements PoolService, Serviceable, Disposable, Initializable, Configurable /srv/gump/public/workspace/turbine-fulcrum/pool/src/java/org/apache/fulcrum/pool/DefaultPoolService.java:[55,108] cannot find symbol symbol: class Initializable public class DefaultPoolService extends AbstractLogEnabled implements PoolService, Serviceable, Disposable, Initializable, Configurable /srv/gump/public/workspace/turbine-fulcrum/pool/src/java/org/apache/fulcrum/pool/DefaultPoolService.java:[55,123] cannot find symbol symbol: class Configurable public class DefaultPoolService extends AbstractLogEnabled implements PoolService, Serviceable, Disposable, Initializable, Configurable /srv/gump/public/workspace/turbine-fulcrum/pool/src/java/org/apache/fulcrum/pool/DefaultPoolService.java:[288,12] cannot find symbol symbol : class ServiceManager location: class org.apache.fulcrum.pool.DefaultPoolService /srv/gump/public/workspace/turbine-fulcrum/pool/src/java/org/apache/fulcrum/pool/DefaultPoolService.java:[575,26] cannot find symbol symbol : class Configuration location: class org.apache.fulcrum.pool.DefaultPoolService /srv/gump/public/workspace/turbine-fulcrum/pool/src/java/org/apache/fulcrum/pool/DefaultPoolService.java:[612,24] cannot find symbol symbol : class ServiceManager location: class org.apache.fulcrum.pool.DefaultPoolService /srv/gump/public/workspace/turbine-fulcrum/pool/src/java/org/apache/fulcrum/pool/DefaultPoolService.java:[577,14] cannot find symbol symbol : class Configuration location: class org.apache.fulcrum.pool.DefaultPoolService /srv/gump/public/workspace/turbine-fulcrum/pool/src/java/org/apache/fulcrum/pool/DefaultPoolService.java:[580,12] cannot find symbol symbol : class Configuration location: class org.apache.fulcrum.pool.DefaultPoolService /srv/gump/public/workspace/turbine-fulcrum/pool/src/java/org/apache/fulcrum/pool/DefaultPoolService.java:[587,12] cannot find symbol symbol : class Configuration location: class org.apache.fulcrum.pool.DefaultPoolService Why does that happen? I can see the excalibur-api is in the classpath?! Your help is appreciated. Bye, Thomas. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: [g...@vmgump]: Project db-torque-runtime (in module db-torque) failed
general@gump.apache.org wrote: [INFO] Compilation failure /srv/gump/public/workspace/db-torque/torque-runtime/src/main/java/org/apache/torque/TorqueInstance.java:[460,8] cannot access org.apache.commons.lang.exception.NestableException class file for org.apache.commons.lang.exception.NestableException not found In this case we catch a ConfigurationException from commons-configuration. This error obviously means that this Exception is based on commons-lang. How would we resolve this for the time being? Thanks in advance. Bye, Thomas. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: torque-gen build fails in Gump due to changes in commons-lang
Stefan Bodewig wrote: Maven2 support is pretty solid by now, the only major problem we haven't managed to solve is that of artifact names. You (or anybody who sees the build failure and wants to fix it) will have to modify the jar names whenever you change the version since we haven't found any way to tell mvn to use a fixed name of our choice from the CLI. Thanks for your corrections in SVN. I'm still not used to the Gump environment. I was not aware of the references. I take it that the Maven-2-built artifacts need to be named manually? Then I need to fix this in the Fulcrum builds as well. Please bear with me if I break something. Bye, Thomas. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: torque-gen build fails in Gump due to changes in commons-lang
Hi Stefan, Stefan Bodewig wrote: The question is whether you want to adapt to commons-lang changes (there may be good reasons not to) or not. If you want to stick with commons-lang 2.x, all that we'd need to do is to change the dependency on commons-lang into one on commons-lang-2.x in your Gump descriptor (which is here: http://svn.apache.org/repos/asf/gump/metadata/project/db-torque-gen.xml) which every ASF committer can change. Or you tell us to change it. Thank you for your support. We are currently in the process of changing the structure of our project in SVN. I will try to change the references in the Gump files to point to the actual trunk. BTW, we will switch to Maven-2 as the main build system. Is there something we need to take care of with respect to Gump? Bye, Thomas. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Cannot find problem: [Fwd: [EMAIL PROTECTED]: Project fulcrum-cache (in module jakarta-turbine-fulcrum) failed]
Thanks for your help. Adding the dependency to maven fixed it. Bye, Thomas. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cannot find problem: [Fwd: [EMAIL PROTECTED]: Project fulcrum-cache (in module jakarta-turbine-fulcrum) failed]
Hi folks, could you please help me to pinpoint a problem with the configuration of the gump-build of the fulcrum-cache module? The gump logs show that the concurrent library cannot be found. It is however referenced as dependency in the project descriptor. I tried to add the runtime=true attribute to the dependency to no avail. What else can I do? I cannot reproduce the problem here. Thanks in advance, Thomas Vandahl Original Message Subject: [EMAIL PROTECTED]: Project fulcrum-cache (in module jakarta-turbine-fulcrum) failed Date: Sat, 30 Dec 2006 05:46:04 PST From: fulcrum-cache development turbine-dev@jakarta.apache.org Reply-To: Turbine Developers List turbine-dev@jakarta.apache.org To: turbine-dev@jakarta.apache.org To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project fulcrum-cache has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 8 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - fulcrum-cache : Services Framework Full details are available at: http://vmgump.apache.org/gump/public/jakarta-turbine-fulcrum/fulcrum-cache/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [fulcrum-cache-30122006.jar] identifier set to project name -DEBUG- Dependency on excalibur-framework-api exists, no need to add for property maven.jar.avalon-framework-api. -DEBUG- Dependency on excalibur-framework-impl exists, no need to add for property maven.jar.avalon-framework-impl. -DEBUG- (Gump generated) Maven Properties in: /usr/local/gump/public/workspace/jakarta-turbine-fulcrum/cache/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /usr/local/gump/public/workspace/jakarta-turbine-fulcrum/cache/project.xml -DEBUG- Maven project properties in: /usr/local/gump/public/workspace/jakarta-turbine-fulcrum/cache/project.properties -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-turbine-fulcrum/fulcrum-cache/gump_work/build_jakarta-turbine-fulcrum_fulcrum-cache.html Work Name: build_jakarta-turbine-fulcrum_fulcrum-cache (Type: Build) Work ended in a state of : Failed Elapsed: 46 secs Command Line: maven --offline jar [Working Directory: /usr/local/gump/public/workspace/jakarta-turbine-fulcrum/cache] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-turbine-fulcrum/cache/target/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/ehcache-1.0/ehcache-1.0.jar:/usr/local/gump/packages/dougLea/concurrent.jar:/usr/local/gump/public/workspace/excalibur/framework/api/target/excalibur-framework-api-30122006.jar:/usr/local/gump/public/workspace/excalibur/framework/impl/target/excalibur-framework-impl-30122006.jar:/usr/local/gump/public/workspace/jakarta-turbine-fulcrum/yaafi/target/fulcrum-yaafi-30122006.jar :/usr/local/gump/public/workspace/jakarta-turbine-fulcrum/testcontainer/target/fulcrum-testcontainer-30122006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-30122006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-30122006.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-30122006.jar:/usr/local/gump/public/workspace/jakarta-turbine-jcs/target/jcs-30122006.jar - [junit] Could not initialize the container [junit] java.lang.RuntimeException: Could not initialize the container [junit] at org.apache.fulcrum.testcontainer.YAAFIContainer.startup(YAAFIContainer.java:90) [junit] at org.apache.fulcrum.testcontainer.BaseUnitTest.lookup(BaseUnitTest.java:134) [junit] at org.apache.fulcrum.cache.JCSCacheTest.setUp(JCSCacheTest.java:60) [junit] [junit] [junit] Testcase: testRefreshableTimeToLive(org.apache.fulcrum.cache.JCSCacheTest): Caused an ERROR [junit] Could not initialize the container [junit] java.lang.RuntimeException: Could not initialize the container [junit] at org.apache.fulcrum.testcontainer.YAAFIContainer.startup(YAAFIContainer.java:90) [junit
