ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yakov Zhdanov <yzhda...@apache.org>
Subject Re: EA versioning
Date Tue, 01 Dec 2015 15:10:56 GMT
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.vladykin@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 <raulk@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" <yzhdanov@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
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message