I also second the wish to take ALL sandbox plugins under CI, not only the actively maintained ones.
Does this make such a huge difference? I mean if no checkins happen to a plugin, then CI will not be triggered at all. And there should be no broken (compile or tests fail) plugin anyway! just my .02 LieGrue, strub ---------------------------------------------------------------- “Multiple exclamation marks are a sure sign of a diseased mind!” (Sir Terry Pratchett) --- Brett Porter <[email protected]> schrieb am Do, 8.1.2009: > Von: Brett Porter <[email protected]> > Betreff: Re: [mojo-dev] Aggregator POM for CI builds > An: [email protected] > Datum: Donnerstag, 8. Januar 2009, 0:31 > On 08/01/2009, at 7:20 AM, Benjamin Bentmann wrote: > > > For b), I created a dedicated aggregator POM in r8572 > [2] where we would list all those plugins that should take > part in the CI build. I assume that won't be all the > plugins currently under mojo/ but only those that are > actively maintained, i.e. get fixed when CI detects issues. > > > > Please feel free to comment. > > Does this mean they all get built in one go, or just a tool > to add them easily? > > I would be glad to know that all the non-sandbox plugins > always build, but when one fails I'd rather it > didn't affect the others. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
