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
On 2011-03-31, Thomas Vandahl wrote: This problem started all of a sudden. I hoped it would vanish the same way. Unfortunately it doesn't. vmgump says it has been that way for the last 66 runs. Probably longer since the counter gets reset if Gump doesn't even try to build Turbine because a required dependency failed to build. I have no idea what is going on here. The plugin used to work just fine. Any ideas? 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 ? Stefan - 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
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
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters,
The following 11 notifys should have been sent
*** G U M P
[GUMP@vmgump]: Project velocity-tools-view (in module velocity-tools) failed
[GUMP@vmgump]: Project cocoon22-store-impl (in module cocoon) failed
[GUMP@vmgump]: Project cocoon22-jnet (in module cocoon) failed
[GUMP@vmgump]: Project cocoon22-pipeline-impl (in module cocoon) failed
[GUMP@vmgump]: Project cocoon22-xml-resolver (in module cocoon) failed
[GUMP@vmgump]: Project cocoon22-servlet-service-impl (in module cocoon) failed
[GUMP@vmgump]: Project pdfbox-lucene (in module pdfbox) failed
[GUMP@vmgump]: Project cocoon22-expression-language-impl (in module cocoon)
failed
[GUMP@vmgump]: Project camel-spring-test (in module camel) failed
[GUMP@vmgump]: Project portals-bridges-script-test (in module portals-bridges)
failed
[GUMP@vmgump]: Project portals-pluto-trunk-test (in module portals-pluto-trunk)
failed
*** G U M P
[GUMP@vmgump]: Project velocity-tools-view (in module velocity-tools) failed
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 velocity-tools-view has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- velocity-tools-view : VelocityTools project
Full details are available at:
http://vmgump.apache.org/gump/public/velocity-tools/velocity-tools-view/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Sole jar output [velocity-tools-view-*[0-9T].jar] identifier set to
project name
-DEBUG- (Apache Gump generated) Apache Maven Settings in:
/srv/gump/public/workspace/velocity-tools/velocity-tools-view/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/srv/gump/public/workspace/velocity-tools/velocity-tools-view/pom.xml
-DEBUG- Extracted fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/velocity-tools/velocity-tools-view/gump_work/build_velocity-tools_velocity-tools-view.html
Work Name: build_velocity-tools_velocity-tools-view (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/velocity-tools/velocity-tools-view/gump_mvn_settings.xml
install
[Working Directory:
/srv/gump/public/workspace/velocity-tools/velocity-tools-view]
M2_HOME: /opt/maven2
-
[INFO] Scanning for projects...
[INFO]
[INFO] Building Apache Velocity Tools - View tools
[INFO]task-segment: [install]
[INFO]
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] snapshot org.apache.velocity:velocity-tools-generic:2.1.0-SNAPSHOT:
checking for updates from apache.snapshots
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'41e8402b5b2bbecd9b89b2dd62ed903da669bd31'; remote = 'html
head
' - RETRYING
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'41e8402b5b2bbecd9b89b2dd62ed903da669bd31'; remote = 'html
head
' - IGNORING
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve dependencies for one or more projects in the reactor.
Reason: Unable to get dependency information: Unable to read the metadata file
for artifact 'org.apache.velocity:velocity-tools-generic:jar': Error getting
POM for 'org.apache.velocity:velocity-tools-generic' from the repository:
Unable to read local copy of metadata: Cannot read metadata from
'/srv/gump/public/workspace/mvnlocalrepo/velocity/org/apache/velocity/velocity-tools-generic/2.1.0-SNAPSHOT/maven-metadata-apache.snapshots.xml':
end tag name /p must match start tag name br from line 6 (position: TEXT
seen ...a href=/home page/a.\n/p... @8:5)
org.apache.velocity:velocity-tools-generic:pom:2.1.0-SNAPSHOT
for project org.apache.velocity:velocity-tools-generic
org.apache.velocity:velocity-tools-generic:jar:2.1.0-SNAPSHOT
from the specified remote
Re: Fwd: [GUMP@vmgump]: Project turbine-core (in module turbine-core) failed
On 2011-03-31, Thomas Vandahl wrote: 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. That's what I thought. What do I have to do to achieve this? Burn a few goats. 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. 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 thing so I'd live with it (the alternative would be to use a separate local repository). Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
