Update:
WAGONSSH-40 is fixed, and wagon-ssh-1.0-alpha-7 has been released. Also,
the pom.xml for Maven 2.0.3-SNAPSHOT is updated to use this new version.
Also, would it be possible for someone with Win2K to look at MNG-1317?
I'm going to be trying to knock out MNG-1415 next.
Thanks,
John
John Casey wrote:
Binding: 9 (John, Jason, Vincent, Brett, Lukas, Emmanuel, Kenney,
Arnaud, Carlos)
Non-Binding: 6 (Brian, Fabrizio, Mike, Vincent S, Stephane, Allan)
HOWEVER, there has been quite a bit of talk about some issues that
should be included in this release. For that reason, I'm going to work
on them for a few more days, and call another vote. I'd like to have as
many interested parties on board as possible, especially since all of
the dissenters to this vote have brought up good points. :-)
From the vote thread, here are the issues and their respective status:
MNG-1317
---------
Emmanuel has no problem on WinXP, but this has not been verified or
marked fixed. Can anyone help us verify/fix this?
MNG-1415
---------
I haven't had time to look at this, beyond the proposed fix in the issue
itself...which seems sane to me. I just want to be sure that (a) I can
duplicate the issue on my linux box, and (b) the fix actually works
cleanly. I don't anticipate problems here, but haven't had time to
integrate that fix yet.
WAGONSSH-36
------------
This is fixed in SVN, and will be released in wagon-ssh-1.0-alpha-7,
which will be included in Maven 2.0.3. The reason I haven't released
this new version of wagon-ssh yet is that we're still looking at a
possible fix for WAGONSSH-40.
WAGONSSH-40
------------
Not sure where this got brought into the release discussion (probably on
IRC), but this is another of those important bugs on SSH, and we should
probably try to get the fix into 2.0.3 if we can (particularly since SSH
is the de facto standard for doing Maven deployments right now). I
haven't had time to look at this one either, but plan to take a look
tonight if I can. If anyone else has some time that they could use to
document the steps to reproduce, or even better, submit a fix, I'd be
grateful for the help.
(no JIRA) Setting plugin parameters on the command line
--------------------------------------------------------
I spent a good deal of time trying to reproduce this on Friday, with
Brian Fox's help, and our conclusion was that this was not a bug in
Maven. If someone can submit a test case we can use - filed in a jira
issue, preferably - then I'll consider this a blocker for 2.0.3.
Otherwise, I'm going to consider this some sort of user-environment
problem and move on.
MNG-2054 & MNG-2068
--------------------
As Brian mentioned, he uncovered two other jira issues which were fixed
for 2.0.3, but which hadn't been marked as fixed. I've incorporated two
new integration tests - it0096 and it0097, respectively - to test these
cases. Thanks for doing the legwork on that, Brian.
So, that's the status as of this morning. I'm going to try to set aside
some time tonight and tomorrow to get these outstanding issues fixed if
I can, and will probably call another vote on Thursday or Friday. I'd
like to get this release out early next week, since it's going to be
holding up a release of Continuum soon.
Thanks,
John
John Casey wrote:
Hi,
I think it's time to release Maven 2.0.3. This release will
incorporate 21 resolved JIRA issues, including some critical fixes for
Continuum and users of the embedder. The full listing of fixes can be
found here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=12107
The remaining open issues are reminders for the site publishing
process which should accompany this binary release.
If you're interested, you can take the current release candidate for a
test drive. The RC tarball is at:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060222.031501.tar.gz
I'll leave the vote open for the customary 72 hours before
summarizing. Please cast your vote as:
[ ] +1 Yes, release
[ ] 0 No opinion
[ ] -1 No, don't release
Here's my +1.
Cheers,
John
---------------------------------------------------------------------
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]
