Christian Schulte wrote:
>
> The maven-scm-plugin may be helpful.
>
> <http://maven.apache.org/scm/maven-scm-plugin/update-mojo.html>
>
My first response to this was: didn't he read my comment:
> I've attempted adding stategies to check if the releasing developer
> (developer 2) is up-to-date, using buildnumber-maven-plugin. Unsuccessful,
> since release plugin does its own local modifications prior to running the
> buildnumber plugin.
>
But SCM may actually be a lot less aggressive than buildnumber. So it's
actually a great idea to use SCM instead!
Which is still a bit tricky is that it will update and silently leave behind
conflicts. For instance, I just tried a release without having updated my
POM properly, which resulted in having:
pom.xml (mangled)
pom.xml.mine
pom.xml.r14815
pom.xml.r14818
This works well: build fails anyway on the mangled pom.xml which is a sign
to the developer that he should have updated ;-)
This will be more problematic: something else than the POM is mangled and
does not get picked up by compile or test, and goes into my release :-(
All'n'all... a good start... still thinking on it!
Thanks for that.
--
View this message in context:
http://www.nabble.com/Up-to-date-release-tp20925759p20986559.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
