Additional repositories are not checked for plugin JAR (POM is OK)
------------------------------------------------------------------
Key: MNG-4477
URL: http://jira.codehaus.org/browse/MNG-4477
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.2.1
Environment: [espin...@espinosadell ~]$ mvn --version
Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
Java version: 1.6.0_12
Java home: /usr/java/jdk1.6.0_12/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux" version: "2.6.29.6-desktop-69mib" arch: "i386" Family: "unix"
Reporter: Jan Uhlir
Attachments: maven_build_log_repo_issue2.txt, pom.xml
More pain with java.net repositry. However this time Maven seems to blame.
Lets have a trivial pom.xml file, just definition of repository,
maven2-repository.dev.java.net, and org.codehaus.mojo:jaxws-maven-plugin:1.12.
What happens:
The jaxws-maven-plugin POM is first checked in central repo. It fails. The
jaxws-maven-plugin POM is then checked in java.net repo. It is detected and
successfully downloaded. So for good.
The problem comes next with jaxws-maven-plugin JAR. The jaxws-maven-plugin JAR
is first checked in central repo*. It fails indeed. But that is it. Maven does
not try to look in java.net repository at all. Destpite it done successfully
for POM.
Verbose output is attached. The simple pom.xml is also attached to this issue.
Cheers
Jan
P.S.
* why!? Why not assume same repo for JAR as was POM in.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
