Re: Unexpected reference to an old Repository
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 idmaven1-repository.dev.java.net/id namemaven1-repository.dev.java.net/name urlhttp://download.java.net/maven/1//url mirrorOfmaven1-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
RE: Unexpected reference to an old Repository
Thanks for the suggestions! I've been through all the dependencies referenced through the tree below and been unable to find any references to maven1-repository.dev.java.net, so no luck there. What I've found is that my problems are caused by recent releases of Maven. I had problems using Maven 2.2.1 and 2.0.11, but when I regress to 2.0.9 (which is what's installed on our build server) the problem goes away. For now, I'll stick to using Maven 2.0.9, but I'd appreciate any insight as to why recent versions of Maven 2 are causing my build to look at maven1-repository.dev.java.net Thanks John -Original Message- From: Barrie Treloar [mailto:baerr...@gmail.com] Sent: Wednesday, May 12, 2010 12:13 AM To: Maven Users List Subject: Re: Unexpected reference to an old Repository 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 idmaven1-repository.dev.java.net/id namemaven1-repository.dev.java.net/name urlhttp://download.java.net/maven/1//url mirrorOfmaven1-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 *** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Unexpected reference to an old Repository
Hi I'm running a Maven build (release 2.2.1). The build is broken because it's somehow referencing an old repository: maven1-repository.dev.java.net (https://maven-repository.dev.java.net/repository/) The repository has been moved and is returning an HTTP 302 - permanently moved, which Maven doesn't handle. Error returned is as follows: Unable to get dependency information: Unable to read local copy of metadata: Cannot read metadata from 'C:\Documents and Settings\jprout\.m2\repository\com\digitalimpact\di-common-db\maven-meta data-maven1-repository.dev.java.net.xml': end tag name /body must match start tag name hr from line 7 (position: TEXT seen .../address\n/body... @9:8) com.digitalimpact:di-common-db:jar:null from the specified remote repositories: central (http://repo1.maven.org/maven2), springfield (http://springfield.corp.acxiom.net:/m2/), 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 di-common-db is one of my Artifacts and it doesn't contain any mention of maven1-repository What puzzles me is that I can't find anything in my project, which references the maven1-repository, which I don't need. I expect the reference is from one of my dependencies, but I can't find which one. I've run the build with the -X flag, but still nothing to tell me why it's referencing maven1-repository. Is there any I can run the Maven build so it tells me where it's getting its list of Repositories from? Is there any way I can explicitly exclude the maven1-repository, so the build doesn't look at it? Thanks in advance! John *** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You.
