[MJAVADOC-310] compiler plugin settings aren't inherited from parent for linking Java API links

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7
• Environment: Maven 2.2.1, maven-compiler-plugin 2.3.2
• Assignee: Unassigned
• Reporter: Michael Osipov
• Created: 26/Feb/11 07:50
• Updated: 19/Dec/19 12:29
• Resolved: 19/Dec/19 12:29

Description

I set my m-c-p version in my parent's pluginManagement section but did not alter source and target because I am fine with 1.5.

Now another project references it and complains that the above setting is not available:

[INFO] Generating "JavaDocs" report.
[DEBUG] No maven-compiler-plugin defined in ${build.plugins} or in ${project.build.pluginManagement} for the <groupId>:url-provider-api:jar:0.1-SNAPSHOT. Added Javadoc API link according the javadoc executable version i.e.: 1.6
[DEBUG] Found Java API link: http://java.sun.com/javase/6/docs/api/
[DEBUG] Try to add links for dependencies...

The behavior is incorrect. Either m-javadoc-p ignores the plugin's default settings or it does not merge the model.

Issue Links

• is duplicated by: MJAVADOC-421 Set ${maven.compiler.source} as the default value for source parameter
• is related to: MPMD-170 Have targetJdk default to maven.compiler.target
• relates to: MPIR-263 improve minimum java requirement when m-compiler-p not explicitely configured: use default properties
• relates to: MPLUGIN-279 improve jdk requirement when m-compiler-p not explicitely configured: use default properties