Fabrizio Giustina wrote:
while testing this I found http://jira.codehaus.org/browse/SUREFIRE-444 I verified that the bug was still in 2.4 and I am not sure how many users can be affected... since it can breaks builds without providing any useful information about the cause I'd like it to be included as soon as possible (either in 2.4.1 or in a very near 2.4.2)
I've added comments to SUREFIRE-444. I think this only happens on versions of TestNG that are pretty old (not sure exactly how old, because I'm not sure what version of TestNG you're using), but I'm not 100% certain of that.
While I kinda expected 2.4.1 to be necessary not long after 2.4 shipped, I'm not expecting 2.4.2 to arrive soon. We could probably let this bug slip, but it's hard to assess its impact clearly, and it's easier to just roll another candidate. :-(
-Dan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
