Re: how to enforce synchronization between source control and mvn deploy?
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
how to enforce synchronization between source control and mvn deploy?
hi, because development team is working with eclipse i want to ensure that source control and contents of repository are synchronized. that means: 1) if someone does mvn:deploy, i want to display a warning, if working copy is not up to date to source control 2) if someone wants to do a commit i want to enforce a deploy beforehand. - has anybody an idea how to bestly integrate this flow to subclipse? -does anybody see problems with this when using SNAPSHOTS (- one snapshot per commit). there is a maven scm plugin, but this cannot be configured to use above synchronizing rules. thanks for your thoughts. -- View this message in context: http://www.nabble.com/how-to-enforce-synchronization-between-source-control-and-mvn-deploy--tf4298166s177.html#a12233924 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to enforce synchronization between source control and mvn deploy?
I don't have an answer (not an eclipse user), but I do have a note on 2): Don't force a deploy beforehand - the SCM might fail - you want to deploy after (assuming no conflicts). Andy On 20 Aug 2007, at 12:08, aldana wrote: hi, because development team is working with eclipse i want to ensure that source control and contents of repository are synchronized. that means: 1) if someone does mvn:deploy, i want to display a warning, if working copy is not up to date to source control 2) if someone wants to do a commit i want to enforce a deploy beforehand. - has anybody an idea how to bestly integrate this flow to subclipse? -does anybody see problems with this when using SNAPSHOTS (- one snapshot per commit). there is a maven scm plugin, but this cannot be configured to use above synchronizing rules. thanks for your thoughts. -- View this message in context: http://www.nabble.com/how-to-enforce- synchronization-between-source-control-and-mvn-deploy-- tf4298166s177.html#a12233924 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
