Hi, On Mon, Oct 25, 2010 at 1:46 PM, Benson Margulies <[email protected]> wrote: > > Have a look, some time, at the POM structure at cxf.apache.org. The > shared parent is over 1,500 lines. A notable fraction of that is > dependency exclusions, which in some cases are repeated, over and over > and over, because all of the Spring artifacts have all of the same > unwanted dependencies.
My top-level corporate POM is over 3,000 lines long, mostly for dependencyManagement and default plugin configurations. The bonus is that most of my satellite POMs are less than 100 lines long. Anyhow, a very clever way to bypass the problem you guys have with specifying exclusions for multiple artifacts (presumably commons-logging) is to specify them as dependencies but with scope=provided. Then you need not specify, let alone repeat, exclusions anywhere else.. Before The Maven Way Police come banging down my office door, I should say that the scope is not being abused in that we use slf4j everywhere and so the jcl-over-slf4j really does justify the scope=provided -- but regardless, only the most die hard Mavenites would critique you on this subtle point. -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
