[
https://jira.codehaus.org/browse/MNG-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341529#comment-341529
]
Jason van Zyl commented on MNG-3283:
------------------------------------
What goals are people trying to run for this case. All of these failures are
happening because of the logic present in the ReactorReader and the implicit
definition of resolution in Maven in that an artifact is not resolved unless a
file can be found for the artifact trying to be resolved. I believe what people
expect is that in the reactor the project is there so it should therefore be
resolved. No file is attached to the artifact until the maven-compiler-plugin
runs and attaches the target/classes directory or after the package phase when
the archive is created.
It is possible to change this logic but I'm curious how people are using it. If
it's for eclipse project file generation then I would recommend using m2eclipse
for a number of reasons. The maven-eclipse-plugin reimplements all sorts of
weird logic to acccount the fact that Maven doesn't consider an artifact
resolved until a file is attached. For a custom that I'm helping to migrate to
Maven we created a new version of the ReactorReader and a modified
maven-eclipse-plugin to deal with this specific case. But we plan not to use
this at all once the full conversion is completed. Again, I would use m2e if
this is the problem you're running into.
If there are other cases I'm interested.
> Plugins that require dependency resolution in early phases cause dependency
> resolution issue
> --------------------------------------------------------------------------------------------
>
> Key: MNG-3283
> URL: https://jira.codehaus.org/browse/MNG-3283
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies, Plugins and Lifecycle, Reactor and
> workspace
> Affects Versions: 2.0.7
> Reporter: Alfie Kirkpatrick
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: maven-dependency-bug.zip
>
>
> What we're seeing is that some multi-project configurations succeed on
> 'mvn package' but fail on 'mvn generate-sources'. They are failing when
> one project in the reactor references another project in the reactor
> which is not installed in the local repo. It seems that the referenced
> project has not quite "made it" into the reactor this early in the phase
> lifecycle. But it does work correctly if you target a later phase at the
> outset which is really confusing.
> The problem only occurs when a plugin binds itself to the
> generate-sources phase and has @requiresDependencyResolution, presumably
> because this is what triggers resolution of the referenced dependency
> too early in the lifecycle, and hence the error.
> We are seeing this problem when trying to run 'mvn eclipse:eclipse'
> because this only executes the generate-sources phase by default and we
> have other mojos which genuinely do generate source, such as java2wsdl.
> A workaround we're using is to run 'mvn process-classes eclipse:eclipse'.
> Attached is a really simple project that exhibits this problem.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
