shouldn't release:branch still support this still though? If not that's bad as you will end up with a release version on the head of either the source branch or the new branch (and both should be used for ongoing development so should be snapshots...)
/James > -----Original Message----- > From: Stephen Connolly [mailto:[email protected]] > Sent: 28 March 2014 13:32 > To: Maven Users List > Subject: Re: maven release-plugin 2.5 bug - releasing snapshots... > > Let me rephrase. The release plugin is designed to make release versions. > It is not designed to make -SNAPSHOT versions. It was a bug that it let you > specify a -SNAPSHOT version as the release version. The bug has been fixed. > > > On 28 March 2014 13:18, ghostwolf59 > <[email protected]>wrote: > > > That's a way to general statement to be made - that also is incorrect ! > > > > A snapshot is not allowed for final release - but could still be > > released into a shapshot repo for test purposes ! > > The question really bogs down to how much control you'd like to have > > against a release snapshot. > > Anyone can in effect release a snapshot into the remote archiva > > snapshot repo but no scm branch tag would take place and the source > > this snapshot was based on would be unknown since uncommitted data > > could have been used. > > > > If you go down the path of controlling this (in selected cases) you'd > > like to have full control over the source it represent as well be able > > to assess the site info linked to this release. > > > > A simple mvn deploy would not do these things - it would only promote > > a local build into archiva's snapshot repository - with a lot of ??? > > to follow when it comes to QA, source control etc. > > > > > > I am not trying to do a "*/release/*" as such - it's a legit release > > of a > > */snapshot/* to be used for test purposed in a highly controlled > > manner pending official signoffs - once a signoff is received a proper > > release for that version would be performed. > > > > The final release would never be allowed to be a snapshot - nor would > > any snapshot dependencies be allowed but that's a side issue and have > > absolutely nothing to do with what I am arguing about. > > > > The snapshot release would end up in a dedicated snapshot repository > > so why you go down this path I don't really understand - bogs down to > > how v2.2.2 vs higher versions of the release-plugin behaves. > > > > I have now done some tests going back in history and it shows that all > > versions after *v.2.3.2* (my initial test was on v2.2.2) fails when it > > comes to this... > > > > So it appear that v 2.4 onwards all fail when it comes to this > > > > Succeeds: > > < > > http://maven.40175.n5.nabble.com/file/n5789892/release-version- > prompt- > > v.2.3.2.jpg > > > > > > > Failures; > > < > > http://maven.40175.n5.nabble.com/file/n5789892/release-version- > prompt- > > v.2.5-w.version.jpg > > > > > > > < > > http://maven.40175.n5.nabble.com/file/n5789892/release-version- > prompt- > > v.2.4.2.jpg > > > > > > > < > > http://maven.40175.n5.nabble.com/file/n5789892/release-version- > prompt- > > v.2.4.1.jpg > > > > > > > < > > http://maven.40175.n5.nabble.com/file/n5789892/release-version- > prompt- > > v.2.4.jpg > > > > > > > > > > > > > > > ----- > > good @ being sucked @ > > -- > > View this message in context: > > http://maven.40175.n5.nabble.com/maven-release-plugin-2-5-bug- > releasin > > g-snapshots-tp5789837p5789892.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] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
