[
https://issues.apache.org/jira/browse/MPMD-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409442#comment-15409442
]
Andreas Dangel commented on MPMD-213:
-------------------------------------
Since [r1682450|http://svn.apache.org/viewvc?view=revision&revision=1682450]
the language parameter isn't used at all. Instead, if the output file from the
`pmd` or `cpd` goal exists, the violations are examined.
There is a language parameter, but this one is for the `pmd`/`cpd` goals - and
this one is configurable.
[~denn...@apache.org] I believe, the language parameter in
`AbstractPmdViolationCheckMojo` can be removed completely. What do you think?
> The language parameter should not be read-only
> ----------------------------------------------
>
> Key: MPMD-213
> URL: https://issues.apache.org/jira/browse/MPMD-213
> Project: Maven PMD Plugin
> Issue Type: Bug
> Reporter: Dennis Lundberg
>
> The language parameter in {{AbstractPmdViolationCheckMojo}} should not be
> read-only. It should be possible to change it in case you have an artifact
> with a type of sources for which there is no artifact handler, i.e.
> javascript.
> The IT PMD-205-pmd-js-check shows this. It currently fails under Maven 2.2.1,
> but works under Maven 3 due to MNG-5001.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
