dogtperfect / jstd-maven-plugin

Automatically exported from code.google.com/p/jstd-maven-plugin
0 stars 0 forks source link

mvn install on jstd-maven-plugin fails due to unresolvable plugin org.jvnet.wagon-svn #6

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. svn checkout jstd-maven-plugin
2. run mvn install
3. view output

What is the expected output? What do you see instead?

The expected output is a successful build.

The actual output is:

james-parkins-mac-mini:jstd-maven-plugin-read-only james$ mvn install
[INFO] Scanning for projects...
Downloading: 
http://repo1.maven.org/maven2/org/jvnet/wagon-svn/wagon-svn/1.8/wagon-svn-1.8.po
m
[WARNING] The POM for org.jvnet.wagon-svn:wagon-svn:jar:1.8 is missing, no 
dependency information available
Downloading: 
http://repo1.maven.org/maven2/org/jvnet/wagon-svn/wagon-svn/1.8/wagon-svn-1.8.ja
r
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-
1.1.jar
Downloaded: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-
1.1.jar (165 KB at 51.6 KB/sec)
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project 
com.google.jstestdriver:maven-jstestdriver-plugin:1.2.2-SNAPSHOT 
(/Users/james/Documents/Dev/JavaScript/jstd-maven-plugin-read-only/pom.xml) has 
1 error
[ERROR]     Unresolveable build extension: Plugin 
org.jvnet.wagon-svn:wagon-svn:1.8 or one of its dependencies could not be 
resolved: Could not find artifact org.jvnet.wagon-svn:wagon-svn:jar:1.8 in 
central (http://repo1.maven.org/maven2) -> [Help 2]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
james-parkins-mac-mini:jstd-maven-plugin-read-only james$ 

What version of the product are you using? On what operating system?

os: OSX
Maven - 3.0.2
trunk version of jstd-maven-plugin

Original issue reported on code.google.com by jppar...@gmail.com on 14 Feb 2011 at 8:42

GoogleCodeExporter commented 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

GoogleCodeExporter commented 8 years ago
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

GoogleCodeExporter commented 8 years ago
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

GoogleCodeExporter commented 8 years ago
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

GoogleCodeExporter commented 8 years ago
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