[
http://jira.codehaus.org/browse/MNG-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184082#action_184082
]
Antony Stubbs commented on MNG-3685:
------------------------------------
I've also hit the problem, even using
mvn release:prepare -DautoVersionSubmodules=true -DpreparationGoals="clean
install"
work around I used was to checkout the commit with the release versions
separately and do a mvn install
> 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
> Issue Type: Bug
> Affects Versions: 2.0.9
> Reporter: Jörg Hohwiller
> Fix For: 2.2.2
>
> 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
