[ https://jira.codehaus.org/browse/MPMD-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=327578#comment-327578
]
Robert Scholte commented on MPMD-170:
-------------------------------------
AFAIK most plugins trust the configuration, which is not so get through the MavenProject and/or
Model. If it is not configured, they assume the default. But you will still be missing the
injected values, but that's just a small percentage (for example MPIR-263).
In both cases I'd like to refer to {{org.apache.maven.report.projectinfo.ProjectSummaryReport}}.
> Have targetJdk default to maven.compiler.target
> -----------------------------------------------
>
> Key: MPMD-170
> URL: https://jira.codehaus.org/browse/MPMD-170
> Project: Maven 2.x 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|