Question

Similar to this question, I can’t do a glassfish deploy because some server in Australia is down at the moment. I’ve had the artifacts cached locally for months.

How can I tell maven to not attempt to update the plugin (and its dependencies)? I tried adding the following to my pom, but it didn’t help:

<pluginRepositories>
    <pluginRepository>
            <id>ocean</id>
            <url>http://maven.ocean.net.au</url>
            <releases>
                    <enabled>false</enabled>
                    <updatePolicy>never</updatePolicy>
            </releases>
            <snapshots>
                    <enabled>true</enabled>
                    <updatePolicy>never</updatePolicy>
            </snapshots>
    </pluginRepository>

</pluginRepositories>

I also tried the command line switches. There’s -npu, which didn’t seem to help with Maven 2.2.1. On Maven 3 the docs say “Ineffective, only kept for backward compatibility”, so I don’t have a lot of hope for that one.

We will be moving to Nexus soon, but there ought to be a simple way to tell maven not to attempt a plugin update.

Answer 1

Use the -o or --offline switch to work offline – this should make Maven not bother to check any repositories for new updates or snapshots, as if you did not have network access.

Additionally – are you specifying the <version> for each of your plugins? There should be no need to check for updates to release versions of a plugin.