snapshot signature

[Jason van Zyl <ja...@zenplex.com>]

Hi,

While using the interactive editor I noticed that the snapshot signature
that has been used for deploying snapshots is probably not the best.
Currently the snapshots have been going up using: 

${artifactId}-${currentVersion}.${timestamp}.jar

And I would like to change this to:

${artifactId}-${timestamp}.jar

Where the the timestamp becomes the version. Period. This will make
things like searching for the latest version easier and just visually
surfing the repository will be easier as every project still uses widely
varying version naming conventions.

I would like to change the snapshot signature, deploy a bunch of
snapshots, run the the snapshot converter to modify the POMs for release
and then cut the release.

Any objections to the modification of the snapshot signature?

-- 
jvz.

Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society

Re: snapshot signature

[Jason van Zyl <ja...@zenplex.com>]

On Tue, 2003-02-11 at 08:55, Rafal Krzewski wrote:
> Jason van Zyl wrote:
> > While using the interactive editor I noticed that the snapshot signature
> > that has been used for deploying snapshots is probably not the best.
> > Currently the snapshots have been going up using: 
> > 
> > ${artifactId}-${currentVersion}.${timestamp}.jar
> > 
> > And I would like to change this to:
> > 
> > ${artifactId}-${timestamp}.jar
> 
> This could possibly be harmful with project like tomcat, where tomcat-3*
> is something wildly different than tomcat-4* and both of them are
> actively developed, and both are producing nightlies/shapshots.

These are in essence entirely different projects and only share the same
name. The same problem would exist with Turbine. They can always have
different directories in the repository as well. Say, tomcat-3 and
tomcat-4 as the artifactIds and even though there is some repetition in
the versioning the different families are kept apart in the repository.

> This could be worked around by including the major version into
> artifactId like 'tomcat4' or even 'tomcat-4'. This should work
> transparently with the current code, and the propsed change.
> 
> Overall, +0 from me.
> 
> R.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-maven-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-maven-dev-help@jakarta.apache.org
-- 
jvz.

Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society

Re: snapshot signature

[Colin Sampaleanu <co...@exis.com>]

Rafal Krzewski wrote:

>Jason van Zyl wrote:
>  
>
>>While using the interactive editor I noticed that the snapshot signature
>>that has been used for deploying snapshots is probably not the best.
>>Currently the snapshots have been going up using: 
>>
>>${artifactId}-${currentVersion}.${timestamp}.jar
>>
>>And I would like to change this to:
>>
>>${artifactId}-${timestamp}.jar
>>    
>>
>
>This could possibly be harmful with project like tomcat, where tomcat-3*
>is something wildly different than tomcat-4* and both of them are
>actively developed, and both are producing nightlies/shapshots.
>
>This could be worked around by including the major version into
>artifactId like 'tomcat4' or even 'tomcat-4'. This should work
>transparently with the current code, and the propsed change.
>
>Overall, +0 from me.
>  
>
The common name notwithstanding, these have become two separate 
products, so that's probably the only way you can really do it. So you'd 
have names like
  tomcat3-3.3.1
  tomcat4-4.1.18

The only question to me is how you handle the transition when a product 
splits off like this. Say you have 'productx', which has built up to a 
version 4
  productx-4.1.2
then you go to a major version 5 which gets a few versions
  productx-5.1.1
then somebody decides it's worth it to keep on working on the 4 series. 
How is that handled? Does it then become
  productx4-4.1.3

Seems like it would work, but I don't like the discontinuity in names... 
 This may not be that much of an issue, since often projects know from 
the beginning that they will break existing apis, e.g. xdoclet (1.x 
series), and xdoclet2 (2.x series)...

Re: snapshot signature

[Rafal Krzewski <Ra...@caltha.pl>]

Jason van Zyl wrote:
> While using the interactive editor I noticed that the snapshot signature
> that has been used for deploying snapshots is probably not the best.
> Currently the snapshots have been going up using: 
> 
> ${artifactId}-${currentVersion}.${timestamp}.jar
> 
> And I would like to change this to:
> 
> ${artifactId}-${timestamp}.jar

This could possibly be harmful with project like tomcat, where tomcat-3*
is something wildly different than tomcat-4* and both of them are
actively developed, and both are producing nightlies/shapshots.

This could be worked around by including the major version into
artifactId like 'tomcat4' or even 'tomcat-4'. This should work
transparently with the current code, and the propsed change.

Overall, +0 from me.

R.