I work on a large application that is built with Maven 1. It has numerous subproject directories.
At one point we realized that it would be handy to write a custom build step that would utilize a custom PMD rule class, along with some Ant code that uses the XMLTask library. The Ant code parses all the Spring context files to determine some candidate bean classes to process through the PMD rule. I tested this in an isolated environment, just using Ant. It works fine. My problem is that I can't figure out the best way to integrate this into Maven (1), with the assumption that the PMD custom rule class has two roles, both project source code and compiled class. I could just punt and manually build a jar file with the compiled PMD rule class and store that in the project dependencies, but that seems to have a smell. What I'd like is if there is a change to the PMD class (or perhaps a new one added to the set), the build would first compile those, and then the steps that process the normal project source code would reference that PMD class. Any ideas about how to best structure this? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
