[
https://jira.codehaus.org/browse/MPMD-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=327575#comment-327575
]
Stevo Slavic commented on MPMD-170:
-----------------------------------
Thanks [~rfscholte], I appreciate your quick review and feedback.
It would help even more if you could also provide some reference to docs or
existing code which does something like that proper solution you mentioned.
To run a report like pmd, which analyzes sources, compiler execution is not
needed. Which maven-compiler-plugin execution configuration of potentially more
than one configured should we read?
> 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
