[jira] Commented: (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:comment-tabpanel&focusedCommentId=199689#action_199689 ] Anthony Whitford commented on MNG-3685: --- I seem to be experiencing this problem with the latest J

[jira] Commented: (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:comment-tabpanel&focusedCommentId=184082#action_184082 ] Antony Stubbs commented on MNG-3685: I've also hit the problem, even using mvn release:prepare -Da

[jira] Commented: (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:comment-tabpanel&focusedCommentId=182686#action_182686 ] Wim Deblauwe commented on MNG-3685: --- I am having the same issue, also with mvn release:prepare -Dpre

[jira] Commented: (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:comment-tabpanel&focusedCommentId=180493#action_180493 ] Zac Thompson commented on MNG-3685: --- Is this the same root cause as MRELEASE-3 ? The above has existe

[jira] Commented: (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:comment-tabpanel&focusedCommentId=175740#action_175740 ] Jochen Hinrichsen commented on MNG-3685: Any new insights regarding this issue after one month?

[jira] Commented: (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:comment-tabpanel&focusedCommentId=172533#action_172533 ] Jochen Hinrichsen commented on MNG-3685: Attached a sample project. It consists of two modules,

[jira] Commented: (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:comment-tabpanel&focusedCommentId=163598#action_163598 ] Torben S. Giesselmann commented on MNG-3685: Could someone provide a sample project? > Dep

[jira] Commented: (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:comment-tabpanel&focusedCommentId=150291#action_150291 ] Borut Bolcina commented on MNG-3685: We are having this issue too. When doing mvn release:prepare a

[jira] Commented: (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:comment-tabpanel&focusedCommentId=145789#action_145789 ] Kaizer Sogiawala commented on MNG-3685: --- We have seen this happen with release artifacts too. >

[jira] Commented: (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:comment-tabpanel&focusedCommentId=144320#action_144320 ] Jörg Hohwiller commented on MNG-3685: - This only happens for SNAPSHOT versions if that helps. Anyho

[jira] Commented: (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: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 condit