Mike Perham wrote: > I updated the PMD plugin to use plugin-parent 2.0.1 instead of 2.0 and > it started generating the documentation. Does this force the use of > maven 2.0.1? I believe so because plugin-parent 2.0.1 pulls in > maven-project 2.0.1.
It will still use the installed maven-project. The risk is that you use something specific to 2.0.1 and it breaks in 2.0 without you knowing. There's a low risk of that in these minor increments though. > > Is it better to just list the plugin report in PMD's POM instead? As a > user, I hate it when a plugin mandates a newer maven version so I want > to maintain backwards compatability where possible. It only mandates it with prerequisites set. I'd say go with the 2.0.1 parent. We need to resolve this in general and will take care of it then. I'm all for putting the plugin-api and maven-project dependencies into each POM. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
