On 27 April 2012 12:27, J.V. <jvsr...@gmail.com> wrote: > > > On 4/27/2012 10:04 AM, Ron Wheeler wrote: >> >> On 27/04/2012 11:40 AM, J.V. wrote: >>> >>> I understand how Maven resolves dependencies (and transitive >>> dependencies) at compile time, but does it bring anything to the table at >>> run time? >> >> It makes your artifacts that your run-time environment will execute. >> It is a build tool. >>> >>> >>> For example, if I have in my application dependency list two versions of >>> log4J (let's say version 8 and version 15), will I deploy both jars/version >>> along with my app on say a tomcat server inside the war? >> >> Fix it so you only have 1. >> Settle on the "right" versions of third party libraries and use >> "exclusions" in your dependencies to prevent other libraries from grabbing >> older versions. > > => this is a very tedious task. I have to be godlike to know the > transitive dependencies and what libraries they use, and inspect my local > repository, find out all dups of everything, find out which top level > dependency needs it and go exclude this. This is a maintenance nightmare.
It's not nearly that bad. Firstly, it's rarely an issue and Maven usually does the right thing. Secondly, Maven offers tools to see what is used. Moreover, IDEs like Eclipse (with the Maven plugin) allow you to see what JARs are included and why. It's not nearly as onerous as you make it out to be. :-) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
