Comments on: Resolving log4j 1.2.15 dependency problems in Maven using exclusions

By: Chriki™

Chriki™ — Wed, 17 Feb 2010 11:52:45 +0000

Thanks very much for the detailed explanations. I’m only doing my first steps with Maven so this helped me a lot.

By: Martin Willitts

Martin Willitts — Wed, 04 Nov 2009 15:58:26 +0000

Thanks. This helped me out enormously.

By: Marshall Schor

Marshall Schor — Tue, 22 Sep 2009 05:39:04 +0000

I tried doing this, and for some strange reason, the maven eclipse:eclipse insisted on treating the log4j as an Eclipse “project” instead if just referring to jar in my local .m2 repository. This of course made my project using log4j fail to build, because I don’t have log4j as an Eclipse project in my workspace.

Using 1.2.14 without the excludes – worked fine.

Any ideas why eclipse:eclipse is acting up on this one? (I’m using version 2.7 of the maven eclipse plugin)

By: Dire

Dire — Mon, 31 Aug 2009 19:13:24 +0000

If you just use the log4j 1.2.14 instead of 1.2.15, things will be much easier.

By: Piotr

Piotr — Sat, 29 Aug 2009 21:01:19 +0000

Thanks, it was very helpful!

… and maven/sun licencing problem very annoing – and for years not resolved

By: Gabriel

Gabriel — Fri, 21 Aug 2009 14:30:03 +0000

Thanks! Exactly the information I needed!

I didn’t knew that the missing jar files where absent because of licencing issues.

I’m astonished that such a problem is not addressed by maven, or at least the m2eclipse plugin.
Something minimal, like adding a licensing text inside the pom, and request the user to accept the licence by clicking a button (inside the eclipse plugin), or setting some flag in the local repository directory structure (like adding an empty file “licence-ok.txt”)

Anyway…Great post!