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. Cheers, On Wed, Dec 5, 2012 at 7:22 AM, Stefan Bodewig <bode...@apache.org> 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. > > http://svn.apache.org/viewvc/gump/metadata/project/apache-mailet.xml?r1=1308018&r2=1416774 > >> Where can we configure/disable Gump. > > http://svn.apache.org/repos/asf/gump/metadata/project/apache-mailet.xml > > 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): > > http://vmgump.apache.org/gump/public/james-jsieve/james-jsieve/gump_work/build_james-jsieve_james-jsieve.txt > > Anyway, if there is consensus among the mailet devs that you want to > disable Gump builds, it can be done easily. > > Cheers > > Stefan -- 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
