Hi,
Let me join this thread, because that "someone" is me. As said by Stephen:
the version handling prior to 2.4 contained several issues, so you were
relying on a bug.
This has all been done as part of MRELEASE-511[1] and related issues.
There is no such thing as a "formal SNAPSHOT": it's a formal release or a
SNAPSHOT, not both.
If you want the release to be formal, use version patterns with alpha,
beta, milestone or release candidate as supported by Maven (through
Aether)[2]
If you want to upload to the SNAPSHOT repository, just "deploy" the
development version
If you want a tag/branch, either use release:branch, scm:branch or
scm:tag[3]
Keep in mind: the difference in behavior between a release and a SNAPSHOT.
And versions are considered cheap nowadays.
thanks,
Robert
[1] https://jira.codehaus.org/browse/MRELEASE-511
[2]
http://sonatype.github.io/sonatype-aether/apidocs/org/sonatype/aether/util/version/GenericVersionScheme.html
[3] http://maven.apache.org/scm/maven-scm-plugin/
Op Fri, 28 Mar 2014 15:12:54 +0100 schreef ghostwolf59
<[email protected]>:
Doing it as I explained did NOT allow you to do a release or refer to it
within other resources during a legic release phase
What you triggered was a release (as if legit) to go into the snapshot
repo
- cant see any issues with that kind of behavior and have turned out to
be
very useful when implementing formal test signoffs where exact version
tested against become critical (mind you these test phases is done before
even taken the app to UAT - technically still in a development phase).
Allowing these "formal" snapshots releases to be released into the
snapshot
repo can hardly affect the normal behavior of releasing local builds
(without any constraint of the build was done against committed data - as
it's currently works)
From what I hear is that someone decided to plug this "feature" =
personally
(and form an organizational point of view I think you removed useful
functionality)
Next question: if this now is a planned move - why not allow snapshots
(that
maven does on local uncommitted data) to be processed as if it actually
is
somewhat legit - without open up the possibility to use this as a prod
state
resource in the dependency sections ?
-----
good @ being sucked @
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-release-plugin-2-5-bug-releasing-snapshots-tp5789837p5789916.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]
