On 4/27/2012 1:37 PM, Hilco Wijbenga wrote:
On 27 April 2012 12:19, J.V.<[email protected]> wrote:
this is the issue (that only one artifact is picked). How does it know to
pick the right one?
What if log4j ver 1.2.15 has a method that log4j 1.2.10 does not have?
You use 1.2.15.
also what if both jars have a method with the same signature but function
differently?
You upgrade or downgrade something else until everything works with
the same version of log4j.
can't do this. one version will break something if the method
signatures are the same yet have different functionality.
I think the answer from this thread to switch a new version of jar
in/out at run time to get the right version is OSGi.
In this case you need both jars and at runtime to have the right jar in the
classpath for that piece of code.
You can't have multiple versions of the same JAR on the classpath and
expect things to work. At best, only the first one found is used and
the others are ignored but usually your app develops all kinds of
interesting features. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
