You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2009/12/31 04:53:56 UTC
[jira] Closed: (MNG-3685) Dependency can't be resolved but has been
found in the reactor.
[ http://jira.codehaus.org/browse/MNG-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-3685.
-----------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.2.2)
sorry, but I can't reproduce this in 2.2.1 or 3.0-alpha-5.
With the given test project, running release:prepare is expected to fail - there are no snapshots. Changing the versions to all be 1-SNAPSHOT, it succeeds. Yes, the error message is present - but that's a problem with the release plugin requiring the artifacts, and not just the projects. This is well documented in issues in MRELEASE as a separate issue.
I couldn't get eclipse:eclipse or javadoc:aggregate to fail. javadoc:javadoc does fail because it requires the JAR to be built, much as above. I think the warning is correct.
> Dependency can't be resolved but has been found in the reactor.
> ---------------------------------------------------------------
>
> Key: MNG-3685
> URL: http://jira.codehaus.org/browse/MNG-3685
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 2.0.9
> Reporter: Jörg Hohwiller
> Attachments: sample-MNG-3685.tgz
>
>
> Since I upgraded maven to 2.0.9, I get messages like the following endlessly:
> Downloading: http://m-m-m.sourceforge.net/repository/net/sf/m-m-m/mmm-util-core/1.0.2-SNAPSHOT/mmm-util-core-1.0.2-SNAPSHOT.jar
> [WARNING] The dependency: net.sf.m-m-m:mmm-util-core:jar:1.0.2-SNAPSHOT can't be resolved but has been found in the reactor.
> This dependency has been excluded from the plugin execution. You should rerun this mojo after executing mvn install.
> This also happens, if someone checks out the project and does "mvn eclipse:eclipse". The process still works but takes extraordinary long to proceed because it scales about n^2 with n beiing the number of modules in your reactor.
> You should also take into account that "mvn install" aborts if some tests fail.
> Sorry to say so, but this behaviour of maven is absolutely inacceptable. I hope there is a chance to fix this in the next release(s). Thanks!
--
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