On Fri, Apr 27, 2012 at 11:40 AM, J.V. <jvsr...@gmail.com> wrote: > I understand how Maven resolves dependencies (and transitive dependencies) > at compile time, but does it bring anything to the table at run time? > > 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? > > At runtime which one does it choose? If I am executing the code that > depends on version 8, how would the correct jar be in the classpath at that > point and later log4J version 15 be in my classpath when code that has that > dependency executes? > > At runtime, Maven is out of the picture correct? This is a missing piece > for me.
There was a blog post some time back about incorporating Maven as a runtime classpath manager, I don't think it went in this direction. You are looking, I think, for OSGi. It is true that 'classworlds', the internal structure in Maven that allows different plugins to have different versions of different things in their classpaths, is an open source component that you could apply, but nothing in Maven will help you set that up unless you want to structure all your code as maven plugins. > > thanks > > J.V. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
