[
http://jira.codehaus.org/browse/MNG-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205366#action_205366
]
Benjamin Bentmann commented on MNG-3283:
----------------------------------------
The constellation is just flawed: If a plugin has requiresDependencyResolution,
i.e. asks for artifact files, and does so in phases like "validate", i.e.
before even compilation occurs, how should Maven satisfies this requirement if
not from the repo? The reactor is simply empty in terms of build output at this
point of the build.
Plugins like the Enforcer which don't actually need the artifact files but only
the dependency graph should be updated to use the new anno
@requiresDependencyCollection (MNG-4331).
> Plugins that require dependency resolution in early phases cause dependency
> resolution issue
> --------------------------------------------------------------------------------------------
>
> Key: MNG-3283
> URL: http://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
> Assignee: Brian Fox
> 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 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
