You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@maven.apache.org by EJ Ciramella <ec...@upromise.com> on 2008/11/18 18:31:05 UTC

specifying "latest" for a dependency

I know this has been discussed time and time again, but I can't seem to
combine the right google keywords to find what I'm looking for.
 
How do you specify "latest" for a dependency?

RE: specifying "latest" for a dependency

Posted by Todd Thiessen <th...@nortel.com>.

Well, all builds are fixed.  Thus all builds are snapshots, including released builds. There is nothing intrinsic in the definition of the word snapshot which indicates that it is meant for developers only.

I am sure you are used to it by now, but I have little doubt that this is a source of confusion to new users of maven.

---
Todd Thiessen

-----Original Message-----
From: David Delbecq [mailto:delbd@oma.be] 
Sent: Wednesday, November 19, 2008 11:17 AM
To: Maven Users List
Subject: Re: specifying "latest" for a dependency

En l'instant précis du 19/11/08 17:01, Todd Thiessen s'exprimait en ces
termes:
>
> I think my biggest confusion was the naming convension here. The term 
> "SNAPSHOT" typically means a fixed state of something at a particular 
> point in time. However, in Maven it isn't fixed at all. It is in 
> constant flux. A better name for SNAPSHOT would of been something like 
> LATEST-DEV.
>   
>
I see no confusion. More over, snapshot are fixed. What you did not fix however, in your pom it which snapshot to use, so maven choose to download the latest snapshot. SNAPSHOT is a good term for an automated daily build. LATEST-DEV would be more, to me, like asking maven to connect to version control an do a build from it.

Example of using a fixed snapshot:

<version>1.0-beta-3-20080505.072643-6</version>

This will fix dependency to that explicit snapshot made on 05/05/2008 of
1.0-beta3
while
<version>1.0-beta3-SNAPSHOT</version>
will point always to latest snapshot of 1.0-beta3

--
David Delbecq
ICT
Institut Royal Météorologique
Ext:557


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: specifying "latest" for a dependency

Posted by David Delbecq <de...@oma.be>.

En l'instant précis du 19/11/08 17:01, Todd Thiessen s'exprimait en ces
termes:
>
> I think my biggest confusion was the naming convension here. The term
> "SNAPSHOT" typically means a fixed state of something at a particular
> point in time. However, in Maven it isn't fixed at all. It is in
> constant flux. A better name for SNAPSHOT would of been something like
> LATEST-DEV.
>   
>
I see no confusion. More over, snapshot are fixed. What you did not fix
however, in your pom it which snapshot to use, so maven choose to
download the latest snapshot. SNAPSHOT is a good term for an automated
daily build. LATEST-DEV would be more, to me, like asking maven to
connect to version control an do a build from it.

Example of using a fixed snapshot:

<version>1.0-beta-3-20080505.072643-6</version>

This will fix dependency to that explicit snapshot made on 05/05/2008 of
1.0-beta3
while
<version>1.0-beta3-SNAPSHOT</version>
will point always to latest snapshot of 1.0-beta3

-- 
David Delbecq
ICT
Institut Royal Météorologique
Ext:557


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: specifying "latest" for a dependency

Posted by Stephen Connolly <st...@gmail.com>.

OK, I'll clarify want I meant.

There are two "special" version numbers: LATEST and RELEASE.

AFAIK

Where LATEST corresponds to "the latest version according to the Maven
Repository Metadata (and I don't mind snapshots)"
and RELEASE corresponds to "the latest released version according to the
Maven Repository Metadata".

Furthermore, AFAIK, these _magic_ versions only work when specifying the
version of a plugin (as you are not allowed to use version ranges in
specifying the version of a plugin)

The _magic_ version strings do not work in the version section of a
dependency, as you can use version ranges there.

On top of all of that, you would not want to use these magic strings anyway,
as the Maven Repository Metadata thinks that the latest version is the last
one that was deployed... so if you publish foo-maven-plugin versions 1.0,
2.0, 1.1 in order then RELEASE will correspond to 1.1 and not the 2.0 that
you think it does!!! ;-)

