I disabled the multiple email option, lets see how that works out. -----Original Message----- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2008 10:45 AM To: Maven Developers List Subject: Re: Plugins at http://ci.sonatype.org/ needs to change
That's right. It's a limitation in hudson compared to continuum in which we can setup builds in the group level. Thus what are we doing ? One or several builds in Hudson ?? On Tue, Jul 29, 2008 at 4:01 PM, Brian E. Fox <[EMAIL PROTECTED]>wrote: > Its not just a case of setting them up one time, it's a case of having > to maintain many individual projects later, like if we want to change > the schedule or some other options. I personally don't care if it runs > all the plugins periodically even if they haven't changed...it's a good > sanity check against any repo changes (the local is flushed nightly). If > we disable the multiple warnings, it shouldn't matter how many times > they run. (and the build should have been set to every 4 hours or so > already but looks like it is now). We were also trying to reduce the > number of svn polls to the system as the infra didn't like many hits all > at once. Having a single project cuts down the polls by 30x (guessing on > the number of plugins). > > In short, I think there are many reasons to keep them together and only > one to keep them separate. > > -----Original Message----- > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 29, 2008 6:16 AM > To: Maven Developers List > Subject: Re: Plugins at http://ci.sonatype.org/ needs to change > > Right. > it's an error I forgot to fix when I copied the Maven Plugins project. > I fixed it for the eclipse plugin. > I'll create projects in hudson for others plugins this afternnon if you > want. > > > On Tue, Jul 29, 2008 at 11:58 AM, Benjamin Bentmann < > [EMAIL PROTECTED]> wrote: > > > Arnaud HERITIER wrote: > > > > (but it can be create by copy from the one I > >> just added : > https://ci.sonatype.org/job/maven-eclipse-plugin-trunk/). > >> > > > > Just a suggestion: We have Java 1.4 as the minimum requirement for all > the > > plugins, don't we? Then how about using a JDK 1.4 to run their ITs to > make > > sure we catch accidental usage of newer methods/classes? > > > > > > Benjamin > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > .......................................................... > Arnaud HERITIER > .......................................................... > OCTO Technology - aheritier AT octo DOT com > www.octo.com | blog.octo.com > .......................................................... > ASF - aheritier AT apache DOT org > www.apache.org | maven.apache.org > ........................................................... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .......................................................... Arnaud HERITIER .......................................................... OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .......................................................... ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ........................................................... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]