log4j (main) should not depend on libjboss-jmx-java (universe)
Bug #522558 reported by
Thierry Carrez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| jakarta-log4j (Ubuntu) |
Fix Released
|
High
|
Thierry Carrez | ||
Bug Description
jakarta-log4j currently build-depends on (and suggests) libjboss-jmx-java to enable Log4J JMX support.
Solution 1: MIR libjboss-jmx-java
Unfortunately, it is impossible to push libjboss-jmx-java to main without having to MIR all jbossas4 [build-
Solution 2: Switch to libmx4j-java
mx4j provides an alternative JMX implementtation and is in main
Solution 3: Drop JMX support from log4j
This was recently enabled to allow pristine Zookeeper to use log4j, we'd need to disable Log4J/JMX support in Zookeeper.
Solution 2, if it works, is the best. Solution 3 is a fallback.
Related branches
| Changed in jakarta-log4j (Ubuntu): | |
| assignee: | nobody → Thierry Carrez (ttx) |
| importance: | Undecided → High |
| status: | New → In Progress |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in jakarta-log4j (Ubuntu): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
This bug was fixed in the package jakarta-log4j - 1.2.15-9ubuntu2
---------------
jakarta-log4j (1.2.15-9ubuntu2) lucid; urgency=low
* debian/control: Switch from libjboss-jmx-java (universe) to
libmx4j-java (main) to keep log4j in main (LP: #522558)
-- Thierry Carrez <email address hidden> Tue, 16 Feb 2010 11:54:21 +0100