We made some changes to the Apache James mailets project and now Gump
builds are failing. Where can we configure/disable Gump.
We have builds on Jenkins so I would prefer it to be disabled since
Gump is less user friendly and less documented than Jenkins - which
makes things harder.


A dump of the message I received:


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 apache-mailet has an issue affecting its community integration.
This issue affects 2 projects,
 and has been outstanding for 6 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - apache-mailet :  Apache Mailet API
    - apache-mailet-test :  Apache Mailet API

Full details are available at:

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages)
were provided:
 -INFO- Making directory for Maven settings:
 -DEBUG- (Apache Gump generated) Apache Maven Settings in:
 -INFO- Failed with reason build failed
 -DEBUG- Extracted fallback artifacts from Gump Repository

The following work was performed:
Work Name: build_apache-mailet_apache-mailet (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: /opt/maven3/bin/mvn --batch-mode -DskipTests=true
[Working Directory: /srv/gump/public/workspace/apache-mailet/api/trunk]
M2_HOME: /opt/maven3

Ioan Eugen Stan / CTO / http://axemblr.com

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

Reply via email to