> -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Lenz > Sent: 25 June 2003 14:36 > To: [EMAIL PROTECTED] > Subject: Re: Building Cactus with Maven -> I'd like to volonteer >
[snip] > > Not sure here. I'd say the requirements is that there is at least a > > nightly build done with recent versions of dependencies. I'm not sure it > > has to be done by gump though. But ok to start with this req. > > I'm sure the Maven community is planning the next big thing to replace > Gump ;-) > > Anyway, I'd consider moving away from Gump a very radical step. OTOH I > think > we have been stretching Gump a bit, by trying to make it generate our > nightly builds, publish our website, etc. > > I have been thinking about setting up CruiseControl somewhere to do > nightly > builds. In contrast to Gump, it'd use the lated released version of any > dependancy, because that's also the baseline for releases. It would upload > the files to our nightly build area, and publish the website, including > Clover coverage reports etc. So we'd have more reliable nightly builds and > website updates, while the integration builds would be performed by Gump. > > When moving towards a release, we could even promote an existing stable > nightly build to beta, rc or release status (similar to what the eclipse > guys do AFAIK). > > The only question is where that should be setup. I will probably start on > my > home machine, and see how well it goes. Sure. Using Maven and CruiseControl is something that I'd also like to try... while waiting for Continuum to appear... ;-) > > >>- I don't like the default Maven documentation/site style. It should > > be > >>possible to keep our current style, which we put a lot of work into. > > > > ... or improve the Maven style... ;-) > > Nah, I really dislike that so many of the Maven generated sites look > exactly > the same. Cactus is a Jakarta subproject, and should strive to keep a > somewhat consistent look with the rest of the family (too many subprojects > ignore this already, many of which have left the jakarta umbrella > recently). > > It's not that Maven doesn't allow pluggable styles, is it? I think you can provide your own stylesheet but I'll need to give it a closer look as I've never used that feature. > > > Honestly, my interest in moving the build to Maven is twice: > > - get a simpler build system for Cactus > > - at the same time, test and improve Maven using Cactus as a guinea pig. > > In other words, I trust in Maven but it has some rough edges and using a > > real and complex project to smoothen them is the best way to go I > > believe. > > If it makes the build simpler, cool. It will. > > If it's just about auto-downloading JAR files, we could also add an Ant > script similar to what the Tomcat folks have done. A benefit of that > approach is that the downloading is optional and only performed when the > user explicitly requests it. Same with Maven... :-) -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
