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 "Matt Sicker (JIRA)" <ji...@apache.org> on 2014/01/27 00:46:37 UTC

[jira] [Created] (LOG4J2-515) Support OSGi bundles without requiring OSGi dependencies.

Matt Sicker created LOG4J2-515:
----------------------------------

             Summary: Support OSGi bundles without requiring OSGi dependencies.
                 Key: LOG4J2-515
                 URL: https://issues.apache.org/jira/browse/LOG4J2-515
             Project: Log4j 2
          Issue Type: Epic
          Components: API, Appenders, Configurators, Core, Filters, Layouts, Receivers
    Affects Versions: 2.0-rc1
         Environment: OSGi, non-OSGi
            Reporter: Matt Sicker


In order to properly support OSGi, we need to use a combination of ideas.

# Packages and modules should be as coherent as possible. This makes bundling them into bundles and services significantly easier. Plus, it's a good idea anyway.
# Use [Felix SCR annotations|http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html] in order to support more advanced OSGi concepts without requiring an explicit dependency on OSGi. This way, the annotations can be discarded or ignored by non-OSGi environments.
# Provide more bundles. The core bundles, while a good start, could be further modularized.
# Don't rely on class loader hacks. Instead, methods that need to use a class loader should always include a ClassLoader parameter. Class loader hacks can be used in centralized locations as a fallback mechanism where no advanced class loaders are provided.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org