问题
I try this command (with dryrun to test) on my maven project :
mvn release:clean release:prepare -DdryRun=true -DgenerateBackupPoms=false -Dtag=solocal-refentreprive-2.1-RC02 -DreleaseVersion=2.1-RC02 -DdevelopmentVersion=2.1-SNAPSHOT
at the end, the build is success, but i have (in my commit) many pom.next / pom.tag and pom.backUp....
i don't when then (-DgenerateBackupPoms=false), if i use without dryrun i dont want push this pom...
Thx,
回答1:
Assuming you accept the defaults release:prepare performs the following
1) build and check all tests pass
2) check there are no SNAPSHOT dependencuies
3) change the version from x.x-SNAPSHOT to x.x
4) push to a tag in SCM
5) change the version for the next iteration to x.(x+1)-SNAPSHOT
So your pom.backUp is the original pom, your pom.tag is from step 3 and your pom.next is from step 5.
You can clean up with a mvn release:clean which will be done automatically after a release:perform see maven-release
回答2:
Maybe it's late, but based on your question you haven't run mvn release:perform after the mvn release:prepare command.
Don't forget to finish your release process with the perform command. https://maven.apache.org/maven-release/maven-release-plugin/plugin-info.html
Or if you don't want to use perform, use should use the mvn release:clean again.
来源：https://stackoverflow.com/questions/43472914/how-to-use-properly-mvn-releaseprepare