Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 34468E8AF for ; Sat, 23 Feb 2013 13:52:14 +0000 (UTC) Received: (qmail 78230 invoked by uid 500); 23 Feb 2013 13:52:13 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 78156 invoked by uid 500); 23 Feb 2013 13:52:13 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 78138 invoked by uid 99); 23 Feb 2013 13:52:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Feb 2013 13:52:13 +0000 Date: Sat, 23 Feb 2013 13:52:13 +0000 (UTC) From: "Thomas Neidhart (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (LOGGING-124) Commons logging does not work in an osgi environment 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/LOGGING-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585121#comment-13585121 ] Thomas Neidhart edited comment on LOGGING-124 at 2/23/13 1:51 PM: ------------------------------------------------------------------ Hi Christian, thanks for your patch: * change the Bundle-SymbolicName to commons-logging is ok * update the packaging to bundle: why? what benefit does it bring? Regarding your question: The different jar versions do include a different set of classes: * full: everything * api: only the Log interface + core classes + SimpleLog + NoLog * adapters: only the adapters to actual Log implementations, e.g. Log4JLogger now some of the things in the api also reside in the impl package which may look weird, but thats the way it was before and can not change for 1.1.2. Thomas was (Author: tn): Hi Christian, thanks for your patch: * change the Bundle-SymbolicName to commons-logging is ok * update the packaging to bundle: why? what benefit does it bring? Thomas > Commons logging does not work in an osgi environment > ---------------------------------------------------- > > Key: LOGGING-124 > URL: https://issues.apache.org/jira/browse/LOGGING-124 > Project: Commons Logging > Issue Type: Improvement > Affects Versions: 1.1.1 > Reporter: Christian Schneider > Attachments: LOGGING-124.patch > > > Commons logging should provide Manifest information for using it as an OSGI bundle. Eventually detection of logging engines and loading of configs should also be changed to make commons-logging osgi ready. > I have given this problem the critical priority as currently many people are working on osgi projects and as many open source libs use commons-logging this is an important thing to solve. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira