Some more observations: 1. It failed on pom checkin because my username was wrong (forgot -Dusername=). After rerunning this with the correct parameter, it failed because it tried to do a straight compile again (mentioned below). Shouldn't it have known from the release.properties that it was already past this step and just started from trying to checking again?
2. would be nice if I could say use the same version for all in a multiproject build 3. It removed the xmlns= and other info from the project tag. 4. Still removes comments from the pom. 5. the new development version default is empty: [INFO] What is the new development version for 'test.stchome.dsms.data.en.upgrad e:wv'? [] and actually uses this version in the poms: <version></version>. Further, I checked the code to see if there was a way to specify on the cli, but didn't find any. 6: it's still calling "m2" in release:perform, thus throwing the deprecated error. 1-4 are annoying but possibly manageable given that it's a beta. # 5 though seems to be a show stopper for me. It's pretty annoying (and error prone) to have to type the version 30 times to do a release. If there is a chance of getting #5 fixed before this release, then I'd vote for it, otherwise as it is now it's effectively no better for me than the old one (although it is obviously much improved everywhere else.). Alternatively, if we can release beta 5 soon after beta 4 with this fix and not have to wait for lots of other fixes, I'd be ok with that too. (and I'd be happy to supply some patches myself( -----Original Message----- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 11:15 AM To: Maven Developers List Subject: RE: [vote] Release Release plugin 2.0-beta-5 Still testing, but here's my initial observation: it looks like release:perform is doing a compile. If this is the first time this version has been built, it will fail in a multi project because sibling dependencies can't be found. Is there a reason not to do install? -----Original Message----- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 9:36 AM To: Maven Developers List Subject: RE: [vote] Release Release plugin 2.0-beta-5 +0 from this user. A few changes I would like to see: -- When running the project to verify that everything works correctly, it would be nice if batch mode was used. The first time I ran this, it decided to update a few plugins and I got a lot of 1/100K, 2/100K, ... lines displayed. -- It would be nice if the release:clean happened automatically after a dry run. If someone does a dry run and comes back to the project at a later date (maybe after working on several other projects) they may do a release:perform even though no actual preparation was performed. -- Comments were removed from my POMs for both the release and the next development versions. The "<?xml" was also removed. My POMs did not have the xmlns information in them. If this is a side effect of omitting the xmlns, then make sure that is CLEARLY documented. Other than these items, the plugin seems to run much better and is much easier to use. It is nice that the questions are asked without other garbage showing up between lines. -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, May 08, 2006 20:19 To: Maven Developers List Subject: [vote] Release Release plugin 2.0-beta-5 No, that's not a typo. I'd like to vote to release the release plugin. It has been completely rewritten since you last met it and now has over 250 unit tests covering everything. Nearly all of the JIRA issues have been closed - a select few were deferred to a 2.0 release. I'm working on a small set of docs right now, which I expect will be elaborated on for the 2.0 release. I've used it several times over the last few days and it seems to be going well. [ ] +1 [ ] +0 [ ] -1 Thanks, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. --------------------------------------------------------------------- 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]
