Hi Reinhard! look for all <nag/> tags and comment them out, and that will stop the flow of e-mail. Note it isn't quite "spamming" -- cocoon requested these e-mails, really!
Please don't simply remove the files, they contain valuable gems of info! To work with the 2.1.x branch, if the build definitions that are currently in place for that branch are still correct (I suspect they might be, largely), you need to look for the svn URL in module.xml and change it, and then we need to manually get rid of existing checkouts. Alternatively, you could duplicate the module.xml tree with a "2.x" addition in there names (eg change names like cocoon-flow to cocoon-flow-2.x) to try and build both the 2.1 and trunk trees. Regarding the second question, I'm not sure of the maven 2 integration status; someone else will have to answer that... cheers, Leo On Wed, Apr 19, 2006 at 09:55:13AM +0200, Reinhard Poetz wrote: > Some time ago the Cocoon community decided to use Maven 2 as build system. > We also changed the directory structure and made our Ant build obsolete. > Because of this the Gump build has stopped to work and is spamming our > mailing list with failure reports every day. What do we need to do to > disable the Gump build for now? Is removing module.xml enough? > > What would we have to do to make the Gump build for our 2.1.x branch > working instead? (... though I'm not sure if there are any volunteers on > our side as we hope that the Maven 2 integration is coming soon). > > -- > Reinhard P?tz Independent Consultant, Trainer & (IT)-Coach --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
