I have fixes in github for 6-7 issues, including stuff like http://jira.codehaus.org/browse/SUREFIRE-34 , 690, 703 and 704 and some "classic" strangeness in the reporting subsystem that isn't even reported as issues (yet). There is also a small group of minor cosmetic issues that should be fixed before releasing, preferably just scanning over issues >700.

I would be releasing sometime late next week, giving a nice round 5 weeks since 2.8, since I need a few more sessions of testing for my changes. If you release 2.8.1 now, I'll probably delay 2.8.2 another 3-4 weeks.

If you want to do an earlier release, feel free to do that. I'm not particularly invested in my particular schedule; i try to stick to 4-6 week interations (and It's 4 weeks on Monday ;)

Kristian



Den 06.04.2011 11:31, skrev Mark Struberg:
yah, nasty thing :(
+1 for a quick release.

txs and LieGrue,
strub

--- On Wed, 4/6/11, Olivier Lamy<[email protected]>  wrote:

From: Olivier Lamy<[email protected]>
Subject: surefire bug fix release 2.8.1 (SUREFIRE-722)
To: "Maven Developers List"<[email protected]>
Date: Wednesday, April 6, 2011, 9:24 AM
Hi Folks,
Just discovered yesterday an annoying (to be politically
correct :-) )
issue with surefire and testng with the implementation of
-Dtest=myClass#myTestMethod .
This issue prevent using the new feature when you need to
execute some
@Before* @After* stuff.

See http://jira.codehaus.org/browse/SUREFIRE-722

@Kristian : have you planned soon an other release for
surefire ? (or
I can do it)

Thanks !
--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

---------------------------------------------------------------------
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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to