We cannot deploy our app as Maven is trying to update glassfish plugin from maven.ocean.net.au repository, although no such repository was defined in our pom. The problem is maven.ocean.net.au isn't online and therefor our build fails. Has this happened to anybody else?
+1
A:
The dependency resolution will only fail if no other repository being used has the version of the glassfish plugin you are attempting to use.
Make sure your maven setup has several other plugin repositories (best is a local repository which proxies requests to remote servers, to build up a huge local cache of Maven artifacts) so that resolution won't fail when a single repo can't be reached.
matt b
2010-10-21 15:23:34
+1
A:
I guess you're using org.glassfish.maven.plugin:maven-glassfish-plugin:2.2-SNAPSHOT which declares indeed http://maven.ocean.net.au/snapshot as snapshot repository.
My suggestion would be to use a released version of the plugin e.g. version 2.1 (released versions of this plugin are hosted in the java.net Maven2 Repository) or to patch and deploy a version 2.2 to your internal corporate repository (i.e. don't use a snapshot from the Ocean Maven2 Snapshot Repository).
Pascal Thivent
2010-10-21 22:18:05