Agreed I am trying to push I the right direction. Regardless what if I have a 1.0-SNAPSHOT and I want to update to 1.0 and release. Then move 1.0 after the release to 1.1-SNAPSHOT.
Again going in the right direction i am trying to do things as the release plugin does but I cannot use the release plugin directly, as my multi module project has modules from different svn repo locations. Please keep an open mind on this. I work in a sensitive env and some of our code base absolutely must be in a different repo with no exceptions. In the end am I out of luck using the update-versions goal such the I update from a SNAPSHOT to a release back to a SNAPSHOT? Thanks again. Sent from my iPhone On Sep 6, 2012, at 10:55 PM, Wayne Fay <[email protected]> wrote: >> my projects. However my company does not set SNAPSHOT versions in all >> projects. I know, I know this is a bad habit but one in which I do >> not have full control over at the moment :( > > This is eventually going to be a very large problem for you or someone > at your company (most likely), and you will regret the decisions which > allowed this situation to occur in the first place. > > Honestly, you need to fix this ASAP for a number of reasons. > > Wayne > > --------------------------------------------------------------------- > 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]
