Sebastien: On my current assignment, we solved this by having one POM for the main dependencies of all projects, and a child POM called WebDependencies. All child projects of type WAR specify WebDependencies as a direct dependency. This *does* include transitive dependencies -- but you should be able to trim down the list of total dependencies included by a significant amount. (The ones you probably actually need.) If you bundle your WAR in an EAR, you can use this Dependencies POM in both the EAR and WAR projects and suppress everything in the WAR's WEB-INF/lib to eliminate duplication further. Hope that helps. Barrett Barrett Nuzum Consultant, Skill Development [EMAIL PROTECTED] T: +1 (918) 640 4414 F: +1 (972) 789 1340
Valtech 5080 Spectrum Drive Suite 700 West Addison, Texas 75001 USA T: +1 (972) 789 1200 ________________________________ From: Sebastien Brunot [mailto:[EMAIL PROTECTED] Sent: Tue 11/7/2006 10:13 AM To: Maven Users List Subject: Transitive dependecies Hi all, transitive dependencies can be a real pain when you have a lot of external dependencies in your project. Using <exclusions> tags is a tedious operation in this case, so I was wondering if a quicker way exists... How can one create a pom module that contains a list of dependencies (let's name it "lib pom"), so that when the lib pom is added as a dependecy in let's say a war project, the exact list of dependencies from lib pom (no more, no less => no transitivity) are added to the war WEB-INF/lib ? Thanks for your help, Sebastien
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
