[#MNG-3743] pluginManagement not consulted when building from lifecycle forked via javdoc reports

Maven 2

pluginManagement not consulted when building from lifecycle forked via javdoc reports

Created: 04/Sep/08 03:10 PM Updated: 08/Sep/08 12:12 PM

Component/s:

Plugins and Lifecycle

Affects Version/s:

2.1.0-M1

Fix Version/s:

2.1.0-M1

Time Tracking:

Not Specified

Complexity:

Intermediate

Description

« Hide

if you use java5 generics or java 1.4 assertions, and you have the compiler plugin configured with source and target parameters inside a plugin entry in the pluginManagement section of the POM, this configuration is not used when building from a forked lifecycle spawned from a report. The classic example here is the javadoc reports, which trigger the compilation of sources (for some reason).

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

John Casey added a comment - 04/Sep/08 03:39 PM

ok, the reason this is triggering compilation is because javadoc:test-aggregate forks to generate-test-sources, which is later than the compile lifecycle phase.

[ Permlink | « Hide ]

John Casey added a comment - 08/Sep/08 12:12 PM

executionProject was not being used to verify plugins in a forked lifecycle. This meant that when pluginManagement information was injected, it was added to a project instance that wasn't actually being used to execute the plugin, and the plugin never saw the injected configuration parameters.