Maven 2 & 3

pluginManagement not consulted when building from lifecycle forked via javdoc reports

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 2.1.0-M1
  • Fix Version/s: 2.1.0-M1
  • Component/s: Plugins and Lifecycle
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

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).

Activity

Hide
John Casey added a comment -

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.

Show
John Casey added a comment - 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.
Hide
John Casey added a comment -

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.

Show
John Casey added a comment - 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.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: