You could certainly create a seperate project/dependency with just your organizations config files etc, then specify it as a dependency in all projects, and perhaps finally use the Assembly plugin to unjar those files into the right place(s) in each project.
There has been some discussion around the lack of a dependency section in the report plugin section, and I'm sure something will be done to address this at some point, probably not before 2.1. Wayne On 3/29/06, Robert Biernat <[EMAIL PROTECTED]> wrote: > Hi, > > I'm using maven on a number of different projects. These projects all > generate websites containing reports generated by the checkstyle, pmd, and > jdepend report plugins. The checkstyle and pmd plugins reference config > files that are tailored to my organisations coding standards. At the moment > each project that wishes to use these standard config files needs to include > them within their project so theyre available when the plugin runs. I am > wondering whether its possible to create a seperate project that contains > these resources, install the jar into the repository and have the various > report plugins use it. I noticed that for report plugins I cannot specify > additional dependencies like I can with regular build plugins, so I'm sort > of stuck as to how I would do it. > > Rob > > > > >
