ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: EA versioning
Date Tue, 01 Dec 2015 18:55:55 GMT
What would the “final” qualifier give us? From what I can see, Maven
version comparison will work fine without it. Does maven have special
handling for the “final” suffix?

On Tue, Dec 1, 2015 at 10:36 AM, Raul Kripalani <raulk@apache.org> wrote:

> On Tue, Dec 1, 2015 at 5:57 PM, Sergi Vladykin <sergi.vladykin@gmail.com>
> wrote:
>
> > Thanks, Raul! I like your synthesis.
> >
> > We have already agreed to use 1.5.0-*b1* format for early access builds,
> > but I did not see any opinions about *final* for releases.
> > Does anyone have objections to use *final *qualifier for release builds
> to
> > conform both OSGi and Maven versioning?
> >
>
> There is also the possibility to drop the qualifier in package exports
> (Bundle-Version can stay as-is).
> But I don't like this, we'd be losing information, it leads to possibly
> incoherent environments and it's confusing.
> I just wanted to mention it for the sake of completeness.
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>

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