[Attn: Jeanfrancois] glassfish-api version has been changed from 10.0.3 to 10.0.400

View: New views
9 Messages — Rating Filter:   Alert me  

[Attn: Jeanfrancois] glassfish-api version has been changed from 10.0.3 to 10.0.400

by Sahoo :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Jeanfrancois,

I am curious to know why you changed [1] the version in glassfish-api
from 10.0.3 to 10.0.400 skipping so many intermediate numbers.

Thanks,
Sahoo

[1]
http://fisheye4.atlassian.com/browse/~br=trunk/glassfish-svn/trunk/v3/common/glassfish-api/pom.xml?r1=21371&r2=21377



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: [Attn: Jeanfrancois] glassfish-api version has been changed from 10.0.3 to 10.0.400

by Jerome Dochez :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I asked him to do that, we should now use 400, 401, 402 and so on...  
so we don't inflate the glassfish-api version number too fast.

jerome

On Jul 23, 2008, at 10:34 PM, Sahoo wrote:

> Jeanfrancois,
>
> I am curious to know why you changed [1] the version in glassfish-
> api from 10.0.3 to 10.0.400 skipping so many intermediate numbers.
>
> Thanks,
> Sahoo
>
> [1] http://fisheye4.atlassian.com/browse/~br=trunk/glassfish-svn/ 
> trunk/v3/common/glassfish-api/pom.xml?r1=21371&r2=21377
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: [Attn: Jeanfrancois] glassfish-api version has been changed from 10.0.3 to 10.0.400

by Sahoo :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I understand we have to now use 401, 402,..., but why did we jump to 400
from 3?

Thanks,
Sahoo

Jerome Dochez wrote:

> I asked him to do that, we should now use 400, 401, 402 and so on...
> so we don't inflate the glassfish-api version number too fast.
>
> jerome
>
> On Jul 23, 2008, at 10:34 PM, Sahoo wrote:
>
>> Jeanfrancois,
>>
>> I am curious to know why you changed [1] the version in glassfish-api
>> from 10.0.3 to 10.0.400 skipping so many intermediate numbers.
>>
>> Thanks,
>> Sahoo
>>
>> [1]
>> http://fisheye4.atlassian.com/browse/~br=trunk/glassfish-svn/trunk/v3/common/glassfish-api/pom.xml?r1=21371&r2=21377 
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: [Attn: Jeanfrancois] glassfish-api version has been changed from 10.0.3 to 10.0.400

by Jerome Dochez :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I did not want to confuse folks about 3 and 100, maybe that was not  
such a good idea. Anyhow I don't think it matters terribly if we  
switch back to snapshots at some point.
now there is a more important subject I would like to discuss : which  
version should we use for prelude, thereafter during development and  
finally for Java EE 6 release.

should we have something like :
        dev now : 10.0-SNAPSHOT
        milestones build : ?
        prelude : 10.1.x [x starts at 0 and is incremented as we deliver  
fixes to prelude]
        dev after prelude : 10.1.99-SNAPSHOT
        Java EE 6 release : 10.2.0

this of course does not have to be in sync with our product version  
but should be if possible.
Also do we  include the version in the jar file name we deliver ? I we  
do keep the version, we will most likely have several versions of the  
same jar in a particular installation, can we ensure that felix will  
always resolve to the latest one when import package with open range  
is specified.

jerome


On Jul 24, 2008, at 12:03 AM, Sahoo wrote:

> I understand we have to now use 401, 402,..., but why did we jump to  
> 400 from 3?
>
> Thanks,
> Sahoo
>
> Jerome Dochez wrote:
>> I asked him to do that, we should now use 400, 401, 402 and so  
>> on... so we don't inflate the glassfish-api version number too fast.
>>
>> jerome
>>
>> On Jul 23, 2008, at 10:34 PM, Sahoo wrote:
>>
>>> Jeanfrancois,
>>>
>>> I am curious to know why you changed [1] the version in glassfish-
>>> api from 10.0.3 to 10.0.400 skipping so many intermediate numbers.
>>>
>>> Thanks,
>>> Sahoo
>>>
>>> [1] http://fisheye4.atlassian.com/browse/~br=trunk/glassfish-svn/ 
>>> trunk/v3/common/glassfish-api/pom.xml?r1=21371&r2=21377
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: [Attn: Jeanfrancois] glassfish-api version has been changed from 10.0.3 to 10.0.400

