You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2013/07/22 02:21:04 UTC
[Bug 55289] New: Log4J Extras contains duplicate classes
https://issues.apache.org/bugzilla/show_bug.cgi?id=55289
Bug ID: 55289
Summary: Log4J Extras contains duplicate classes
Product: Log4j
Version: 1.2.17
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Companions
Assignee: log4j-dev@logging.apache.org
Reporter: nojspam@losgibsons.us
CC: log4j-dev@logging.apache.org
Created attachment 30610
--> https://issues.apache.org/bugzilla/attachment.cgi?id=30610&action=edit
Adjusts the OSGi configuration to prevent it from copying the classes from
Log4J.
Although it looks like you tried to remove the duplicate classes from Log4J
from the extras jar in <a
href="http://svn.apache.org/viewvc?view=revision&revision=1481778">commit
1481778</a>, the attempt was unsuccessful. After poking around I've found that
the felix-maven-bundle plugin is still copying in all of the classes from the
original Log4J jar.
This is because the underlying BND tool is trying to unify the split packages
between the two different jars. The enclosed patch will prevent BND from doing
this while still behaving properly in an OSGi environment.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[Bug 55289] Log4J Extras contains duplicate classes
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=55289
--- Comment #1 from a6537691@bofthew.com ---
The problem is still there. The current download of
apache-log4j-extras-1.2.17-src.zip, for example, does not contain the
AsyncApender class, but the apache-log4j-extras-1.2.17-bin.zip does.
And what's worse, it contains some older version, with a bug from 2002 still
not fixed (this one: https://issues.apache.org/bugzilla/show_bug.cgi?id=5932).
I worked it around by compiling it by myself from the source distribution.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
[Bug 55289] Log4J Extras contains duplicate classes
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=55289
--- Comment #2 from Jess Holle <je...@ptc.com> ---
There was a 1.2.17.1 that addressed this issue.
But it was never officially released. Looking back at the mail archives it
looks like this got 1 vote and then no more because some folk saw failures on 1
automated test on Windows with Java 7. The thread appears to just fizzle out,
rather than anyone getting to the bottom of that 1 test failure and releasing
something. For myself I just use 1.2.17.1 -- released or not.
(In reply to Viliam Anirud from comment #1)
> The problem is still there. The current download of
> apache-log4j-extras-1.2.17-src.zip, for example, does not contain the
> AsyncApender class, but the apache-log4j-extras-1.2.17-bin.zip does.
>
> And what's worse, it contains some older version, with a bug from 2002 still
> not fixed (this one:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=5932).
>
> I worked it around by compiling it by myself from the source distribution.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org