Maven looks for snapshots in offline mode

Does fail also when offline set to true in settings.xml (which is kind of critical for us behind firewalls...):

[INFO] artifact org.apache.maven.plugins:maven-scm-plugin: checking for updates from central

[WARNING] repository metadata for: 'artifact org.apache.maven.plugins:maven-scm-plugin' could not be retrieved from repository: central due to an error: Error transferring file
[INFO] Repository 'central' will be blacklisted

I'm not seeing this locally with a test and I'm using TPIMon on Windows and truss in Linux and see no network activity. Torsten, you still seeing this?

I cannot reproduce this at all on Linux, Windows, or MAC so I'll give this a day or two and then consider it closed.

There is no network traffic, it's a logging problem. Created MNG-2881.

I often see the problem that Maven actually does check for new snapshot POMs in offline mode. It does not download artifacts though.

Once I got the problem (running Maven 2.0.5 or 2.0.6) that I ran mvn -o install, it downloaded new snapshot POMs, but then failed because it "could" not download the artifacts referenced by the new POMs.

Maven should not download anything in offline mode.

can someone reopen this issue?

I am using maven 2.0.8
mvn -o site

...
[INFO] Error building POM (may not be this project's POM).
Project ID: org.codehaus.mojo:cobertura-maven-plugin
Reason: POM 'org.codehaus.mojo:cobertura-maven-plugin' not found in repository: System is offline.
org.codehaus.mojo:cobertura-maven-plugin:pom:2.2-SNAPSHOT
for project org.codehaus.mojo:cobertura-maven-plugin

Do you not have 2.2-SNAPSHOT already present on your system? I imagine that if it isn't there the first time, it cannot possibly build with a plugin that's absent. That is different than trying to update a plugin that already is installed.

Yes, I do!
I run "mvn site" online and it works fine. Then I call "mvn -o site" and it fails!

When I am offline and dont tell maven (omitt -o): "mvn site" proceeds past this point but fails with
...
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] The skin does not exist: Unable to determine the release version

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-classic-skin -Dvers
ion=RELEASE -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.maven.skins -DartifactId=maven-classic-skin -Dversio
n=RELEASE -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

org.apache.maven.skins:maven-classic-skin:jar:RELEASE

I have the same problem with Maven 2.0.8. It happened to me while doing a demonstration, so I had to improvise, not very comfortable lol
I ran maven with -o option because I had no network at the place where I did the demo, so I did not want to check artifacts. All artifacts are in my local repository so there should have been no problem ... but it tried to download artifacts and I can't understand why.

I had the following error message :

[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) org.andromda.profiles.uml14:andromda-profile-service:xml.zip:3.3-SNAPSHOT

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.andromda.profiles.uml14 -DartifactId=andromda-profile-service -Dversion=3.3-SNAPSHOT -Dpackaging=xml.zip -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.andromda.profiles.uml14 -DartifactId=andromda-profile-service -Dversion=3.3-SNAPSHOT -Dpackaging=xml.zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

Path to dependency:
1) fr.xxx.t4:t4-core-mda:pom:1.0-SNAPSHOT
2) org.andromda.cartridges:andromda-ejb3-cartridge:jar:1.0-SNAPSHOT
3) org.andromda.profiles.uml14:andromda-profile:xml.zip:3.3-SNAPSHOT
4) org.andromda.profiles.uml14:andromda-profile-service:xml.zip:3.3-SNAPSHOT

----------
1 required artifact is missing.

for artifact:
fr.xxx.t4:t4-core-mda:pom:1.0-SNAPSHOT

