[
https://jira.codehaus.org/browse/MPMD-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355429#comment-355429
]
Michael Osipov edited comment on MPMD-170 at 11/2/14 8:42 AM:
--------------------------------------------------------------
I'd like to fix this finally by apply to proposed fix. As you have already
[layed
out|http://jira.codehaus.org/browse/MJAVADOC-310?focusedCommentId=354200&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-354200]
Robert, plugins should not know of each other. Reading compiler plugin's
config is the wrong way to go. If no one opposes, I will by default provide
{{maven.compiler.target}}.
was (Author: michael-o):
I'd like to fix this finally by apply to proposed fix. As you have already
layed out Robert, plugins should not know of each other. Reading compiler
plugin's config is the wrong way to go. If no one opposes, I will by default
provide {{maven.compiler.target}}.
> Have targetJdk default to maven.compiler.target
> -----------------------------------------------
>
> Key: MPMD-170
> URL: https://jira.codehaus.org/browse/MPMD-170
> Project: Maven PMD Plugin
> Issue Type: Improvement
> Components: PMD
> Affects Versions: 3.0.1
> Reporter: Stevo Slavic
> Priority: Minor
> Attachments: MPMD-170.patch
>
>
> Currently {{targetJdk}} has to be defined separately from
> {{maven.compiler.target}} property that most plugins already default to, so
> target JDK information is unnecessarily repeated, making POMs with
> maven-pmd-plugin less DRY, harder to maintain, prone to mistakes and unwanted
> behavior.
> So, please make {{targetJdk}} default to {{maven.compiler.target}} property.
> Attached is [^MPMD-170.patch] which adds this behavior.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
