On Tue, Oct 21, 2008 at 6:01 PM, Bob Tiernay <[EMAIL PROTECTED]> wrote: > I get the sense that CI + Maven is a like wrestling with a slinky. Is this > problem endemic to s2? What do other open source projects do to alleviate > this?
The release process here could be *much* simpler, but it's really hard to change someone else's process. :) It's going to take someone to volunteer to be release manager and refine the process and the build once or twice. Compare to... http://cwiki.apache.org/ARCHIVA/archiva-release-process.html It really should be those two steps-- "mvn release:prepare" and "mvn release:perform" The first thing I'd do is flip things around so that everything builds by default, and use profiles to *exclude* things if necessary. But since I'm pretty sure that would break Bamboo, I won't do it. I will make time to help if someone wants to drive this. I think Maven and CI is pretty easy... Continuum or Hudson work fine, and they both have integration with Maven release. But CI may be problematic for releases here due to the PGP signing requirement-- you wouldn't want to put your private signing key on a shared CI server. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
