Try to cheek your settings.xml maven config file.
Perhaps snapshot are enabled there
Le 19 juin 2012 15:47, Dünnebeil Gerhard gerhard.duenneb...@ait.ac.at a
écrit :
Hmm,
ok. I double checked things. Here is the outcome:
--- some excerpt from the log output (gained with the -X
switch) ---
The dependencies of the project:
[DEBUG] at.ac.ait.enviro:tsapi-io-trafficCount:jar:4.0.7-SNAPSHOT
[DEBUG]junit:junit:jar:4.8.2:test
[DEBUG]at.ac.ait.enviro:tsapi-api:jar:4.0.7-SNAPSHOT:compile
[DEBUG]at.ac.ait.enviro:tsapi-basic-impls:jar:4.0.7-SNAPSHOT:compile
[DEBUG] at.ac.ait.enviro:utils:jar:4.0.7-SNAPSHOT:compile
-- This is the module that fails
[DEBUG] com.vividsolutions:jts:jar:1.8:compile
[DEBUG] org.codehaus.groovy:groovy:jar:1.7.0:compile
[DEBUG] antlr:antlr:jar:2.7.7:compile
[DEBUG] asm:asm:jar:3.2:compile
[DEBUG] asm:asm-commons:jar:3.2:compile
[DEBUG] asm:asm-util:jar:3.2:compile
[DEBUG] asm:asm-analysis:jar:3.2:compile
[DEBUG] asm:asm-tree:jar:3.2:compile
[DEBUG] jline:jline:jar:0.9.94:compile
[DEBUG] org.slf4j:slf4j-api:jar:1.6.1:compile
[DEBUG] commons-collections:commons-collections:jar:3.2.1:compile
[DEBUG]log4j:log4j:jar:1.2.16:compile
A few lines above maven tells me it is happy with the version it finds in
the local repository but tries to download things nevertheless (at least
that's how I interpret things)
[DEBUG] Skipped remote update check for
at.ac.ait.enviro:utils:4.0.7-SNAPSHOT/maven-metadata.xml, locally installed
metadata up-to-date.
[DEBUG] Skipped remote update check for
at.ac.ait.enviro:utils:4.0.7-SNAPSHOT/maven-metadata.xml, locally installed
metadata up-to-date.
[DEBUG] Using connector WagonRepositoryConnector with priority 0 for
http://ts-toolbox.ait.ac.at/maven2/ as ts-toolbox
Downloading:
http://ts-toolbox.ait.ac.at/maven2/at/ac/ait/enviro/utils/4.0.7-SNAPSHOT/utils-4.0.7-20120619.063804-9.pom
[DEBUG] Using connector WagonRepositoryConnector with priority 0 for
http://ts-toolbox.ait.ac.at/maven2/snapshots as ts-toolbox
Downloading:
http://ts-toolbox.ait.ac.at/maven2/snapshots/at/ac/ait/enviro/utils/4.0.7-SNAPSHOT/utils-4.0.7-20120619.063804-9.pom
[WARNING] The POM for at.ac.ait.enviro:utils:jar:4.0.7-20120619.063804-9
is missing, no dependency information available
Finally, near the end of the run it tells me the following
message : Failed to execute goal on project tsapi-io-trafficCount: Could
not resolve dependencies for project
at.ac.ait.enviro:tsapi-io-trafficCount:jar:4.0.7-SNAPSHOT: Could not find
artifact at.ac.ait.enviro:utils:jar:4.0.7-20120619.063804-9 in
ts-toolbox.ait.snapshots (http://ts-toolbox.ait.ac.at/maven2/snapshots)
-
So, yes. I think it is a snapshot dependency.
Another thing that is fishy here is that the URL that maven tries to
download is NOT in the list of repositories.
Here is the list just as a reference, also taken from the effective-pom.
repositories
repository
snapshots
enabledfalse/enabled
/snapshots
idcentral/id
nameCentral Repository/name
urlhttp://repo.maven.apache.org/maven2/url
/repository
/repositories
I hope that gives somebody some clue as I definitely am out of my depths
here.
Best regards
Gerhard
-Ursprüngliche Nachricht-
Von: abhijith tn [mailto:abhijit...@gmail.com]
Gesendet: Dienstag, 19. Juni 2012 15:26
An: Maven Users List
Betreff: Re: Problems with the update of snapshots
Hi Gerhard,
This is the basic functionality on which the question is raised on. I
guess, maven at any cost should not check the repository which is not
mentioned in the pom.
Please check the dependency that you have given, if the version has
SNAPSHOT word in it, then Maven by default tries to look in the SNAPSHOT
repository.
Folks,
Correct me if I am wrong.
On Tue, Jun 19, 2012 at 2:52 PM, Dünnebeil Gerhard
gerhard.duenneb...@ait.ac.at wrote:
Hello everybody,
having migrated from maven2 to maven3 (3.0.4) recently I observed some
strange behavior.
I am not sure whether this is due to some configuration problem on my
side or whether it's a bug of maven.
The problems I have:
I am running a continuous integration server (Jenkins). One of the
things this server shall check is whether we are indeed using a set of
artifacts that are up to date, i.e. can be compiled from the newest
code. To check this I delete significant parts of the local repository
each night and rebuild everything from scratch.
To achieve this I created a build-profile that does not mention ANY
snapshot repository. I did control that with help:effective-pom.
Additionally I provided the -no-snapshot-update flag as a command
line parameter to maven.
I now see the following effect:
A module A is built by Jenkins using maven and then installed to the
local
