gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From g...@vmgump.apache.org
Subject BATCH: All dressed up, with nowhere to go...
Date Sun, 06 Jun 2010 03:25:18 GMT
Dear Gumpmeisters,
            
The following 2 notifys should have been sent

*********************************************************** G U M P
[GUMP@vmgump]: Project jetty-enforcer-rules (in module jetty-toolchain) failed
[GUMP@vmgump]: Project apacheds-core-mock (in module apacheds) failed
*********************************************************** G U M P
[GUMP@vmgump]: Project jetty-enforcer-rules (in module jetty-toolchain) 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 jetty-enforcer-rules 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:
    - jetty-enforcer-rules :  Tools for building Jetty


Full details are available at:
    http://vmgump.apache.org/gump/public/jetty-toolchain/jetty-enforcer-rules/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -DEBUG- Sole output [jetty-enforcer-rules-*[0-9T].jar] identifier set to project name
 -INFO- Making directory for Maven2 settings: [/srv/gump/public/workspace/jetty-toolchain/jetty-enforcer-rules]
 -DEBUG- (Gump generated) Maven2 Settings in: /srv/gump/public/workspace/jetty-toolchain/jetty-enforcer-rules/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/jetty-toolchain/jetty-enforcer-rules/gump_work/build_jetty-toolchain_jetty-enforcer-rules.html
Work Name: build_jetty-toolchain_jetty-enforcer-rules (Type: Build)
Work ended in a state of : Failed
Elapsed: 8 secs
Command Line: mvn --batch-mode --settings /srv/gump/public/workspace/jetty-toolchain/jetty-enforcer-rules/gump_mvn_settings.xml
install 
[Working Directory: /srv/gump/public/workspace/jetty-toolchain/jetty-enforcer-rules]
CLASSPATH: /usr/lib/jvm/java-6-sun/lib/tools.jar:/srv/gump/public/workspace/jetty-toolchain/jetty-toolchain/pom.xml:/srv/gump/public/workspace/junit/dist/junit-05062010.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-05062010.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-05062010.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-05062010.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-05062010-dep.jar
---------------------------------------------
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO]    task-segment: [install]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Cannot execute mojo: resources. It requires a project with an existing pom.xml, but
the build is not using one.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7 seconds
[INFO] Finished at: Sat Jun 05 18:50:39 PDT 2010
[INFO] Final Memory: 4M/7M
[INFO] ------------------------------------------------------------------------
---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/jetty-toolchain/jetty-enforcer-rules/rss.xml
- Atom: http://vmgump.apache.org/gump/public/jetty-toolchain/jetty-enforcer-rules/atom.xml

============================== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 05001605062010, vmgump:vmgump-public:05001605062010
Gump E-mail Identifier (unique within run) #1.

*********************************************************** G U M P
[GUMP@vmgump]: Project apacheds-core-mock (in module apacheds) 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 apacheds-core-mock 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:
    - apacheds-all :  Apache Directory Server
    - apacheds-core-mock :  Apache Directory Server


Full details are available at:
    http://vmgump.apache.org/gump/public/apacheds/apacheds-core-mock/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -DEBUG- Sole output [apacheds-core-mock-*[0-9T].jar] identifier set to project name
 -INFO- Making directory for Maven2 settings: [/srv/gump/public/workspace/apacheds/core-mock]
 -DEBUG- (Gump generated) Maven2 Settings in: /srv/gump/public/workspace/apacheds/core-mock/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/apacheds/apacheds-core-mock/gump_work/build_apacheds_apacheds-core-mock.html
Work Name: build_apacheds_apacheds-core-mock (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: mvn --batch-mode --settings /srv/gump/public/workspace/apacheds/core-mock/gump_mvn_settings.xml
install 
[Working Directory: /srv/gump/public/workspace/apacheds/core-mock]
CLASSPATH: /usr/lib/jvm/java-6-sun/lib/tools.jar:/srv/gump/public/workspace/apacheds/pom.xml:/srv/gump/public/workspace/apacheds/core-api/target/apacheds-core-api-1.5.8-SNAPSHOT.jar
---------------------------------------------
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO]    task-segment: [install]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Cannot execute mojo: resources. It requires a project with an existing pom.xml, but
the build is not using one.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Sun Jun 06 02:58:59 PDT 2010
[INFO] Final Memory: 4M/7M
[INFO] ------------------------------------------------------------------------
---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/apacheds/apacheds-core-mock/rss.xml
- Atom: http://vmgump.apache.org/gump/public/apacheds/apacheds-core-mock/atom.xml

============================== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 05001605062010, vmgump:vmgump-public:05001605062010
Gump E-mail Identifier (unique within run) #2.


--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org


Mime
View raw message