[
http://jira.codehaus.org/browse/MNG-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Smart closed MNG-5060.
---------------------------
Resolution: Fixed
Fix Version/s: 3.0.4
Looks like this is an easyb issue. I'll reopen if it turns out not to be.
> Fails to resolve plugin dependencies in Maven 3.0.x
> ---------------------------------------------------
>
> Key: MNG-5060
> URL: http://jira.codehaus.org/browse/MNG-5060
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0.3
> Reporter: John Smart
> Priority: Blocker
> Fix For: 3.0.4
>
>
> For some projects, Maven 3.x fails to resolve/download plugin dependencies,
> whereas Maven 2.x worked fine. Could be an aether bug. The artifact when
> resolving in aether has "remoteRepositories" : size:0
> The situation appears to be that it it downloads it from central, adds in
> _maven.repositories as
> #NOTE: This is an internal implementation file, its format can be changed
> without prior notice.
> #Thu Apr 07 20:42:04 NZST 2011
> easyb-core-1.1.jar>central=
> easyb-core-1.1.pom>central=
> and then proceeds to only look for
> easyb-core-1-1.pom>=
> (i.e. local only repository) which isn't there.
> An example of this problem can be reproduced by building the following
> project from github:
> https://github.com/wakaleo/thucydides/tree/maven-3.0.x-bug-example
> Just run mvn install. With Maven 2.2.1 it works fine. With Maven 3.0.x you
> get the following:
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 2:05.397s
> [INFO] Finished at: Thu Apr 07 23:08:55 NZST 2011
> [INFO] Final Memory: 23M/81M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Missing:
> [ERROR] ----------
> [ERROR] 1) org.easyb:easyb-core:jar:1.1
> [ERROR]
> [ERROR] Try downloading the file manually from the project website.
> [ERROR]
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=org.easyb -DartifactId=easyb-core
> -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file
> [ERROR]
> [ERROR] Alternatively, if you host your own repository you can deploy the
> file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=org.easyb -DartifactId=easyb-core
> -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> [ERROR]
> [ERROR] Path to dependency:
> [ERROR] 1) org.easyb:maven-easyb-plugin:jar:1.1
> [ERROR] 2) org.easyb:easyb-core:jar:1.1
> [ERROR]
> [ERROR] ----------
> [ERROR] 1 required artifact is missing.
> [ERROR]
> [ERROR] for artifact:
> [ERROR] org.easyb:maven-easyb-plugin:jar:1.1
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] (none)
> [ERROR] -> [Help 1]
> [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/MultipleArtifactsNotFoundException
> It does this despite the fact that the dependency in question is (a) on
> central, (b) in the local repository, or (c) both. If you try to install it
> manually, it fails with a message saying that there is already a JAR file
> there.
--
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
