Return-Path: X-Original-To: apmail-logging-log4j-dev-archive@www.apache.org Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5EE211116A for ; Sat, 20 Sep 2014 06:07:34 +0000 (UTC) Received: (qmail 61190 invoked by uid 500); 20 Sep 2014 06:07:34 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 61137 invoked by uid 500); 20 Sep 2014 06:07:34 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 61127 invoked by uid 99); 20 Sep 2014 06:07:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Sep 2014 06:07:34 +0000 Date: Sat, 20 Sep 2014 06:07:34 +0000 (UTC) From: "Remko Popma (JIRA)" To: log4j-dev@logging.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (LOG4J2-370) Log4j2 & OSGi How-To MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LOG4J2-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-370: ------------------------------- Fix Version/s: (was: 2.1) 2.2 > 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.2 > > > 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.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org