AFAIK, in maven you can have versions with qualifiers, like 1.5.0-ea1 and standard versions, like 1.5.0.
According to this article [1], all the versions with a qualifier, such as “-ea” will be considered older than the versions without qualifiers. This means that 1.5.0-ea1 will be older than 1.5.0. Seems like the versioning scheme proposed by Yakov would work. [1] - https://docs.oracle.com/middleware/1212/core/MAVEN/maven_version.htm#MAVEN8855 D. On Tue, Dec 1, 2015 at 7:10 AM, Yakov Zhdanov <yzhda...@apache.org> wrote: > I have got the following output: > > $ java -cp maven-core-3.3.9.jar:maven-artifact-3.3.9.jar > org.apache.maven.artifact.versioning.ComparableVersion 1.5.0 1.5.0-EA1 > 1.5.0-final > > Display parameters as parsed by Maven (in canonical form) and comparison > result: > > 1. 1.5.0 == 1.5 > > 1.5.0 < 1.5.0-EA1 > > 2. 1.5.0-EA1 == 1.5-ea-1 > > 1.5.0-EA1 > 1.5.0-final > > 3. 1.5.0-final == 1.5 > > --Yakov > > 2015-12-01 18:07 GMT+03:00 Sergi Vladykin <sergi.vlady...@gmail.com>: > > > Also it is an interesting subject with respect to OSGi versioning because > > Maven and OSGi versions are > > somewhat conflicting as well. See [1] > > > > [1] http://versionatorr.appspot.com/?a=1.5.0-final&b=1.5.0-ea > > > > Sergi > > > > 2015-12-01 17:56 GMT+03:00 Raul Kripalani <ra...@apache.org>: > > > > > It is different when the keyword is part of the version > (1.1.1.RELEASE), > > > like Spring, and when it's a qualifier (1.1.1-RELEASE). > > > > > > Maven treats both cases differently. > > > On 1 Dec 2015 14:52, "Yakov Zhdanov" <yzhda...@apache.org> wrote: > > > > > > > Sergi, very good point! Guys, it seems that EA is not a good choice. > > > > > > > > However, how many of you have ever used RELEASE as version in maven > or > > > > version range? > > > > > > > > --Yakov > > > > > > > > > >
