+1, we've been using this trick for some years now to be sure nobody could
send their logs basically to /dev/null without being noticed.
In the meantime, as we actually control the corp pom, we also both added
the exclusions everywhere we could + enabled a bannedDependencies on
commons-logging.
Gr
(TL;DR: Use this repo and the versions on your dependencyMgmt:
http://version99.qos.ch/)
a hack, but works like a charm:
http://day-to-day-stuff.blogspot.com.br/2007/10/announcement-version-99-does-not-exist.html
--
-- Aldrin Leal,
Master your EC2-fu! Get the latest ekaterminal public beta
htt
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
element that I want to introduce would allow either slf4j's
binder to advert
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
the-s-project
...
pom
import
Now I'd like to exc
