The 2.4 git problems are related to the release plugin ignoring local
checkout/disabling push settings primarily, so that your release is
tagged locally, but then MRP tries to clone the tag from upstream and fails.
Either way, dropping back to 2.3.2 to eliminate those issues would be a
good point of call.
One thing I've also noticed that sounds familiar, make sure you don't
have a release.properties in your working directory prior to a new
release - sometimes I've noticed it gets left behind somehow and
depending on whats in that file, MRP will "resume the release" from a
point where it thinks your version number has already been updated - and
thus releases/deploys a -SNAPSHOT to your release repo.
Mark
Robert Scholte wrote:
could you try to use maven-release-plugin 2.3.2?
There are some known issues with GIT and the maven-release-plugin 2.4,
which need to be fixed in the SCM project first.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
