[
https://issues.apache.org/jira/browse/LOG4J2-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-370:
-------------------------------
Affects Version/s: 2.0-rc1
Fix Version/s: 2.0
> Log4j2 & OSGi How-To
> --------------------
>
> Key: LOG4J2-370
> URL: https://issues.apache.org/jira/browse/LOG4J2-370
> Project: Log4j 2
> Issue Type: Documentation
> Components: API, Core, JCL Bridge, log4j 1.2 emulation, SLF4J Bridge
> Affects Versions: 2.0-beta9, 2.0-rc1
> Environment: OSGi R5 (e.g. Apache Felix)
> Reporter: Roland Weiglhofer
> Priority: Minor
> Fix For: 2.0
>
>
> The Log4j2-manual should provide a Quick-Start for OSGi-developers.
> Very important: It is not enough that the core library is located in the same
> folder as the api. If log4j2 is used in an OSGi-environment, you have to
> specify the dependencies on the core and on the api in your POM, otherwise
> the libraries are not added to the bundle-ClassLoader. This leads to the
> error: 'StatusLogger Unable to locate a logging implementation, using
> SimpleLogger.'
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
