The hack way I would use is to create an intermediate "wrapper" project and then you can define exclusions on that wrapper at the pom level directly.
Other than that you just have to wait for model version 5.0.0 when the <provides> element that I want to introduce would allow either slf4j's binder to advertise that it "provides" commons-logging, or you would be able to state that in your <dependency> directly On 20 January 2014 09:03, Stephane Nicoll <stephane.nic...@gmail.com> wrote: > Hi, > > Has anybody thought (or worked on) the ability to exclude dependencies from > the import of a pom for a given project. > > Let's say that project S uses commons-logging and we use that project in > our project. We have something like > > <dependency> > <groupId>....</groupId> > <artifactId>the-s-project</artifactId> > <version>...</version> > <type>pom</type> > <scope>import<scope> > </dependency> > > Now I'd like to exclude the "commons-logging" dependency from the whole > project so that I can use the slf4j binder instead. > > Thoughts? > > Thanks, > S. >
