[
https://jira.codehaus.org/browse/MJAVADOC-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355432#comment-355432
]
Robert Scholte commented on MJAVADOC-310:
-----------------------------------------
I've asked [~jason] to have a look at this concept. The consequence of this
solution is that users must add
{{<maven.compiler.source>someValue</maven.compiler.source>}} to the properties
of their pom. It's not a beautiful solution, but it might be the best solution
for now. This also means, that you should advice users to use a property
instead of a configuration entry, first of all in the maven-compiler-plugin for
the source parameter. That's kind of weird, but that's the result of this
solution.
> compiler plugin settings aren't inherited from parent tor linking Java API
> links
> --------------------------------------------------------------------------------
>
> Key: MJAVADOC-310
> URL: https://jira.codehaus.org/browse/MJAVADOC-310
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.7
> Environment: Maven 2.2.1, maven-compiler-plugin 2.3.2
> Reporter: Michael Osipov
>
> 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:
> {noformat}
> [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...
> {noformat}
> The behavior is incorrect. Either m-javadoc-p ignores the plugin's default
> settings or it does not merge the model.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
