Dependency can't be resolved but has been found in the reactor.

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

Do you have a sample project?

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.

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.

We have seen this happen with release artifacts too.

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.

Could someone provide a sample project?

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@maven.apache.org/msg75486.html is to make the release plugin execute an 'install' lifecycle:

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

Also does not work for me.

Any new insights regarding this issue after one month?

-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

I am having the same issue, also with

mvn release:prepare -DpreparationGoals="clean install"

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

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

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.