[jira] Created: (MNG-3685) Dependency can't be resolved but has been found in the reactor.

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


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

     [ http://jira.codehaus.org/browse/MNG-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-3685:
------------------------------

    Fix Version/s: 2.0.11

it looks like this got missed for 2.0.10 so we should review for 2.0.11.

Do you have a sample project?

> 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
>
>
> 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

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

Brett Porter commented on MNG-3685:
-----------------------------------

Ah, I've now seen this myself.

I think this is a failure condition - it's a resolution error - at the least.

Though I don't understand why it isn't sufficient to use the one from the reactor - it sounds like it is just being precautionary against goals that need the actual artifacts.

> 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
>
>
> 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

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

Jörg Hohwiller commented on MNG-3685:
-------------------------------------

This only happens for SNAPSHOT versions if that helps. Anyhow if it is a module in the reactor there can be no more actual place than that.

> 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
>
>
> 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

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

Kaizer Sogiawala commented on MNG-3685:
---------------------------------------

We have seen this happen with release artifacts too.

> 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
>
>
> 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

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

Borut Bolcina commented on MNG-3685:
------------------------------------

We are having this issue too. When doing mvn release:prepare and the artifact was not installed previously, it complains with "...SNAPSHOT can't be resolved but has been found in the reactor.". We use Maven 2.0.9.

> 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
>
>
> 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

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

Torben S. Giesselmann commented on MNG-3685:
--------------------------------------------

Could someone provide a sample project?

> 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
>
>
> 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

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

Jochen Hinrichsen commented on MNG-3685:
----------------------------------------

Attached a sample project. It consists of two modules, module-1 depending on module-common. Executing 'mvn release:prepare' produces:

[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   Module Common
[INFO]   Module #1
[INFO]   Simple Maven Multi-Module Project
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO] ------------------------------------------------------------------------
[INFO] Building Simple Maven Multi-Module Project
[INFO]    task-segment: [release:prepare] (aggregator-style)
[INFO] ------------------------------------------------------------------------
Downloading: (some repo)
Downloading: (more repos)
[WARNING] The dependency: name.hinrichsen.jochen:module-common:jar:1 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.

[INFO] [release:prepare]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE


I tried both maven 2.0.8, 2.0.10 and 2.1.0 - same problem. I also ran the sonatype 'Definitive Guide' multi-module example in chapter 6 - same problem.

Not sure if this is a release plugin or a maven issue. The proposed solution from thread http://www.mail-archive.com/users@.../msg75486.html is to make the release plugin execute an 'install' lifecycle:

         <configuration>
           <preparationGoals>clean install</preparationGoals>
         </configuration>

Also does not work for me.

> 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

     [ http://jira.codehaus.org/browse/MNG-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Hinrichsen updated MNG-3685:
-----------------------------------

    Attachment: sample-MNG-3685.tgz

> 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

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

Jochen Hinrichsen commented on MNG-3685:
----------------------------------------

Any new insights regarding this issue after one month?

> 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

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

Zac Thompson commented on MNG-3685:
-----------------------------------

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

    [ 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

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

Wim Deblauwe commented on MNG-3685:
-----------------------------------

I am having the same issue, also with

mvn release:prepare -DpreparationGoals="clean 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.1
>
>         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

    [ 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

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

Anthony Whitford commented on MNG-3685:
---------------------------------------

I seem to be experiencing this problem with the latest Javadoc plugin.  I would characterize the issue as a *Blocker*!

> 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