Re: Release surefire 2.3.1?
Hi Mauro, Also, I would prefer an enforcer rule on the java version for the junit4 provider instead of getting javac error. BTW, is it really useful to compile with 1.4 this provider? Cheers, Vincent 2007/12/7, Mauro Talevi [EMAIL PROTECTED]: Dan Fabulich wrote: Nope. SUREFIRE-347 is regression: plexus is not properly isolated which is what I'd wish we'd fix before we release 2.3.1. Rolled back commits for 2.3.1 staging release and added regression issue to 2.3.1 target again. Any other issue that can be fixed by weekend should also be added of course. Cheers - 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]
Re: Release surefire 2.3.1?
Dan Fabulich wrote: Nope. SUREFIRE-347 is regression: plexus is not properly isolated which is what I'd wish we'd fix before we release 2.3.1. Rolled back commits for 2.3.1 staging release and added regression issue to 2.3.1 target again. Any other issue that can be fixed by weekend should also be added of course. Cheers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release surefire 2.3.1?
Brett Porter wrote: I was hesitant because at least one of them seemed to be a regression over 2.3. Anyway, my preference is to fix them first - but if someone is prepared to do a release - go for it. There's lots of good stuff in there already. I agree they should be fixed, but since no one has stepped forward to say that they're being worked on, I'll prepare release of what's currently there. I personally need some of the fixes released for at least one project. Cheers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release surefire 2.3.1?
I was hesitant because at least one of them seemed to be a regression over 2.3. Anyway, my preference is to fix them first - but if someone is prepared to do a release - go for it. There's lots of good stuff in there already. - Brett On 05/12/2007, at 2:13 PM, Dan Fabulich wrote: There are still three bugs targeted for 2.3.1. These bugs are there in 2.3 today, so I guess we could live with them for 2.3.1 and ship a fix in 2.3.2, but it sure would be nice to get those fixed. I think the bugs are currently assigned to Brett. Brett, are you still thinking about these bugs? -Dan - 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]
Re: Release surefire 2.3.1?
Did we ever remove the dependency on plexus-archiver, so we are just creating the manifest-only jar directly? I know you and I talked about it, Dan...I was just wondering. -john On Dec 4, 2007, at 10:13 PM, Dan Fabulich wrote: There are still three bugs targeted for 2.3.1. These bugs are there in 2.3 today, so I guess we could live with them for 2.3.1 and ship a fix in 2.3.2, but it sure would be nice to get those fixed. I think the bugs are currently assigned to Brett. Brett, are you still thinking about these bugs? -Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john rss: http://feeds.feedburner.com/ejlife/john
Re: Release surefire 2.3.1?
John Casey wrote: Did we ever remove the dependency on plexus-archiver, so we are just creating the manifest-only jar directly? I know you and I talked about it, Dan...I was just wondering. Nope. SUREFIRE-347 is regression: plexus is not properly isolated which is what I'd wish we'd fix before we release 2.3.1. -Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release surefire 2.3.1?
+1 for a 2.3.1 to make fixes available, and delay other issues to 2.3.2 / 2.4 With the no-SNAPSHOT limitation in the release plugin, maven plugin release cycle should be short ! Nico. 2007/12/4, Mauro Talevi [EMAIL PROTECTED]: Hi, as there have been a number of useful fixes since 2.3, and in line with the release early-release often, I wanted to gauge opinions about the opportunity to release 2.3.1 as currently in branch and postponing outstanding 2.3.1 issues to a 2.3.2. Unless these outstanding issues are being worked on and a fix is imminent. Cheers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Release surefire 2.3.1?
I say cut a release. The current surefire seems to work for most of my cases and building maven so it can't be too bad. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Mauro Talevi Sent: Tuesday, December 04, 2007 5:59 AM To: dev@maven.apache.org Subject: Release surefire 2.3.1? Hi, as there have been a number of useful fixes since 2.3, and in line with the release early-release often, I wanted to gauge opinions about the opportunity to release 2.3.1 as currently in branch and postponing outstanding 2.3.1 issues to a 2.3.2. Unless these outstanding issues are being worked on and a fix is imminent. Cheers - 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]
Re: Release surefire 2.3.1?
+1 for releasing 2.3.1 2007/12/4, Mauro Talevi [EMAIL PROTECTED]: Hi, as there have been a number of useful fixes since 2.3, and in line with the release early-release often, I wanted to gauge opinions about the opportunity to release 2.3.1 as currently in branch and postponing outstanding 2.3.1 issues to a 2.3.2. Unless these outstanding issues are being worked on and a fix is imminent. Cheers - 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]
Re: Release surefire 2.3.1?
+1 On Dec 4, 2007, at 6:58 AM, Mauro Talevi wrote: Hi, as there have been a number of useful fixes since 2.3, and in line with the release early-release often, I wanted to gauge opinions about the opportunity to release 2.3.1 as currently in branch and postponing outstanding 2.3.1 issues to a 2.3.2. Unless these outstanding issues are being worked on and a fix is imminent. Cheers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john rss: http://feeds.feedburner.com/ejlife/john
Re: Release surefire 2.3.1?
There are still three bugs targeted for 2.3.1. These bugs are there in 2.3 today, so I guess we could live with them for 2.3.1 and ship a fix in 2.3.2, but it sure would be nice to get those fixed. I think the bugs are currently assigned to Brett. Brett, are you still thinking about these bugs? -Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
