Hi Betrand, Am Montag, den 28.01.2008, 11:01 +0100 schrieb Bertrand Delacretaz: > On Jan 28, 2008 10:41 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > > > ...To get a complete list of dependencies we would have to analyze the > > dependencies of each pom just like the maven's dependency report does.... > > I think this does it, if run from the top of our source code tree > (assuming all modules are listed in the main pom.xml): > > mvn dependency:resolve | grep ':.*:.*:.*' | grep -v "Finished at" | > cut -d ':' -f 1-4 | sort -u
Cool trait ! Thanks for this. > > The resulting list also shows some "interesting" duplicates like: > > commons-httpclient:commons-httpclient:jar:3.0 > commons-httpclient:commons-httpclient:jar:3.1 > > And > > commons-logging:commons-logging:jar:1.0.3 > commons-logging:commons-logging:jar:1.0.4 > commons-logging:commons-logging:jar:1.1 > > And a few others like this. These could be caused by transitive dependencies. Still we might want to analyze our poms. But I think, except for inter-Sling dependencies we define all our versions in the parent pom. Regards Felix
