[
https://issues.apache.org/jira/browse/SOLR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505426
]
Hoss Man commented on SOLR-143:
-------------------------------
1) i never got a chance to look into the license issues of including the XSLT
for
formating the PMD output in solr
2) since opening this issue, i have found better ways to do things with PMD
instead of needing to run the analysis twice.
It might be best to just pursue the clover integration separately from the PMD
stuff since many people use IDEs that have "code inspectors" for doing PMD type
stuff built into them. ... then we can revist PMD later if we want.
> Support for PMD and Clover
> --------------------------
>
> Key: SOLR-143
> URL: https://issues.apache.org/jira/browse/SOLR-143
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Priority: Minor
> Attachments: pmd-and-clover.diff, SOLR-143-CloverAndPMD.patch
>
>
> had some time on a plane this weekend, so I adapted some of the clover hooks
> from Java-Lucene to Solr's build.xml and also put in hooks for running PMD (a
> bug pattern finding tool).
> the PMD hook actually teste the PMD ruleset twice, once warning about any
> violations, and once failing the build if any serious violations were found
> ... the goal would be to hook this into the "ant test" target so you can't
> successfully build if you have any serious rule violations.
> i strarted with a custom ruleset based on some of the bigger rules from PMD
> ... the theory being that as well clean up the code base we can add more
> nit-picky rules if we want to :)
> User is required to provide their own copy of PMD and/or clover on in an
> ANT_LIB. Clover requires (ASF committer) license, PMD is freely available...
> http://pmd.sourceforge.net/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
