Re: [m2] best practices on defining dependencies: i.e. how to avoid the kitchen sink

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 solutio

Re: [m2] best practices on defining dependencies: i.e. how to avoid the kitchen sink

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 provi

[m2] best practices on defining dependencies: i.e. how to avoid the kitchen sink

I just added a dependency on EasyConf easyconf easyconf 0.9.5 and now I have a lot of dependencies which I don't need. I think this is because the dependencies listed in EasyConf pom needs to be more strictly defined. For example there are api dependencies and im