The dependency resolution will only fail if no other repository being used has the version of the glassfish plugin you are attempting to use.
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.
I guess you're using org.glassfish.maven. Plugin:maven-glassfish-plugin:2.2-SNAPSHOT which declares indeed 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).
2 I'm using 2.1 (not a snapshot) and also have the problem. It's frustrating, because I already have the artifact; maven is just hanging while attempting to (needlessly) update it. – Caffeine Coma Jun 15 at 17:53.
I have the same problem. The only solution I have found at this time is to delete all repositories (or switch them to enabled=false) from all the dependencies (3). They should put all these repositories into a profile, this is terrible solution.It would be even alright if there was any response from the server, but it simply hangs.
Timeout settings are also ignored.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.