Make the change to the version in the pom file its own commit in the release branch and immediately "fake" merge it back to the development branch (merge --strategy=ours
).
https://stackoverflow.com/a/19794987/11296
Once that commit is merged (even fake merged) back into the development, its change won't be included in future merges back into development (until the pom file is changed again).
Note, if you have any commits on the release branch before the version-change commit, make sure you "real" merge those first, and then fake merge the version-change commit (and then real merge the future real changes, then fake the future version changes, rinse-and-repeat ...).