Two things can be done on this matter: Short term solution: add an extra excludes/exclude element to your dependency which allows for transitive dependencies filtering. (You can include it in your dependencyManagement section of your parent pom if your project is multi-module).
Long term solution: If you are confident pom is wrong and dependency scope/optionnal shoudl be corrected, you can submit an issue to http://jira.codehaus.org/browse/MEV after having read http://maven.apache.org/guides/mini/guide-maven-evangelism.html Denis baerrach wrote: > > I'm sure there are probably other pom's out there that do not > correctly define the dependencies. So in these cases what is the > suggested way of overriding them so they are not included? Including > the dependency again and using optional doesn't fix the problem, > nor does changing the scope to provided, but this might be because > EasyConf depends on xdoclet:xdoclet:jar:1.2.1 which is not available > at ibiblio. > > Cheers > Bae > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/-m2--best-practices-on-defining-dependencies%3A-i.e.-how-to-avoid-the-kitchen-sink-tf2070286.html#a5701865 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
