maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zac Thompson (JIRA)" <j...@codehaus.org>
Subject [jira] Issue Comment Edited: (MNG-3685) Dependency can't be resolved but has been found in the reactor.
Date Tue, 16 Jun 2009 20:41:15 GMT

    [ http://jira.codehaus.org/browse/MNG-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180493#action_180493
] 

Zac Thompson edited comment on MNG-3685 at 6/16/09 3:40 PM:
------------------------------------------------------------

-Is this the same root cause as MRELEASE-3 ?-
-The above has existed since 2005; described as 'an MNG issue' -- is this correct?  Can the
MNG people and the MRELEASE people get together to determine where the root problem is?-

-I think that some of the following may be related as well (but likely not all):-
MNG-3283
MNG-3023 
MNG-3260
MJAVADOC-116
-... however, I'm not confident enough in the relationship to create the links myself--

please ignore my text above ... seems like there was a good reason I was unsure of myself

      was (Author: zac):
    Is this the same root cause as MRELEASE-3 ?
The above has existed since 2005; described as 'an MNG issue' -- is this correct?  Can the
MNG people and the MRELEASE people get together to determine where the root problem is?

I think that some of the following may be related as well (but likely not all):
MNG-3283
MNG-3023 (not fixed, despite status -- the "mvn release:prepare from a clean checkout" example
still fails for me in 2.1.0)
MNG-3260
MJAVADOC-116
... however, I'm not confident enough in the relationship to create the links myself
  
> 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.0.11
>
>         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

       

Mime
View raw message