ECTED] On
> Behalf Of Scott M Stark
> Sent: Tuesday, February 07, 2006 10:22 AM
> To: Max Andersen; Christian Bauer; development Hibernate;
> [EMAIL PROTECTED]
> Cc: jboss-development@lists.sourceforge.net
> Subject: RE: [Hibernate] Release naming conventions
>
> Any place the vers
e;
> [EMAIL PROTECTED]
> Subject: Re: [Hibernate] Release naming conventions
>
>
> so where do you want the name applied ?
>
> in the eclipse plugins it make sense for the jar's since that
> is the part being used to identify it + the
> plugin.xml/MANIFEST.MF osgi ver
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Max Rydahl Andersen
Sent: Tuesday, February 07, 2006 10:01 AM
To: Christian Bauer; development Hibernate;
[EMAIL PROTECTED]
Subject: Re: [Hibernate] Release naming conventions
>>
>> I'm not a big fan of all minor
Yes, I plan to start using these conventions starting with 3.2.
I'm not a big fan of all minor releases needing to append '.ga' (i.e.
3.1.3.ga.jar). I really wish there was a way to define ordering amongst
"qualifiers".
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
te;
> [EMAIL PROTECTED]
> Subject: Re: [Hibernate] Release naming conventions
>
> >>
> >> I'm not a big fan of all minor releases needing to append
> '.ga' (i.e.
> >> 3.1.3.ga.jar). I really wish there was a way to define ordering
> >&g
I'm not a big fan of all minor releases needing to append '.ga' (i.e.
3.1.3.ga.jar). I really wish there was a way to define ordering amongst
"qualifiers".
AFAIK these conventions are for package names and not necessarily
library names?
it's the version branded into the application - meani
On Feb 7, 2006, at 6:51 PM, Steve Ebersole wrote:
Yes, I plan to start using these conventions starting with 3.2.
I'm not a big fan of all minor releases needing to append '.ga' (i.e.
3.1.3.ga.jar). I really wish there was a way to define ordering
amongst
"qualifiers".
AFAIK these conven
