pluginManagement not consulted when building from lifecycle forked via javdoc
reports
-------------------------------------------------------------------------------------
Key: MNG-3743
URL: http://jira.codehaus.org/browse/MNG-3743
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.1.0-M1
Reporter: John Casey
Priority: Blocker
Fix For: 2.1.0-M1
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).
--
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