by Sahoo :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Jerome Dochez wrote:
> I did not want to confuse folks about 3 and 100, maybe that was not
> such a good idea. Anyhow I don't think it matters terribly if we
> switch back to snapshots at some point.
> now there is a more important subject I would like to discuss : which
> version
For which artifact? glassfish-api or for all artifacts built as part of
v3. If you are asking for all artifacts, then this is what I was
thinking a few days back:
For all artifacts built out of v3, we would use 10.0.0 for prelude,
10.0.x for any patch/UR on top of prelude, 10.1.0 for release following
prelude, and 10.2.0 for the next next. Obviously, this won't work any
more, because we have already changed glassfish-api to use 10.0.1 :-( .

For all promoted builds and milestones, we can use qualifier.

Thanks,
Sahoo

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: [Attn: Jeanfrancois] glassfish-api version has been changed from 10.0.3 to 10.0.400

by Jerome Dochez :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


On Jul 24, 2008, at 12:34 AM, Sahoo wrote:

> Jerome Dochez wrote:
>> I did not want to confuse folks about 3 and 100, maybe that was not  
>> such a good idea. Anyhow I don't think it matters terribly if we  
>> switch back to snapshots at some point.
>> now there is a more important subject I would like to discuss :  
>> which version
> For which artifact? glassfish-api or for all artifacts built as part  
> of v3. If you are asking for all artifacts, then this is what I was  
> thinking a few days back:
> For all artifacts built out of v3, we would use 10.0.0 for prelude,
I am always confused with maven version as you can tell, but 10.0.0 is  
"after" 10.0-SNAPSHOT ?
> 10.0.x for any patch/UR on top of prelude,
yes so that follows what I was suggesting assuming we don't have to  
use 10.1.0 for prelude.
> 10.1.0 for release following prelude, and 10.2.0 for the next next.  
> Obviously, this won't work any more, because we have already changed  
> glassfish-api to use 10.0.1 :-( .
yes but that's ok, not all the modules have to have the same version  
for all of them. we will have to do something special for glassfish-
api for prelude, after it will fall back on the same scheme as the  
others.

>
>
> For all promoted builds and milestones, we can use qualifier.
>
> Thanks,
> Sahoo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: [Attn: Jeanfrancois] glassfish-api version has been changed from 10.0.3 to 10.0.400

by Stephen Connolly-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message



On Thu, Jul 24, 2008 at 8:39 AM, Jerome Dochez <Jerome.Dochez@...> wrote:

On Jul 24, 2008, at 12:34 AM, Sahoo wrote:

Jerome Dochez wrote:
I did not want to confuse folks about 3 and 100, maybe that was not such a good idea. Anyhow I don't think it matters terribly if we switch back to snapshots at some point.
now there is a more important subject I would like to discuss : which version
For which artifact? glassfish-api or for all artifacts built as part of v3. If you are asking for all artifacts, then this is what I was thinking a few days back:
For all artifacts built out of v3, we would use 10.0.0 for prelude,
I am always confused with maven version as you can tell, but 10.0.0 is "after" 10.0-SNAPSHOT ?

http://maven.apache.org/ref/current/maven-artifact/xref/org/apache/maven/artifact/versioning/DefaultArtifactVersion.html#50

1 == 1.0 == 1.0.0

So 10.0.0 is after 10-SNAPSHOT, 10.0-SNAPSHOT and 10.0.0-SNAPSHOT as a build with a qualifier is always before a build with a qualifier

 

10.0.x for any patch/UR on top of prelude,
yes so that follows what I was suggesting assuming we don't have to use 10.1.0 for prelude.

10.1.0 for release following prelude, and 10.2.0 for the next next. Obviously, this won't work any more, because we have already changed glassfish-api to use 10.0.1 :-( .
yes but that's ok, not all the modules have to have the same version for all of them. we will have to do something special for glassfish-api for prelude, after it will fall back on the same scheme as the others.



For all promoted builds and milestones, we can use qualifier.

Thanks,
Sahoo

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...



Re: [Attn: Jeanfrancois] glassfish-api version has been changed from 10.0.3 to 10.0.400

by Sahoo :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Stephen Connolly wrote:
>
> So 10.0.0 is after 10-SNAPSHOT, 10.0-SNAPSHOT and 10.0.0-SNAPSHOT as a
> build with a qualifier is always before a build with a qualifier
Did you want to say:
a build with a qualifier is always before a build *without* a qualifier?

Thanks,
Sahoo

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: [Attn: Jeanfrancois] glassfish-api version has been changed from 10.0.3 to 10.0.400

by Stephen Connolly-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

yes

Sent from my iPod

On 24 Jul 2008, at 17:55, Sahoo <sahoo@...> wrote:

>
> Stephen Connolly wrote:
>>
>> So 10.0.0 is after 10-SNAPSHOT, 10.0-SNAPSHOT and 10.0.0-SNAPSHOT  
>> as a build with a qualifier is always before a build with a qualifier
> Did you want to say:
> a build with a qualifier is always before a build *without* a  
> qualifier?
>
> Thanks,
> Sahoo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...