Closed GoogleCodeExporter closed 8 years ago
It doesn't seem like it is looking at the other repository defined in the
pom.xml file:
<repository>
<id>maven2-repository.dev.java.net</id>
<name>Java.net Repository for Maven</name>
<url>http://download.java.net/maven/2/</url>
</repository>
The wagon-svn dependency isn't in the standard maven repo at maven.org.
Does your pom.xml file have this added to the <repositories> section? Are you
using some third-party maven repository internally? If so, you might need to
add the java.net repository to it.
Original comment by burke.we...@gmail.com
on 23 Feb 2011 at 10:43
I found I was able to resolve this by adding a <pluginRepositories> element to
pom.xml which is an exact copy of <repositories>, except of course that its
child elements are <pluginRepository> elements. Both <repositories> and
<pluginRepositories> must be present for the build to work. I found a handful
of pages which talked about this, and they seemed to be suggesting that this is
common behavior for a Maven build, though I'm not sure why.
Original comment by craigpe...@gmail.com
on 23 Jun 2011 at 10:07
org.jvnet.wagon-svn:wagon-svn:jar:1.8 is in Maven Central now:
http://search.maven.org/#artifactdetails%7Corg.jvnet.wagon-svn%7Cwagon-svn%7C1.8
%7Cjar
http://repo1.maven.org/maven2/org/jvnet/wagon-svn/wagon-svn/1.8/wagon-svn-1.8.po
m
Original comment by i...@ianbrandt.com
on 9 Jan 2012 at 11:06
I still get: "Plugin org.jvnet.wagon-svn:wagon-svn:1.8 or one of its
dependencies could not be resolved". Can you paste your pom.xml content please?
Original comment by apfelbe...@googlemail.com
on 11 May 2012 at 9:48
This shouldn't be an issue any more due to no longer using code.google.com as a
Maven repository.
Original comment by nateredd...@gmail.com
on 1 Mar 2013 at 12:58
Original issue reported on code.google.com by
jppar...@gmail.com
on 14 Feb 2011 at 8:42