[jboss-dev] ejb3 versioning

[Dimitris Andreadis]

AFAICT, the discussion went on unfinished and the one conclusion was not to use version 
ranges yet, in which case there is no reason to move to the maven versioning scheme.

Carlo de Wolf wrote:
> Are we doing Maven or not?
> 
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132665
> 
> public class VersionRangeTestCase
> {
>   @Test
>   public void testWithQualifier() throws Exception
>   {
>      VersionRange range = VersionRange.createFromVersionSpec("[1.0,)");
>          ArtifactVersion version = new DefaultArtifactVersion("1.0.0-ga");
>          assertTrue(range.containsVersion(version));
>   }
> 
>   @Test
>   public void testWithoutQualifier() throws Exception
>   {
>      VersionRange range = VersionRange.createFromVersionSpec("[1.0,)");
>          ArtifactVersion version = new DefaultArtifactVersion("1.0.0");
>          assertTrue(range.containsVersion(version));
>   }
> }
> 
> Carlo
> 
> Dimitris Andreadis wrote:
>> Modified:
>>    branches/Branch_5_x/component-matrix/pom.xml
>> -    <version.org.jboss.ejb3>1.0.0-CR2</version.org.jboss.ejb3>
>> +    <version.org.jboss.ejb3>1.0.0</version.org.jboss.ejb3>
>>
>> Rather than dropping GA as a suffix, why not discussing the issue first?
>>
>> Either we follow the rules or we provide arguments why they have to 
>> change:
>> http://www.jboss.org/community/docs/DOC-10725
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>