I'm reading the maven release:prepare and noticed that it will not build because of SNAPSHOT dependencies. In my multiproject, I'm using a dependency that is currently in SNAPSHOT release and won't be upgraded for a while. Is there a way to bypass this since this 3rd party dependency's release version is out of my control?
-los Yann Le Du-4 wrote: > > Hi Los, > > maven-release-plugin is your friend : > http://maven.apache.org/plugins/maven-release-plugin/ > > Tag version and POM version must indeed match. > > - Yann > > 2007/1/11, moraleslos <[EMAIL PROTECTED]>: >> >> >> I'm about to tag my code in my repository to the maven-recommended >> x.x.x-yyyyy-z format-- probably at 1.0.0-alpha-1. I was wondering how >> this >> correlates to the version used in my POMs-- currently at 1.0-SNAPSHOT. >> Shouldn't they match, or are they suppose to be different? I'm new to >> the >> tagging/branching of code for release so if anyone has any suggestions, I >> would appreciate it. I just would like to know how maven2 can help >> facilitate in code releases since it has some project management >> functionality built in. Thanks in advance. >> >> -los >> -- >> View this message in context: >> http://www.nabble.com/Correlation-between-tagging-and-versioning-tf2957108s177.html#a8272307 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- View this message in context: http://www.nabble.com/Correlation-between-tagging-and-versioning-tf2957108s177.html#a8286933 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
