Dear Gumpmeisters,
The following 3 notifys should have been sent
*********************************************************** G U M P
[g...@vmgump]: Project lenya-core-api (in module lenya) failed
[g...@vmgump]: Project james-server (in module james-server) failed
[g...@vmgump]: Project camel-jms-test (in module camel) failed
*********************************************************** G U M P
[g...@vmgump]: Project lenya-core-api (in module lenya) 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 [email protected].
Project lenya-core-api 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:
- lenya-core-api : Content Management System
Full details are available at:
http://vmgump.apache.org/gump/public/lenya/lenya-core-api/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-INFO- Optional dependency cocoon22-flowscript-impl prerequisite failed with
reason build failed
-INFO- Optional dependency cocoon22-chaperon-impl prerequisite failed with
reason build failed
-INFO- Optional dependency cocoon22-serializers-impl prerequisite failed with
reason build failed
-INFO- Optional dependency cocoon22-serializers-impl prerequisite failed with
reason build failed
-INFO- Optional dependency cocoon22-validation-impl prerequisite failed with
reason build failed
-INFO- Optional dependency cocoon22-core prerequisite failed with reason build
failed
-INFO- Optional dependency cocoon22-sitemap-impl prerequisite failed with
reason build failed
-DEBUG- (Gump generated) Maven2 Settings in:
/srv/gump/public/workspace/lenya/org.apache.lenya.core.api/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/srv/gump/public/workspace/lenya/org.apache.lenya.core.api/pom.xml
The following work was performed:
http://vmgump.apache.org/gump/public/lenya/lenya-core-api/gump_work/build_lenya_lenya-core-api.html
Work Name: build_lenya_lenya-core-api (Type: Build)
Work ended in a state of : Failed
Elapsed: 32 secs
Command Line: mvn --batch-mode --settings
/srv/gump/public/workspace/lenya/org.apache.lenya.core.api/gump_mvn_settings.xml
package
[Working Directory: /srv/gump/public/workspace/lenya/org.apache.lenya.core.api]
---------------------------------------------
6) org.apache.cocoon:cocoon-core:test-jar:tests:2.2.1-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.cocoon
-DartifactId=cocoon-core -Dversion=2.2.1-SNAPSHOT -Dclassifier=tests
-Dpackaging=test-jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.cocoon
-DartifactId=cocoon-core -Dversion=2.2.1-SNAPSHOT -Dclassifier=tests
-Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.lenya:lenya-core-api:jar:2.2.0-SNAPSHOT
2) org.apache.cocoon:cocoon-core:test-jar:tests:2.2.1-SNAPSHOT
7) org.apache.cocoon:cocoon-sitemap-impl:test-jar:tests:1.1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.cocoon
-DartifactId=cocoon-sitemap-impl -Dversion=1.1.0-SNAPSHOT -Dclassifier=tests
-Dpackaging=test-jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.cocoon
-DartifactId=cocoon-sitemap-impl -Dversion=1.1.0-SNAPSHOT -Dclassifier=tests
-Dpackaging=test-jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.lenya:lenya-core-api:jar:2.2.0-SNAPSHOT
2) org.apache.cocoon:cocoon-sitemap-impl:test-jar:tests:1.1.0-SNAPSHOT
----------
7 required artifacts are missing.
for artifact:
org.apache.lenya:lenya-core-api:jar:2.2.0-SNAPSHOT
from the specified remote repositories:
gump-central (http://localhost:8192/maven2),
java.net (http://download.java.net/maven/1),
java.net.2 (http://download.java.net/maven/2),
gump-apache.snapshots (http://localhost:8192/repo/m2-snapshot-repository)
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 31 seconds
[INFO] Finished at: Fri Sep 03 18:36:41 UTC 2010
[INFO] Final Memory: 11M/26M
[INFO] ------------------------------------------------------------------------
---------------------------------------------
To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/lenya/lenya-core-api/rss.xml
- Atom: http://vmgump.apache.org/gump/public/lenya/lenya-core-api/atom.xml
============================== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 12001203092010, vmgump.apache.org:vmgump:12001203092010
Gump E-mail Identifier (unique within run) #2.
*********************************************************** G U M P
[g...@vmgump]: Project james-server (in module james-server) 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 [email protected].
Project james-server has an issue affecting its community integration.
This issue affects 2 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- james-server : James Server
- james-server-test : James Server
Full details are available at:
http://vmgump.apache.org/gump/public/james-server/james-server/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-INFO- Optional dependency openjpa prerequisite failed with reason build failed
-INFO- Optional dependency james-jsieve failed with reason build failed
-INFO- Optional dependency activemq-pool prerequisite failed with reason build
failed
-INFO- Optional dependency activemq-core prerequisite failed with reason build
failed
-DEBUG- (Gump generated) Maven2 Settings in:
/srv/gump/public/workspace/james-server/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in: /srv/gump/public/workspace/james-server/pom.xml
-DEBUG- Extracted fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/james-server/james-server/gump_work/build_james-server_james-server.html
Work Name: build_james-server_james-server (Type: Build)
Work ended in a state of : Failed
Elapsed: 3 secs
Command Line: mvn --batch-mode -DskipTests=true --settings
/srv/gump/public/workspace/james-server/gump_mvn_settings.xml install
[Working Directory: /srv/gump/public/workspace/james-server]
---------------------------------------------
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Project ID: org.apache.james:james-server-core-function
POM Location: /srv/gump/public/workspace/james-server/core-function/pom.xml
Validation Messages:
[0] 'dependencies.dependency.version' is missing for
javax.persistence:persistence-api:jar
Reason: Failed to validate POM for project
org.apache.james:james-server-core-function at
/srv/gump/public/workspace/james-server/core-function/pom.xml
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Failed to validate POM for
project org.apache.james:james-server-core-function at
/srv/gump/public/workspace/james-server/core-function/pom.xml
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.InvalidProjectModelException: Failed to
validate POM for project org.apache.james:james-server-core-function at
/srv/gump/public/workspace/james-server/core-function/pom.xml
at
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1077)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:880)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:560)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391)
... 12 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Fri Sep 03 20:25:30 UTC 2010
[INFO] Final Memory: 5M/15M
[INFO] ------------------------------------------------------------------------
---------------------------------------------
To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/james-server/james-server/rss.xml
- Atom: http://vmgump.apache.org/gump/public/james-server/james-server/atom.xml
============================== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 12001203092010, vmgump.apache.org:vmgump:12001203092010
Gump E-mail Identifier (unique within run) #3.
*********************************************************** G U M P
[g...@vmgump]: Project camel-jms-test (in module camel) 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 [email protected].
Project camel-jms-test 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:
- camel-jms-test : Integration framework based on known Enterprise
Integration
...
Full details are available at:
http://vmgump.apache.org/gump/public/camel/camel-jms-test/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-WARNING- Overriding Maven2 settings:
[/srv/gump/public/workspace/camel/components/camel-jms/gump_mvn_settings.xml]
-DEBUG- (Gump generated) Maven2 Settings in:
/srv/gump/public/workspace/camel/components/camel-jms/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/srv/gump/public/workspace/camel/components/camel-jms/pom.xml
-INFO- Project Reports in:
/srv/gump/public/workspace/camel/components/camel-jms/target/surefire-report
-WARNING- No directory
[/srv/gump/public/workspace/camel/components/camel-jms/target/surefire-report]
The following work was performed:
http://vmgump.apache.org/gump/public/camel/camel-jms-test/gump_work/build_camel_camel-jms-test.html
Work Name: build_camel_camel-jms-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 34 mins 35 secs
Command Line: mvn --batch-mode --settings
/srv/gump/public/workspace/camel/components/camel-jms/gump_mvn_settings.xml
test
[Working Directory: /srv/gump/public/workspace/camel/components/camel-jms]
---------------------------------------------
Running org.apache.camel.component.jms.tx.AsyncEndpointJmsTXWireTapTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.787 sec
Running org.apache.camel.component.jms.issues.JmsSpringSimpleTXResequencerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.16 sec
Running org.apache.camel.component.jms.JmsRouteUsingSpringWithAutoWireTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.366 sec
Running org.apache.camel.component.jms.JmsRouteWithCustomKeyFormatStrategyTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.766 sec
Running org.apache.camel.component.jms.issues.BruceHandlingBeanExceptionTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.917 sec
Running org.apache.camel.component.jms.ConsumeJmsMapMessageTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.017 sec
Running org.apache.camel.component.jms.tx.XMLQueueToQueueTransactionTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.485 sec
Running
org.apache.camel.component.jms.JmsRouteWithPassThroughKeyFormatStrategyTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.745 sec
Running org.apache.camel.component.jms.BrowsableQueueTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.151 sec
Running org.apache.camel.component.jms.JmsTransferExchangeTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.131 sec
Running
org.apache.camel.component.jms.issues.JmsSendToAlotOfDestinationWithSameEndpointTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.311 sec
Running org.apache.camel.component.jms.JmsRoutingSlipTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.052 sec
Running org.apache.camel.component.jms.JmsRouteUsingDifferentHeadersTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.55 sec
Running org.apache.camel.component.jms.JmsRouteToFileTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.509 sec
Running
org.apache.camel.component.jms.tx.JMXTXUseOriginalBodyWithDLCErrorHandlerTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.584 sec
Results :
Failed tests:
Tests run: 312, Failures: 1, Errors: 0, Skipped: 6
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
Please refer to
/srv/gump/public/workspace/camel/components/camel-jms/target/surefire-reports
for the individual test results.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 34 minutes 32 seconds
[INFO] Finished at: Fri Sep 03 21:00:04 UTC 2010
[INFO] Final Memory: 42M/101M
[INFO] ------------------------------------------------------------------------
---------------------------------------------
To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/camel/camel-jms-test/rss.xml
- Atom: http://vmgump.apache.org/gump/public/camel/camel-jms-test/atom.xml
============================== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 12001203092010, vmgump.apache.org:vmgump:12001203092010
Gump E-mail Identifier (unique within run) #4.
--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
