[
https://jira.codehaus.org/browse/MJAVADOC-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355433#comment-355433
]
Michael Osipov edited comment on MJAVADOC-310 at 11/2/14 12:21 PM:
-------------------------------------------------------------------
I am little bit confused by the consequence. The use must not add this but can
directly provide that parameter in the plugin option. With the property though,
we have a unique value for several plugins and those do not need to query
{{maven-compiler-plugin}} settings which are incomplete due to one-way
resolution only.
So these work:
{code}
<sourceVersion>1.7</sourceVersion>
{code}
or
{code}
<properties>
<maven.compiler.source>1.6</maven.compiler.source>
</properties>
...
<sourceVersion>${maven.compiler.source}</sourceVersion>
{code}
or just
{code}
<properties>
<maven.compiler.source>1.6</maven.compiler.source>
</properties>
{code}
What would be the alternative for now, imho none and what problems does it
cause? I highly doubt that people do not set {{maven.compiler.source/target}}
these days.
was (Author: michael-o):
I am little bit confused by the consequence. The use must not add this but can
directly provide that parameter in the plugin option. With the property though,
we have a unique value for several plugins and those do not need to query
{{maven-compiler-plugin}} settings which are incomplete due to one-way
resolution only.
So these work:
{code}
<sourceVersion>1.7</sourceVersion>
{code}
or
{code}
<properties>
<maven.compiler.source>1.6</maven.compiler.source>
</properties>
...
<sourceVersion>${maven.compiler.source}</sourceVersion>
{code}
or just
{code}
<properties>
<maven.compiler.source>1.6</maven.compiler.source>
</properties>
{code}
What would be the alternative for now, imho none and what problems does it
cause? I highly double that people do not set {{maven.compiler.source/target}}
these days.
> 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)
