-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins on linux
When a Maven release is performed right after a previous one, then the proposed Release Version and Development Version are still the same as the previous ones.
For the versions to be updated, a build must be executed between two Maven releases.
I suspect that the versions aren't the only outdated information .
Maybe module dependencies should be updated as well after a successful build if the release task changes the pom in order to fix SNAPSHOTS versions (using the "prepare-with-pom" goal)
Is it possible to reparse poms after releasing the version. I've seen MavenModuleSetBuildExecution.parsePoms method, but it isn't public.