Re: maven-release-plugin
Thanks for your helpful answer! The solution works fine: REM Dependency-Snapshot-Versions are replaced by the corresponding release version (e.g. 0.4.0-SNAPSHOT -- 0.4.0) call mvn versions:use-releases call svn commit REM Release Prepare and install to local repository call mvn -B release:prepare -Dtag=0.4.0 -DdevelopmentVersion=0.5.0-SNAPSHOT -DreleaseVersion=0.4.0 -DpreparationGoals=clean install REM Dependency-Release-Versions are replaced by the newest Snapshot-Version call mvn versions:use-latest-snapshots call svn commit -- View this message in context: http://maven.40175.n5.nabble.com/maven-release-plugin-update-dependency-snapshots-to-versions-in-batch-mode-tp3351425p3359398.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-release-plugin
I have the following problem releasing a project with the maven-release-plugin (version 2.1). I’m using the maven release plugin in batch-mode. When using the release plugin in interactive mode, the plugin prompts for the new versions of snapshot dependencies. How can I populate the versions (development + release) of snapshot dependencies running the mvn release:prepare command in batch-mode? I 've tried something like this: call mvn -B release:prepare -Dtag=0.4.0 \ -DdevelopmentVersion=0.5.0-SNAPSHOT -DreleaseVersion=0.4.0 \ -Ddependency.org.sonatype.mavenbook:project-a.release=0.4.0 \ -Ddependency.org.sonatype.mavenbook:project-a.development=0.5.0-SNAPSHOT and the pom content of project-b is as follows: http://maven.40175.n5.nabble.com/file/n3351425/pom.xml pom.xml -- View this message in context: http://maven.40175.n5.nabble.com/maven-release-plugin-tp3351425p3351425.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-release-plugin
No, it's a very simple project structure without any submodules. The problem are not any submodules, the problem is, that the dependency to project-a has a snaphot version at release time and needs to be updated to a release version. -- View this message in context: http://maven.40175.n5.nabble.com/maven-release-plugin-update-dependency-snapshots-to-versions-in-batch-mode-tp3351425p3351456.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