-Stephen

2008/11/19 Yanko, Curtis <cu...@uhc.com>

> Maven supports the idea of latest if you use version ranges no? So at
> least for a given milestone you can grab the latest release of a given
> component.
>
>
> ==========
> Curtis Yanko
> Application & Developer Infrastructure Services
> Source->Build->Deploy
> W: 860.702.9059
> M: 860.881.2050
>
> -----Original Message-----
> From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> Sent: Wednesday, November 19, 2008 11:08 AM
> To: Maven Users List
> Subject: Re: specifying "latest" for a dependency
>
> Those special values, AFAIK are for plugin versions only.... and are
> depricated
>
> 2008/11/19 Todd Thiessen <th...@nortel.com>
>
> > Thanks for the reply. I do understand that SNAPSHOT is meant for
> > developers only.  I did read here:
> >
> > http://books.sonatype.com/maven-book/reference/pom-relationships.html#
> > d0
> > e9801<http://books.sonatype.com/maven-book/reference/pom-relationships
> > .html#d0e9801>
> >
> > that LATEST means the latest SNAPSHOT or RELEASED version and a
> > version of RELEASED means the latest RELEASED version.  I tried
> > playing with these as version values but the artifact couldn't be
> > found.  I did have success using no upper bound on range however.
> >
> > I think my biggest confusion was the naming convension here. The term
> > "SNAPSHOT" typically means a fixed state of something at a particular
> > point in time. However, in Maven it isn't fixed at all. It is in
> > constant flux. A better name for SNAPSHOT would of been something like
>
> > LATEST-DEV.
> >
> >
> > ---
> > Todd Thiessen
> >
> > -----Original Message-----
> > From: Simone Gianni [mailto:simoneg@apache.org]
> > Sent: Wednesday, November 19, 2008 9:19 AM
> > To: Maven Users List
> > Subject: Re: specifying "latest" for a dependency
> >
> > Hi Todd,
> > SNAPSHOT is different from latest, because a SNAPSHOT is unstable,
> > pre-alpha stuff, not the latest known working released version. This
> > is a critical distinction, many projects use and publish SNAPSHOTS for
>
> > internal use (for example, if I have three modules, they all evolve
> > simultaneously, so they depend on the snapshot of each other until we
> > arrive to a release).
> >
> > To get the latest one, simply put no upper bound to a version range.
> > This will avoid SNAPSHOTS, and get the highest available version. And
> > yes, only the first three are considered numbers. Obviously this is
> > not perfect, because every organization can setup a standard with one,
>
> > two, three, four or one hundred numbers. Anyway the three numbers are
> > quite considered a de-facto standard, and used in 90% of software
> development.
> >
> > So, I would suggest to stick with 3 (major, minor, rev) number, and
> > use the fourth if needed for stuff like ALPHA, BETA, RC1, RC2 (or OSGI
>
> > timestamp), remembering that if your development practice often brings
>
> > you to RC10 or above, you should number them 01, 02 etc...
> >
> > Simone
> >
> > Todd Thiessen wrote:
> > > Snapshot versions work this way. Perhaps this is what you are
> > > looking for.
> > >
> > > I was confused by this too btw. I think snapshot would of been
> > > better named as "lastest".
> > >
> > > I don't know if you can do this with release versions though. It
> > > would
> >
> > > be nice to always get the latest release.
> > >
> > >
> > > ---
> > > Todd Thiessen
> > >
> > > -----Original Message-----
> > > From: EJ Ciramella [mailto:eciramella@upromise.com]
> > > Sent: Tuesday, November 18, 2008 12:31 PM
> > > To: users@maven.apache.org
> > > Subject: specifying "latest" for a dependency
> > >
> > > I know this has been discussed time and time again, but I can't seem
>
> > > to combine the right google keywords to find what I'm looking for.
> > >
> > > How do you specify "latest" for a dependency?
> > >
> > > --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> > --
> > Simone Gianni            CEO Semeru s.r.l.           Apache Committer
> > http://www.simonegianni.it/
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or entity
> to which it is addressed. If the reader of this e-mail is not the intended
> recipient or his or her authorized agent, the reader is hereby notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify the
> sender by replying to this message and delete this e-mail immediately.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

