Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-238

OSGi dependency failures in core

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Abandoned
    • Affects Version/s: 2.0-beta5
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
    • Environment:

      OSGi (Eclipse 4.2.2, but I think the issue is generic OSGi)

      Description

      To get the core module to load, in addition to re-fixing what was almost fixed in LOG4J2-159 I had to make several packages optional.

      • com.lmax.disruptor
      • com.lmax.disruptor.dsl
      • com.lmax.disruptor.util

      These provided a dependency on sun.misc, which I could hack around to make available but isn't normally available in OSGi and thus not a dependency I can easily put into a product. I believe the dependency is on sun.misc.Unsafe I'd like to use it...

      There is also a direct dependency somewhere on

      • sun.misc (also Unsafe)
      • com.sun.tools.jconsole – I think this unlikely to be used in an OSGi environment, so optional is appropriate.
      • org.codehaus.jackson
      • org.codehaus.jackson.map

      These would be easy enough to satisfy, but since most people won't need JSON logging, the dependency should be optional.

      I think the correct minimal fix is just to make them all optional in the manifest. Eliminating the need for sun.misc would be a good further step

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              rwk Bob Kerns
            • Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: