RE: maven POM and snapshot jars in the project.xml

[Quinton McCombs <qm...@nequalsone.com>]

> -----Original Message-----
> From: Jason van Zyl [mailto:jason@zenplex.com] 
> Sent: Tuesday, March 04, 2003 1:22 PM
> To: Turbine Developers List
> Subject: RE: maven POM and snapshot jars in the project.xml
> 
> 
> On Tue, 2003-03-04 at 12:44, Quinton McCombs wrote:
> > We should be able to convert all of these to timestamped versions.
> > 
> > Another thing that we should do when we use timestamped or SNAPSHOT 
> > versions, it to add a comment in project.xml just before the 
> > dependency indicating the release of that aritifact.  For 
> example, the 
> > next release of torque will be 3.1.
> > 
> > It is unfortunate that Maven does not allow something like 
> > torque-3.1-SNAPSHOT to be used instead of torque-SNAPSHOT.
> 
> What's your use case for requiring the version as part of the 
> snapshot? It's not hard to add. This was being done before 
> but made the bidirection mapping between snapshots and 
> timestamped versions more difficult and I didn't really see 
> the need for the current version to be in their as snapshot 
> refers to an approximately HEAD build which is ignorant of 
> versioning. If you have a use case or requirement poke into 
> maven-dev or blow something into JIRA.
> 

Case 1:
In the cases, where I have used snapshots, it is not because I just want
to develop against the absolute latest version.  It is simply because I
need some functionality that will be included in the next release.  If
the snapshot has the release number included as part of the identifier,
it would be easy to spot snapshots that can be converted into the
released version when it becomes available.  

If I was the person who added the snapshot dependency, then I will know
what version I am waiting to be released.  Even then, I am likely to
forget.  Granted, this use case can be dealt with by simply adding
comments to the POM.

Case 2:
Some projects have multiple development version.  For example, Torque
has 3.0.1 and 3.1.  torque-SNAPSHOT can only point to one of them.

[OT] Re: maven POM and snapshot jars in the project.xml

["Jeffrey D. Brekke" <jb...@wi.rr.com>]

>>>>> On Tue, 4 Mar 2003 13:37:26 -0600, "Quinton McCombs" <qm...@nequalsone.com> said:

> Case 2: Some projects have multiple development version.  For
> example, Torque has 3.0.1 and 3.1.  torque-SNAPSHOT can only point
> to one of them.

As an aside of sorts, isn't this situation very confusing regardless
of snapshots and all that?  Although I'm a developer on both Turbine
and Torque, with my end-user hat on, I find it very confusing to track
multiple sub-versions of the same release, let alone snaps of those
versions.

I'm not sure I have a real point here, just observing something out
loud, wondering if any others viewed the situation in the same light.

I guess I wonder if multiple streams of development in the same
codebase is a *non*-best practice.  Short Releases?

Anyhow, carry on.
 
-- 
=====================================================================
Jeffrey D. Brekke                                   jbrekke@wi.rr.com
Wisconsin,  USA                                     brekke@apache.org
                                                    ekkerbj@yahoo.com