RE: specifying "latest" for a dependency

Posted by "Yanko, Curtis" <cu...@uhc.com>.

Maven supports the idea of latest if you use version ranges no? So at
least for a given milestone you can grab the latest release of a given
component. 


==========
Curtis Yanko
Application & Developer Infrastructure Services
Source->Build->Deploy
W: 860.702.9059
M: 860.881.2050

-----Original Message-----
From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com] 
Sent: Wednesday, November 19, 2008 11:08 AM
To: Maven Users List
Subject: Re: specifying "latest" for a dependency

Those special values, AFAIK are for plugin versions only.... and are
depricated

2008/11/19 Todd Thiessen <th...@nortel.com>

> Thanks for the reply. I do understand that SNAPSHOT is meant for 
> developers only.  I did read here:
>
> http://books.sonatype.com/maven-book/reference/pom-relationships.html#
> d0 
> e9801<http://books.sonatype.com/maven-book/reference/pom-relationships
> .html#d0e9801>
>
> that LATEST means the latest SNAPSHOT or RELEASED version and a 
> version of RELEASED means the latest RELEASED version.  I tried 
> playing with these as version values but the artifact couldn't be 
> found.  I did have success using no upper bound on range however.
>
> I think my biggest confusion was the naming convension here. The term 
> "SNAPSHOT" typically means a fixed state of something at a particular 
> point in time. However, in Maven it isn't fixed at all. It is in 
> constant flux. A better name for SNAPSHOT would of been something like

> LATEST-DEV.
>
>
> ---
> Todd Thiessen
>
> -----Original Message-----
> From: Simone Gianni [mailto:simoneg@apache.org]
> Sent: Wednesday, November 19, 2008 9:19 AM
> To: Maven Users List
> Subject: Re: specifying "latest" for a dependency
>
> Hi Todd,
> SNAPSHOT is different from latest, because a SNAPSHOT is unstable, 
> pre-alpha stuff, not the latest known working released version. This 
> is a critical distinction, many projects use and publish SNAPSHOTS for

> internal use (for example, if I have three modules, they all evolve 
> simultaneously, so they depend on the snapshot of each other until we 
> arrive to a release).
>
> To get the latest one, simply put no upper bound to a version range.
> This will avoid SNAPSHOTS, and get the highest available version. And 
> yes, only the first three are considered numbers. Obviously this is 
> not perfect, because every organization can setup a standard with one,

> two, three, four or one hundred numbers. Anyway the three numbers are 
> quite considered a de-facto standard, and used in 90% of software
development.
>
> So, I would suggest to stick with 3 (major, minor, rev) number, and 
> use the fourth if needed for stuff like ALPHA, BETA, RC1, RC2 (or OSGI

> timestamp), remembering that if your development practice often brings

> you to RC10 or above, you should number them 01, 02 etc...
>
> Simone
>
> Todd Thiessen wrote:
> > Snapshot versions work this way. Perhaps this is what you are 
> > looking for.
> >
> > I was confused by this too btw. I think snapshot would of been 
> > better named as "lastest".
> >
> > I don't know if you can do this with release versions though. It 
> > would
>
> > be nice to always get the latest release.
> >
> >
> > ---
> > Todd Thiessen
> >
> > -----Original Message-----
> > From: EJ Ciramella [mailto:eciramella@upromise.com]
> > Sent: Tuesday, November 18, 2008 12:31 PM
> > To: users@maven.apache.org
> > Subject: specifying "latest" for a dependency
> >
> > I know this has been discussed time and time again, but I can't seem

> > to combine the right google keywords to find what I'm looking for.
> >
> > How do you specify "latest" for a dependency?
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> Simone Gianni            CEO Semeru s.r.l.           Apache Committer
> http://www.simonegianni.it/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: specifying "latest" for a dependency

