Maven automatic SNAPSHOT update

Question

Let's say I have one project with the following POM:

<groupId>com.mine</groupId>
<artifactId>coreJar</artifactId>
<packaging>jar</packaging>
<version>0.0.1-SNAPSHOT</version>

And then in another project I always want to reference the latest SNAPSHOT:

<dependencies> 
    <dependency>
        <groupId>com.mine</groupId>
        <artifactId>coreJar</artifactId>
        <version>0.0.1-SNAPSHOT</version>
    </dependency>
    ...
<dependencies>

But instead of 0.0.1-SNAPSHOT, I want it to always grab the latest SNAPSHOT version. In the past you could use LATEST, but this has since been deprecated (for reasonable reasons).

I do understand you can specify versions, such as:

[1.5,)

But I could never get it to work with a "-SNAPSHOT":

[0.0.1,)-SNAPSHOT // Doesn't work!

The question then is how do I get maven to grab the latest SNAPSHOT in my other project?

Have a look here: http://stackoverflow.com/questions/30571/how-do-i-tell-maven-to-use-the-latest-version-of-a-dependency#answer-1172371 — dma_k, Mar 01 '10 at 22:31

score 45 · Answer 1 · edited Aug 04 '14 at 22:27

Another option (which I use) is to include the following in your pom.xml. updatePolicy tag will force maven to always use latest snapshot from this repo.

<repositories>
    <repository>
        <id>you-snapshots</id>
        <url>http://host/nexus/repos/snapshots</url>
        <snapshots>
            <updatePolicy>always</updatePolicy>
        </snapshots>
        <releases>
            <updatePolicy>always</updatePolicy>
        </releases>
    </repository>
</repositories>

p.s. I always configure all repos in pom.xml because we use several CI servers and it will be quite hard to configure all of them (I am lazy...)

Doc on settings.xml updatePolicy for reference. The frequency for downloading updates - can be "always", "daily" (default), "interval:XXX" (in minutes) or "never" (only if it doesn't exist locally).

Thanks. That a clean way to update local repository which may be change any time. — roterl, Apr 02 '14 at 07:37

score 16 · Answer 2 · answered Mar 01 '10 at 21:01

16

Use

mvn -U, --update-snapshots

Forces a check for updated releases and snapshots on remote repository

answered Mar 01 '10 at 21:01

Tim

19,793
8
70
95

I think the question is asking how to update to the latest SNAPSHOT, not just the latest 0.0.1-SNAPSHOT - which is what -U would do. – Martin Mar 01 '10 at 21:02
3

@Strawberry: I don't see any reasonable explanation of how `0.0.1-SNAPSHOT` can become `0.0.2-SNAPSHOT` or any other later version. – dma_k Mar 01 '10 at 22:18

score 15 · Accepted Answer · answered Mar 01 '10 at 22:49

A few words about dependency ranges and SNAPSHOT dependencies (quoting the Dependency Mediation and Conflict Resolution design document):

Incorporating SNAPSHOT versions into the specification

Resolution of dependency ranges should not resolve to a snapshot (development version) unless it is included as an explicit boundary. There is no need to compile against development code unless you are explicitly using a new feature, under which the snapshot will become the lower bound of your version specification. As releases are considered newer than the snapshot they belong to, they will be chosen over an old snapshot if found.

So, to answer your question, the only way to use a SNAPSHOT with dependency ranges is as boundary and you won't get higher SNAPSHOT versions automatically by design (which really makes sense).

Personally, I don't like to use dependency ranges because I find that it can lead to build reproducibility issues and makes the build more fragile. I do not recommend them.

Just in case, upgrading the SNAPSHOT version typically means that you are releasing some code and the maven release plugin provides support for that (see the Updating POM Versions).

@Pascal: Can you give an example of what is "dependency ranges as explicit boundary"? Is it `[0.0,1000.0]-SNAPSHOT` for example? — dma_k, Mar 02 '10 at 07:55
@PascalThivent Link in your post is sadly not avaiable anymore. — Michi-2142, Jul 16 '19 at 12:33

score 8 · Answer 4 · edited Jul 09 '15 at 17:08

8

There is a Versions plugin for Maven which allows you to update your pom to the latest greatest SNAPSHOTS in visible repositories. It does this by inspecting your pom and comparing against remote repositories and then modifying as required.

It is a useful tool but I would definitely like to see an equivalent to the deprecated LATEST option. I find this kind of dependency particularly useful in continuous integration scenarios.

edited Jul 09 '15 at 17:08

akokskis

1,486
15
32

answered Mar 01 '10 at 21:08

Martin

7,089
3
28
43

3

I find this kind of dependency particularly *harmful*. – Pascal Thivent Mar 01 '10 at 22:53

score 3 · Answer 5 · answered Sep 03 '14 at 13:13

3

use mvn install -U u must use this to force maven to get the latest snapshots

answered Sep 03 '14 at 13:13

Harish Mallikarjuna

93
1
10

score 1 · Answer 6 · answered Oct 17 '16 at 17:11

1

It's

<version>[0.0-SNAPSHOT,)</version>

answered Oct 17 '16 at 17:11

Dimath

381
1
4
13

score 0 · Answer 7 · answered Nov 13 '12 at 23:57

0

In case you want to update your SNAPSHOT releases inside Eclipse (when using m2e / m2eclipse), right click the affected project, then select "Maven" -> "Update Project..." -> "OK" (with selected project causing problems).

answered Nov 13 '12 at 23:57

Abdull

26,371
26
130
172

Why does Eclipse not consider the updatePolicy=always setting from settings.xml? Is it intended or a bug of the Maven Eclipse plugin? – schoenk Dec 02 '15 at 13:04

Maven automatic SNAPSHOT update

7 Answers7

Incorporating SNAPSHOT versions into the specification

Linked