Is "maven.dependency.classpath" the classpath created by Maven of all the
dependencies listed in the <dependecies> section (I did not see this property
described on the Properties Reference page, or elsewhere)?
If so, then is the correct solution to install a jar of the custom rules in the
local repo and add it as a project dependency?
The PMD plugin.jelly has this:
<!-- Setup the classpath for pmd plugins -->
<path id="pmd-classpath">
<pathelement path="${plugin.getDependencyPath('pmd:pmd')}" />
<pathelement path="${plugin.getDependencyPath('jaxen:jaxen')}" />
<pathelement path="${plugin.getDependencyPath('saxpath:saxpath')}" />
<pathelement path="${pom.getDependencyClasspath()}" />
<path refid="maven.dependency.classpath" />
</path>
so, I think that would work. Would very much appreciate an expert's validation
of this and/or a better, more correct approach suggested!
Quoting Jeff Jensen <[EMAIL PROTECTED]>:
> I know to use maven.pmd.rulesetfiles to specify the rules config, but I'm not
> sure of the correct way to get the custom PMD rule Java class files on the
> classpath so the PMD plugin sees them.
>
> Can anyone advise on that, please?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
