We can open this up for discussion.
This is the reason I just sent it to myself for now. But we do have a
copy of Continuum running on the Maven zone that can be used (its out of
date right now - it will be updated tomorrow for the new release).
There are limitations with the current Maven 1.x support of extended
projects so it may not be immediately viable for all projects (though
certainly the Ant builds can be run through it with the additional
configuration).
Another concern is the possible duplication of nags with gump (though
obviously these are significantly different approaches, they are both
going to complain if it is broken).
For now, I'll leave this one going to me for testing. From there, I
think it should be up to the individual components, including what build
intervals are appropriate if it is to go to the dev list.
Cheers,
Brett
Rahul Akolkar wrote:
On 10/24/05, Dion Gillard <[EMAIL PROTECTED]> wrote:
Can we make these go to the dev list please??
<snip/>
Continuum will generate a fair bit of traffic, especially if many
Commons components take it up. IMO, given the nature of Commons,
subscribing build statuses / integration results to the dev list might
not have as much value as, say, bugzilla reports and cvs/svn commits.
Maybe only the developers listed in the project POM should be
notified?
Yes, I can filter emails :-) Just trying to gauge the broader opinion,
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
