CODEWITHSUNDEEP
maven-2maven
schmmd
schmmd

Reputation: 19448

Why does maven use my internal repository before my local repository?

when I am doing development I often need to change a dependency, but I'm not ready to deploy my changes. For example, I'm working on project Foo and I realize I need to add a method to the common library. Before deploying this change to our internal repository, I would like to install the changes to common library (mvn install) and recompile Foo to use the common library in the local repository (note that I'm using all SNAPSHOT versions).

However, after I mvn install my common library, when I recompile Foo it doesn't use the new common library--it keeps using the latest SNAPSHOT of common library in the internal repository. If I deploy the changed common library, Foo picks it up immediately.

How can I get maven to look first in the local repository?

UPDATE: when the file is installed into the local repository, it gets a name like foo-1.0.0-SNAPSHOT.jar, but when I deploy it, it gets a timestamp foo-1.0.0-20111104.191316-23.jar. I think this is why the remote artifact gets pulled each time. Any idea why mvn install is not working like mvn deploy? Does it have to do with the fact that I have a snapshot repository set up for deploy?

Upvotes: 6

Views: 8729

Answers (2)

Narendra Verma
Narendra Verma

Reputation: 1

You can try this option. This worked for me.

In your project's main pom.xml change 'snapshots' enabled setting to 'false'.

<repository>
    <id>yourRepo</id>
    <name>Repository</name>
    <url>http://your.repo.com/repo</url>
    <snapshots>
        <enabled>false</enabled>
    </snapshots>
</repository>

Upvotes: 0

Ryan Stewart
Ryan Stewart

Reputation: 128749

By default, Maven checks for new versions of SNAPSHOT artifacts once per day. When it does this check, it will download SNAPSHOTS from remote repos that are newer than what you have locally. Either your artifact timestamps are out of sync and you're doing something to override Maven's update policy (like calling it with -U or setting the udpatePolicy to "always"), or else the local repository you're installing the artifact to isn't the same one you're subsequently running Maven against. What you're describing isn't typical Maven behavior. For a better answer, give more details in your question.

One indicator you can look for: after you install your common artifact, when you next compile Foo, does Maven download the common artifact again? If so, then it really is getting it from the remote, and you need to check your update settings. If not, then you have something strange going on locally.

Upvotes: 3

Related Questions