You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2015/01/05 22:29:10 UTC

[jira] (MPMD-170) Have targetJdk default to maven.compiler.target

    [ https://jira.codehaus.org/browse/MPMD-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360728#comment-360728 ] 

Michael Osipov commented on MPMD-170:
-------------------------------------

[~hboutemy], no opinion?

> 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
>            Assignee: Michael Osipov
>            Priority: Minor
>             Fix For: 3.4
>
>         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)