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/04/14 01:32:14 UTC
[jira] [Commented] (LOG4J2-515) Support OSGi bundles without
requiring OSGi dependencies.
[ https://issues.apache.org/jira/browse/LOG4J2-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967983#comment-13967983 ]
Matt Sicker commented on LOG4J2-515:
------------------------------------
Making a parallel repo with svn:external to the various subdirectories might be a good way to implement a lot of this.
> 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
> Labels: bundle, osgi
>
> 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.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org