Oh I didn't understand the question the first time! Went back and now I understand better... Ignore my first response completely. ;-)
I would just add the jar file as follows: <plugin> maven-pmd-plugin etc <dependencies> <dependency> your jar here </dep> </deps> </plugin> However... I think right now, the maven-pmd-plugin does not support custom rulesets, so either way you're going to need to run an internal/private version for a while until the next release is pushed out that supports custom XML rulesets. Wayne On 3/18/06, Subhash Chandran <[EMAIL PROTECTED]> wrote: > ---- quote start ---- > Personally, I think you should Maven2-ize the other project, and run > PMD directly on it, instead of doing this convoluted thing... > ---- quote end ---- > > Well, even if I mavenize our plugin-extension project, where will I add the > dependency? The only logical place I can believe is PMD plugin's dependency > section. This would mean we, in our company maintaining a fork version of > PMD plugin, which we want to avoid. > > Regards, > Subhash. > > On 3/18/06, Wayne Fay <[EMAIL PROTECTED]> wrote: > > > > Perhaps need to use assembly plugin to unzip the the Jar and then let > > PMD run on the classes directly? > > > > (Personally, I think you should Maven2-ize the other project, and run > > PMD directly on it, instead of doing this convoluted thing...) > > > > Wayne > > > > > >