from the specified remote repositories:
central (http://10.11.4.108:8080/artifactory/repo),
andromda (http://10.11.4.108:8080/artifactory/repo),
snapshots (http://10.11.4.108:8080/artifactory/repo)

NOTE: Maven is executing in offline mode. Any artifacts not already in your local
repository will be inaccessible.

To help to reproduce the problem, note I use artifactory as a repository. I have the following config in pom.xml :

<repositories>
<repository>
<id>andromda</id>
<url>http://10.11.4.108:8080/artifactory/repo</url>
<snapshots>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
</snapshots>
</repository>
<repository>
<id>central</id>
<url>http://10.11.4.108:8080/artifactory/repo</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<repository>
<id>snapshots</id>
<url>http://10.11.4.108:8080/artifactory/repo</url>
<releases>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
</releases>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>andromda</id>
<url>http://10.11.4.108:8080/artifactory/repo</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>
<pluginRepository>
<id>central</id>
<url>http://10.11.4.108:8080/artifactory/repo</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>
<pluginRepository>
<id>snapshots</id>
<url>http://10.11.4.108:8080/artifactory/repo</url>
<releases>
<enabled>false</enabled>
</releases>
</pluginRepository>
</pluginRepositories>

I tried with updatePolicy as "weekly" or "never" but it changed nothing.

I also have the following mirrors in maven settings.xml, but removing them changed nothing :

<mirror>
<id>andromda</id>
<mirrorOf>andromda</mirrorOf>
<name>AndroMDA Repository</name>
<url>http://10.11.4.108:8080/artifactory/repo</url>
</mirror>

<mirror>
<id>apache-incubator</id>
<mirrorOf>apache-incubator</mirrorOf>
<name>Apache Incubator Repository</name>
<url>http://10.11.4.108:8080/artifactory/repo</url>
</mirror>

I really think there is a bug somewhere, as we run maven with -o option, it should not try to download artifacts. Maybe a problem with transitive dependencies ?

we're also seeing the problem with maven 2.0.9. so please re-open the issue!
Note we're using a company wide maven repository (artifactory)

$ mvn --version
Maven version: 2.0.9
Java version: 1.5.0_13
OS name: "mac os x" version: "10.5.2" arch: "i386" Family: "unix"

$ mvn -o test
[INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in your local
repository will be inaccessible.

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Embedded JBoss Tests
[INFO] task-segment: [test]
[INFO] ------------------------------------------------------------------------
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) org.jboss.embedded:jboss-embedded:jar:beta3-SNAPSHOT

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.jboss.embedded -DartifactId=jboss-embedded -Dversion=beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.jboss.embedded -DartifactId=jboss-embedded -Dversion=beta3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

Path to dependency:
1) akquinet:embedded-tests:jar:1.7-SNAPSHOT
2) org.jboss.embedded:jboss-embedded-all:jar:beta3
3) org.jboss.embedded:jboss-embedded:jar:beta3-SNAPSHOT

----------
1 required artifact is missing.

for artifact:
akquinet:embedded-tests:jar:1.7-SNAPSHOT

from the specified remote repositories:
akquinet (http://192.168.1.1:8080/artifactory/akquinet),
akquinet.snapshots (http://192.168.1.1:8080/artifactory/libs-snapshots)

NOTE: Maven is executing in offline mode. Any artifacts not already in your local
repository will be inaccessible.

[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Wed May 28 10:13:47 CEST 2008
[INFO] Final Memory: 7M/13M
[INFO] ------------------------------------------------------------------------

the artifact maven complains about
seems to be existing in the local repository:

$ ls ~/.m2/repository/org/jboss/embedded/jboss-embedded/beta3-SNAPSHOT/
jboss-embedded-beta3-SNAPSHOT.jar
jboss-embedded-beta3-SNAPSHOT.pom.sha1
maven-metadata-repository.jboss.org.xml
jboss-embedded-beta3-SNAPSHOT.jar.sha1
maven-metadata-cellactive.snapshots.xml
maven-metadata-snapshots.jboss.org.xml
jboss-embedded-beta3-SNAPSHOT.pom
maven-metadata-cellactive.snapshots.xml.sha1
maven-metadata-snapshots.jboss.org.xml.sha1

We have the same problem here. We are migrating from an old environment (with direct connection to the central repositories) to a new one that uses artifactory to proxy all the repositories. We were using Maven 2.0.7 in the old environment and Maven 2.0.8 in the new one. By the way, all the default plugins appear in:

http://svn.apache.org/viewvc/maven/components/tags/maven-2.0.9/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?view=markup

but not in

http://svn.apache.org/viewvc/maven/components/tags/maven-2.0.8/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?view=markup

Please, reopen the bug.

Best regards,
JMB

I have maven version 2.0.9 and I am having the same issue.

doing "mvn install -Dmaven.test.skip" works fine, but when I use
"mvn install -Dmaven.test.skip -o" (the offline mode) it doesn't work and I double checked that the jar is in my local repo!
It's painfully slow to do a build trying to download all the dependencies and POM files everytime!

I have the same issue with apache rampart and it's related to some invalid version describe in the pom.xml (https://issues.apache.org/jira/browse/RAMPART-195)

Might be the same problem here.

as a side note: I don't think maven handle this kind of situation gracefully

IT for MNG-3314 confirms issue was still existent.