Posted by Stephen Connolly <st...@gmail.com>.

Those special values, AFAIK are for plugin versions only.... and are
depricated

2008/11/19 Todd Thiessen <th...@nortel.com>

> Thanks for the reply. I do understand that SNAPSHOT is meant for
> developers only.  I did read here:
>
> http://books.sonatype.com/maven-book/reference/pom-relationships.html#d0
> e9801<http://books.sonatype.com/maven-book/reference/pom-relationships.html#d0e9801>
>
> that LATEST means the latest SNAPSHOT or RELEASED version and a version
> of RELEASED means the latest RELEASED version.  I tried playing with
> these as version values but the artifact couldn't be found.  I did have
> success using no upper bound on range however.
>
> I think my biggest confusion was the naming convension here. The term
> "SNAPSHOT" typically means a fixed state of something at a particular
> point in time. However, in Maven it isn't fixed at all. It is in
> constant flux. A better name for SNAPSHOT would of been something like
> LATEST-DEV.
>
>
> ---
> Todd Thiessen
>
> -----Original Message-----
> From: Simone Gianni [mailto:simoneg@apache.org]
> Sent: Wednesday, November 19, 2008 9:19 AM
> To: Maven Users List
> Subject: Re: specifying "latest" for a dependency
>
> Hi Todd,
> SNAPSHOT is different from latest, because a SNAPSHOT is unstable,
> pre-alpha stuff, not the latest known working released version. This is
> a critical distinction, many projects use and publish SNAPSHOTS for
> internal use (for example, if I have three modules, they all evolve
> simultaneously, so they depend on the snapshot of each other until we
> arrive to a release).
>
> To get the latest one, simply put no upper bound to a version range.
> This will avoid SNAPSHOTS, and get the highest available version. And
> yes, only the first three are considered numbers. Obviously this is not
> perfect, because every organization can setup a standard with one, two,
> three, four or one hundred numbers. Anyway the three numbers are quite
> considered a de-facto standard, and used in 90% of software development.
>
> So, I would suggest to stick with 3 (major, minor, rev) number, and use
> the fourth if needed for stuff like ALPHA, BETA, RC1, RC2 (or OSGI
> timestamp), remembering that if your development practice often brings
> you to RC10 or above, you should number them 01, 02 etc...
>
> Simone
>
> Todd Thiessen wrote:
> > Snapshot versions work this way. Perhaps this is what you are looking
> > for.
> >
> > I was confused by this too btw. I think snapshot would of been better
> > named as "lastest".
> >
> > I don't know if you can do this with release versions though. It would
>
> > be nice to always get the latest release.
> >
> >
> > ---
> > Todd Thiessen
> >
> > -----Original Message-----
> > From: EJ Ciramella [mailto:eciramella@upromise.com]
> > Sent: Tuesday, November 18, 2008 12:31 PM
> > To: users@maven.apache.org
> > Subject: specifying "latest" for a dependency
> >
> > I know this has been discussed time and time again, but I can't seem
> > to combine the right google keywords to find what I'm looking for.
> >
> > How do you specify "latest" for a dependency?
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> Simone Gianni            CEO Semeru s.r.l.           Apache Committer
> http://www.simonegianni.it/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

RE: specifying "latest" for a dependency

Posted by Todd Thiessen <th...@nortel.com>.

Thanks for the reply. I do understand that SNAPSHOT is meant for
developers only.  I did read here:

http://books.sonatype.com/maven-book/reference/pom-relationships.html#d0
e9801

that LATEST means the latest SNAPSHOT or RELEASED version and a version
of RELEASED means the latest RELEASED version.  I tried playing with
these as version values but the artifact couldn't be found.  I did have
success using no upper bound on range however.

I think my biggest confusion was the naming convension here. The term
"SNAPSHOT" typically means a fixed state of something at a particular
point in time. However, in Maven it isn't fixed at all. It is in
constant flux. A better name for SNAPSHOT would of been something like
LATEST-DEV.

