Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <187543321.1240380467556.JavaMail.jira@brutus>
Date: Tue, 21 Apr 2009 23:07:47 -0700 (PDT)
From: "Jochen Wiedmann (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Commented: (LOGGING-124) Commons logging does not work in an
 osgi environment
In-Reply-To: <1819526919.1218908984497.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LOGGING-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701397#action_12701397 ] 

Jochen Wiedmann commented on LOGGING-124:
-----------------------------------------

If Niall's comment above applies, then there is indeed a problem: As OSGI is more and more important, we should clearly reconsider the commons-logging intialization. If it cannot be made OSGI compliant now, then that needs to be changed.


> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.