No response on the users list. Should I file a bug for this or is it expected behaviour?
/James -----Original Message----- From: Nord, James [mailto:[email protected]] Sent: 16 June 2009 11:21 To: Maven Users List Subject: release plugin? Hi all, Why if I specify exactly what versions to use for release and developement version for the exact module and specify the default values does the release plugin still try (and fail) to parse the versions? e.g. mvn.bat -B -X -e -Dproject.dev.test:test=X_1.0.1-SNAPSHOT -Dproject.rel.test:test=X_1.0.0 release:prepare (this is a single module project groupID=test artifactId=test) Apache Maven 2.1.0 (r755702; 2009-03-18 19:10:27+0000) Java version: 1.6.0_06 maven-release-plugin:2.0-beta-9 [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error parsing version, cannot determine next version: Unable to parse the version string: "X1.0.0-SNAPSHOT" at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:703) ... Caused by: org.apache.maven.plugin.MojoExecutionException: Error parsing version, cannot determine next version: Unable to parse the version string: "X1.0.0-SNAPSHOT" at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRelea seMojo.java:186) ... Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Error parsing version, cannot determine next versi on: Unable to parse the version string: "X1.0.0-SNAPSHOT" at org.apache.maven.shared.release.phase.MapVersionsPhase.getNextVersion(Ma pVersionsPhase.java:227) at org.apache.maven.shared.release.phase.MapVersionsPhase.execute(MapVersio nsPhase.java:140) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultRel easeManager.java:196) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultRel easeManager.java:133) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultRel easeManager.java:96) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRelea seMojo.java:182) ... 18 more Caused by: org.apache.maven.shared.release.versions.VersionParseException: Unable to parse the version string: "X1.0.0-SNAPSHOT" at org.apache.maven.shared.release.versions.DefaultVersionInfo.<init>(Defau ltVersionInfo.java:171) at org.apache.maven.shared.release.phase.MapVersionsPhase.getNextVersion(Ma pVersionsPhase.java:177) ... 23 more Fair enoguh if I haven't parsed in any versions as this version is in effect just a string qualifier (which is a valid version?) - but I have been explicit so what gives ? Would this be considered as a bug or would it be rejected due to the non-standard version. Regards, /James ************************************************************************************** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the [email protected] and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 ************************************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
