Yes that's one reason. I often go into that folder and do a top to bottom build or resolve all dependencies etc. Modules is a normal part of the build hierarchy and we should start axing it out because of a release plugin bug. If you want to comment it out so you can do your release and put it back after, then that's ok.
-----Original Message----- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Saturday, April 12, 2008 5:55 PM To: Maven Developers List Subject: Re: [regression] Cannot release plugins parent! Is that to prevent you from having to set up 39 individual projects in Hudson (or any other CI server) ? Brian E. Fox wrote: > Hudson uses this to detect the children so we need this in there. > > -----Original Message----- > From: Benjamin Bentmann [mailto:[EMAIL PROTECTED] > Sent: Saturday, April 12, 2008 8:47 AM > To: Maven Developers List > Subject: Re: [regression] Cannot release plugins parent! > >> What is the purpose of having a <modules> element for our plugins? > It's >> not like we want to build all plugins in one go, is it? > > Hudson used to do this if I remember correctly (the plugin ITs seem to > have > been removed recently). > > > Benjamin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
