On Wed, May 12, 2010 at 5:57 AM, Prout John - jprout
<john.pr...@acxiom.com> wrote:
> maven1-repository.dev.java.net
> (https://maven-repository.dev.java.net/repository/)
>
>
>
> Path to dependency:
>
> 1) com.acxiomdigital.iws:IWS-Service:war:8.3.0-5-SNAPSHOT
>
> 2) com.acxiomdigital.is.ws:is-ws-service:jar:8.2.0-3
>
> 3) com.acxiomdigital.is.cache:is-cache:jar:8.2.0-3
>
> 4) com.digitalimpact:factory:jar:8.2.0-31
>
> 5) com.digitalimpact:di-common:jar:8.1.0-136
>
For each of these poms, check to see whether they define the repository.
Once a repository is defined (from any pom) it will be used to check
all future poms.
It's one of the reasons why repository definition is now frowned upon
and replaced with repository managers.
If you can't find a repository definition in that list, start checking
your transitive dependency graph (i.e your project dependencies, then
the dependencies of those, etc)
I suspect you can edit your ~/.m2/settings.xml and create a mirror for
this bad repository.
Something like:
<settings>
...
<mirrors>
<mirror>
<id>maven1-repository.dev.java.net</id>
<name>maven1-repository.dev.java.net</name>
<url>http://download.java.net/maven/1/</url>
<mirrorOf>maven1-repository.dev.java.net</mirrorOf>
</mirror>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
