[MNG-3283] Plugins that require dependency resolution in early phases cause dependency resolution issue

• Type: Bug
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0.7
• Fix Version/s: Issues to be reviewed for 4.x
• Component/s: Dependencies, Plugins and Lifecycle, Reactor and Workspace
• Assignee: Unassigned
• Reporter: Alfie Kirkpatrick
• Created: 12/Nov/07 15:07
• Updated: 27/Nov/20 12:16

Description

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.

Issue Links

• Blocked: MANTRUN-216 CLONE - Use of AntRun during clean phase fails multiproject with intermodule dependencies
• is depended upon by: MANTRUN-78 Use of AntRun during clean phase fails multiproject with intermodule dependencies
• is depended upon by: MENFORCER-42 Maven-Enforcer-Plugin fails in multimodule project when artifacts not in repository
• is depended upon by: MJAVADOC-116 Impossible to aggregate javadoc if snapshot never built
• is duplicated by: MNG-4331 Add new requiresDependencyCollection mojo feature (with corresponding annotation) to grab dependency tree without files
• is duplicated by: MECLIPSE-380 dependencies in multi-module may projects require a 'mvn install' before using
• is related to: MENFORCER-304 Improve dependency resolving in multiple modules project
• is related to: MDEP-409 dependency:tree fails for a multi-module project where one module depends on another and "mvn install" has not been run yet
• is related to: MDEP-410 Add dependency:collect goal which prints the dependency list by resolving the POMs only
• is related to: MNG-2277 aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue
• is related to: MNG-4331 Add new requiresDependencyCollection mojo feature (with corresponding annotation) to grab dependency tree without files