Hello Xavier
Thanks for the clarifications.
You were right, my ruleset file, basic.xml, which I copied from the
pmd-4.2.1 distribution
does contain the AvoidMultipleUnaryOperators rule. That rule indeed has
since=4.2.
When reverting to the pmd-4.1 distribution, with an earlier basic.xml
ruleset file, the problem is gone.
10x again
--Amir
Hi,
I saw your message on the pmd developer forum and on the maven lists.
Based on the forum post, you are using a custom ruleset that references
the AvoidMultipleUnaryOperators rule. That rule was introduced in pmd
4.2 and is not in pmd 4.1 nor is it referenced in the rulesets that ship
with pmd 4.1.
So the issue is not with the pmd plugin packaging but with how your
custom ruleset references a newer rule that is not available yet from
the pmd plugin.
Best regards,
Xavier Le Vourch
Amir Eliaz wrote:
| Hello,
| Looking in
|
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-pmd-plugin/2.3/maven-pmd-plugin-2.3.pom
| I found out it depends on pmd-jdk14-4.1.1.jar
| Now, this Jar does not contain net.sourceforge.pmd.rules
| .basic.AvoidMultipleUnaryOperators
| but the plugin implementation is looking for it.
| But, if your use pmd-4.2.1.jar (from
| http://repo1.maven.org/maven2/pmd/pmd/4.2.1)
| instead of pmd-jdk14-4.1.1.jar (by manually replacing in
~/.m2/repository),
| the class is found and everything works.
| So the problem really is a wrong dependency in maven-pmd-plugin-2.3.pom,
| which is the latest for this plugin.
|
| FYI
| --Amir
|
- --
Xavier Le Vourch
Brittany Software, Inc.
<[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
