+1 from me. I think applying stuff with patches and small issues is important, but don't want to hold this up either. It should have been in the first release :)
Thanks for sorting it out Jason! Cheers, Brett Jason van Zyl wrote: > John Casey (Yahoo!) wrote: >> It looks like the maven-surefire-plugin has 5 open issues currently. >> One of them is the forking issue, another is related (but requires its >> own fix), and still another is outside the scope of the current >> release, IMO (testng support). Can we get those remaining 4 issues >> figured out before releasing the plugin? I think one even has a patch >> for it, or has a patch for surefire (SUREFIRE-11, IIRC) that we need >> to apply. > > Sure, I can look at them and see what's skaking. I'm mostly interested > in the forking which seems to be causing widespread grief and turmoil :-) > >> I guess once we patch for SUREFIRE-11 (or verify that it's fixed), I'm >> +1 for releasing surefire. >> >> As for the plugin, I'd like to get those four issues (not the testng >> one) fixed before we release. >> >> WDYT? >> >> -john >> >> Jason van Zyl wrote: >> >>> Hi, >>> >>> Surefire will now fork tests and I've updated the surefire plugin >>> accordingly so I think it's time for a release. >>> >>> +1 >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