---
Todd Thiessen

-----Original Message-----
From: Simone Gianni [mailto:simoneg@apache.org] 
Sent: Wednesday, November 19, 2008 9:19 AM
To: Maven Users List
Subject: Re: specifying "latest" for a dependency

Hi Todd,
SNAPSHOT is different from latest, because a SNAPSHOT is unstable,
pre-alpha stuff, not the latest known working released version. This is
a critical distinction, many projects use and publish SNAPSHOTS for
internal use (for example, if I have three modules, they all evolve
simultaneously, so they depend on the snapshot of each other until we
arrive to a release).

To get the latest one, simply put no upper bound to a version range.
This will avoid SNAPSHOTS, and get the highest available version. And
yes, only the first three are considered numbers. Obviously this is not
perfect, because every organization can setup a standard with one, two,
three, four or one hundred numbers. Anyway the three numbers are quite
considered a de-facto standard, and used in 90% of software development.

So, I would suggest to stick with 3 (major, minor, rev) number, and use
the fourth if needed for stuff like ALPHA, BETA, RC1, RC2 (or OSGI
timestamp), remembering that if your development practice often brings
you to RC10 or above, you should number them 01, 02 etc...

Simone

Todd Thiessen wrote:
> Snapshot versions work this way. Perhaps this is what you are looking 
> for.
>
> I was confused by this too btw. I think snapshot would of been better 
> named as "lastest".
>
> I don't know if you can do this with release versions though. It would

> be nice to always get the latest release.
>
>
> ---
> Todd Thiessen
>
> -----Original Message-----
> From: EJ Ciramella [mailto:eciramella@upromise.com]
> Sent: Tuesday, November 18, 2008 12:31 PM
> To: users@maven.apache.org
> Subject: specifying "latest" for a dependency
>
> I know this has been discussed time and time again, but I can't seem 
> to combine the right google keywords to find what I'm looking for.
>  
> How do you specify "latest" for a dependency?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>   

-- 
Simone Gianni            CEO Semeru s.r.l.           Apache Committer
http://www.simonegianni.it/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: specifying "latest" for a dependency

Posted by Simone Gianni <si...@apache.org>.

Hi Todd,
SNAPSHOT is different from latest, because a SNAPSHOT is unstable,
pre-alpha stuff, not the latest known working released version. This is
a critical distinction, many projects use and publish SNAPSHOTS for
internal use (for example, if I have three modules, they all evolve
simultaneously, so they depend on the snapshot of each other until we
arrive to a release).

To get the latest one, simply put no upper bound to a version range.
This will avoid SNAPSHOTS, and get the highest available version. And
yes, only the first three are considered numbers. Obviously this is not
perfect, because every organization can setup a standard with one, two,
three, four or one hundred numbers. Anyway the three numbers are quite
considered a de-facto standard, and used in 90% of software development.

So, I would suggest to stick with 3 (major, minor, rev) number, and use
the fourth if needed for stuff like ALPHA, BETA, RC1, RC2 (or OSGI
timestamp), remembering that if your development practice often brings
you to RC10 or above, you should number them 01, 02 etc...

Simone

Todd Thiessen wrote:
> Snapshot versions work this way. Perhaps this is what you are looking
> for.
>
> I was confused by this too btw. I think snapshot would of been better
> named as "lastest".
>
> I don't know if you can do this with release versions though. It would
> be nice to always get the latest release.
>
>
> ---
> Todd Thiessen
>
> -----Original Message-----
> From: EJ Ciramella [mailto:eciramella@upromise.com] 
> Sent: Tuesday, November 18, 2008 12:31 PM
> To: users@maven.apache.org
> Subject: specifying "latest" for a dependency
>
> I know this has been discussed time and time again, but I can't seem to
> combine the right google keywords to find what I'm looking for.
>  
> How do you specify "latest" for a dependency?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>   

-- 
Simone Gianni            CEO Semeru s.r.l.           Apache Committer
http://www.simonegianni.it/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org