We wrote a custom enforcer rule for maven-enforcer-plugin to check whether there is a newer revisions while maven was in install lifecycle (deploy lifecycle is to late to enforce, already deployed..). It wasn't that difficult but very helpful, it was really worth the work. You could for example use an SVN library and check with "svn status -u" in your custom enforcer rule or perhaps access maven-scm-plugin.
Greets Chris -----Ursprüngliche Nachricht----- Von: CloudStrife [mailto:jpell...@atti.com] Gesendet: Freitag, 15. Juli 2011 06:57 An: users@maven.apache.org Betreff: Re: how to enforce synchronization between source control and mvndeploy? Hi, Very old thread, but very relevant to me right now. :) I'd like to follow up on point 1. We have multiple dev groups collaborating on some artifacts. It seems like once in a while an SCM update is not done before mvn deploy. This is quite an easy trap to fall into, even if you do a clean checkout when starting your work (everyone does, right?), someone could have checked in some updates and deployed a new version before you do both. Maven should certainly allow enforcement of this - it's pretty easy to check the sync status with SCM. Is this available in 2.2.1? If not out of the box, how hard would it be to write some sort of hook to the mvn deploy:deploy-file? -- View this message in context: http://maven.40175.n5.nabble.com/how-to-enforce-synchronization-between-source-control-and-mvn-deploy-tp92391p4589368.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
