Thx Stefan,

We'd like to keep the existing James gumps projects.

Do we have commit right to gump metadata files, or do we have to send any change request to

Thx, Eric

On 05/12/2012 07:14, Ioan Eugen Stan wrote:
Thank you Stefan,

I've added Eric (PMC Chair James) in the loop. If it works right now
is great. Personally I don't have plans (time) to maintain Gump builds
if this proves too much of a hassle (for me). Documentation is missing
big time on this and I'm not a fan of missing documentation.

Other than that it's great that it works and I hope not to break it
again with the next pushes.


On Wed, Dec 5, 2012 at 7:22 AM, Stefan Bodewig <> wrote:
On 2012-12-04, Ioan Eugen Stan wrote:

We made some changes to the Apache James mailets project and now Gump
builds are failing.

Already fixed.

Where can we configure/disable Gump.

to configure - removing is a bit more complex than that since other
projects depend on mailet.

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.

Gump's and Jenkins' goals are different.  Jenkins won't be able to tell
you the JSieve build is broken because Mailet has "broken" MailetContext
by adding dnsLookup (or JSieve has failed to keep track):

Anyway, if there is consensus among the mailet devs that you want to
disable Gump builds, it can be done easily.



To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to