On 07/09/2007, at 2:00 PM, Jason van Zyl wrote:
On 6 Sep 07, at 12:17 PM 6 Sep 07, Brett Porter wrote:
Jason - you're aware of this?
Builds fine in Hudson and on my machine, you sure this isn't a
Continuum error?
This morning - no, it failed on my machine as well when I
bootstrapped to test a patch. I expect your last commits are fine and
will roll around next build. Due to the load on the box, they aren't
all that frequent.
It would also be a lot more helpful to turn on the blame mechanism.
Turn that on to mail/IM developers individually and it will be an
order of magnitude more effective. If you want to point it at my
mail for my commits feel free, or tell me what to put in the POM.
As I said before the more checks the better, but I find more often
then not I'm getting spammed or Continuum is not very robust at
dealing with heavy sets of changes.
We just have it set to go to [EMAIL PROTECTED] for now -
but sure, we can mail the people who've touched it since success as
well...
Removing modules or moving classes between modules seems to throw
it for a loop.
Yah, now that Maven isn't really "exporting" it's modules, maybe we
should set it up as a single build instead? Easy enough to do. Not
really a limitation of Continuum, just the way we have it configured.
Has the advantage of only building what changed (including dependency
changes), but has the downside that it won't detect removed modules,
and if you commit in between queued builds it might take a second
build to figure it out.
I'll put it on my list to change these couple of things.
Cheers,
Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
