Hi,
BTW the behaviour of Maven's version comparision can be simply
shown by using the following:
java -jar /usr/local/apache-maven-3.3.9/lib/maven-artifact-3.3.9.jar
2.0-alpha-1 2.0-SNAPSHOT
Display parameters as parsed by Maven (in canonical form) and comparison
result:
1. 2.0-alpha-1 == 2-alpha-1
2.0-alpha-1 < 2.0-SNAPSHOT
2. 2.0-SNAPSHOT == 2-snapshot
Kind regards
Karl Heinz Marbaise
PS.: This is part of Maven since Maven
3.2.5(https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12330189).
On 23/09/16 22:29, Karl Heinz Marbaise wrote:
Hi,
On 23/09/16 18:38, Robert Patrick wrote:
What I am questioning is the "engineer's approach" to version range
resolution without
a valid use case for why Maven should consider
pre-released versions as within the "not including 2.0" version
range semantics.
The simple answer to this is the timeline of those releases...
So a pre-release (2.0-alpha-1, 2.0-RC1 etc.) will be done before the
final release (2.0) so must be defined as before...
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
