On 27/04/2012 3:37 PM, Hilco Wijbenga wrote:
On 27 April 2012 12:19, J.V.<jvsr...@gmail.com> 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.
Or you use another library. Upward compatibility is a sign of a well-run
utility project.
If their new version breaks code that uses the older version without
error, that is a warning that their QC process is not under control or
they just don't care.
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
