[
https://issues.apache.org/jira/browse/LOGGING-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623171#action_12623171
]
Christian Schneider commented on LOGGING-124:
---------------------------------------------
Ok .. I read the thread on the mailing list. But this will not really help. The
last mail says : Please don´t support OSGI as it won´t work with
commons-logging anyway. Personally I think this is quite counter productive. We
have an urgent problem here. Many Open Source libraries use commons-logging and
when they move to osgi the users of these libraries have problems. I do not
think the answer can be: let all people switch to pax-logging (or yet another
logging framework). I think either commons-logging should make the move to osgi
or be discontinued. If things stay as they are people will only move away from
commons-logging over time and the problems will continue to exist over a long
time.
The minimal thing would be to explain in the commons-logging documentation what
people have to do to make their apps work. The better thing would be to provide
a commons-logging jar that simply works in osgi. I am sure the bootstrapping
and detection of frameworks can be changed in a way that is not as problematic
as today.
> 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: Bug
> Affects Versions: 1.1.1
> Reporter: Christian Schneider
> Priority: Critical
>
> 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.
