FYI. I just sent this to Matt Raible (the author of appfuse) who has asked for global exclusions in Maven. -------- Original Message -------- Subject: global exclusions in Maven Date: Sat, 27 Feb 2010 15:09:12 +0100 From: Ceki Gülcü <ceki@qos.ch> To: matt@... CC: Ceki Gulcu <ceki@qos.ch> Hello Matt, I just wanted to inform you that even without global exclusions in Maven, it is still possible to exclude commons logging quite conveniently. Given that jcl-over-slf4j is a perfect binary replacement for commons logging, simply declare commons-logging in the provided scope in the a project top-level pom.xml file. This translates into the following pom file snippet: <dependency> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> <version>1.1.1</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>jcl-over-slf4j</artifactId> <version>1.5.11</version> </dependency> There is an SLF4J FAQ entry discussing this same point [1]. I don't believe global exclusions would buy us anything more than what is already available by declaring CL in the provided scope. Cheers, -- Ceki [1] http://slf4j.org/faq.html#excludingJCL