Re: We need to discuss version names for OSGi one last time.

2014-03-02 Thread Matt Sicker
I think we could just add .RELEASE to the OSGi version in the manifest. Simple. On 2 March 2014 19:56, Ralph Goers wrote: > Maven treats 2.0 or 2.0.0 very differently than 2.0.0-rc1. The first is > treated as numeric coordinates while the second is just a string. Once we > release 2.0 it is u

Re: We need to discuss version names for OSGi one last time.

2014-03-02 Thread Ralph Goers
Maven treats 2.0 or 2.0.0 very differently than 2.0.0-rc1. The first is treated as numeric coordinates while the second is just a string. Once we release 2.0 it is unlikely we would have another release with a string in it until perhaps 3.0. I would not recommend or be in favor of using 2.0.0

Re: We need to discuss version names for OSGi one last time.

2014-03-02 Thread Gary Gregory
On Sun, Mar 2, 2014 at 7:49 PM, Remko Popma wrote: > In that case I'd be fine with 2.0.0.RELEASE for the reasons you mentioned. > This is only for OSGi right? I'd hate to have to use that as Maven coords. Gary > > Sent from my iPhone > > On 2014/03/03, at 9:35, Matt Sicker wrote: > > Right.

Re: We need to discuss version names for OSGi one last time.

2014-03-02 Thread Remko Popma
In that case I'd be fine with 2.0.0.RELEASE for the reasons you mentioned. Sent from my iPhone > On 2014/03/03, at 9:35, Matt Sicker wrote: > > Right. You can specify this all as metadata. It's easier to use the same > version number as the Maven artefacts, but it doesn't have to be the same

Re: We need to discuss version names for OSGi one last time.

2014-03-02 Thread Matt Sicker
Right. You can specify this all as metadata. It's easier to use the same version number as the Maven artefacts, but it doesn't have to be the same at all. On 2 March 2014 18:16, Remko Popma wrote: > To clarify, whatever we decide on the OSGi version number string *only* > affects the value for

Re: We need to discuss version names for OSGi one last time.

2014-03-02 Thread Remko Popma
To clarify, whatever we decide on the OSGi version number string *only* affects the value for an OSGi-specific attribute in the manifest, right? (Not sure if this attribute exists in the manifest for all jar files or only for the OSGi ones.) So it doesn't affect the jar/zip file names. Correct?

We need to discuss version names for OSGi one last time.

2014-03-02 Thread Matt Sicker
Alright, I know I've brought this up a couple times, but this is also based on new information I've learned about the esoteric rules behind versioning in OSGi (which I'm pretty sure also applies to Maven; however, most people don't use version number ranges in Maven dependencies). Here's everythin