You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2008/08/16 19:49:44 UTC
[jira] Created: (LOGGING-124) Commons logging does not work in an
osgi environment
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.
[jira] Commented: (LOGGING-124) Commons logging does not work in an
osgi environment
Posted by "Joerg Schaible (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOGGING-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701396#action_12701396 ]
Joerg Schaible commented on LOGGING-124:
----------------------------------------
A lot of people writing about classloader issues with commons-logging actually do use or did use an older version at that time. There's a reason why 1.1.1 is around.
> 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.
[jira] Commented: (LOGGING-124) Commons logging does not work in an
osgi environment
Posted by "Jochen Wiedmann (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (LOGGING-124) Commons logging does not work in an
osgi environment
Posted by "Niall Pemberton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOGGING-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623160#action_12623160 ]
Niall Pemberton commented on LOGGING-124:
-----------------------------------------
See the Note on the Commons OSGi wiki page re commons logging:
http://wiki.apache.org/commons/CommonsOsgi
> 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.
[jira] Updated: (LOGGING-124) Commons logging does not work in an
osgi environment
Posted by "Simon Kitching (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOGGING-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Kitching updated LOGGING-124:
-----------------------------------
Priority: Major (was: Critical)
Issue Type: Improvement (was: Bug)
> 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.
[jira] Commented: (LOGGING-124) Commons logging does not work in an
osgi environment
Posted by "Stevo Slavic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOGGING-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707316#action_12707316 ]
Stevo Slavic commented on LOGGING-124:
--------------------------------------
Doesn't SpringSource already have OSGi ready version of commons-logging in their enterprise bundle repository (See [1]) ?
Wouldn't just adding OSGi related metadata (e.g. by using existing ones from SpringSource release) to MANIFEST.MF be enough?
[1]
http://www.springsource.com/repository/app/bundle/version/detail?name=com.springsource.org.apache.commons.logging&version=1.1.1&searchType=bundlesByName&searchQuery=logging
> 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.
[jira] Commented: (LOGGING-124) Commons logging does not work in an
osgi environment
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (LOGGING-124) Commons logging does not work in an
osgi environment
Posted by "Zach Calvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOGGING-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925160#action_12925160 ]
Zach Calvert commented on LOGGING-124:
--------------------------------------
The commons http client uses logging 1.1.1. Now there is no way for me to make use of it on my OSGI stack. Here is the direct path that I'm now roadblocked at. I add httpclient to my list of OSGI dependencies:
<dependency>
<groupId>org.apache.httpcomponents</groupId>
<artifactId>httpclient-osgi</artifactId>
<version>4.0.1</version>
</dependency>
I try to interact with httpcomponents on my equinox osgi stack and discover the manifest to httpclient looks like:
Import-Package: javax.crypto,javax.crypto.spec,javax.net.ssl,javax.sec
urity.auth.x500,org.apache.commons.logging;version="1.1.1",org.apache
...
Since there is a direct dependency to 1.1.1 of commons logging, which no longer supports OSGI, I'm now torn with either regressing to the old httpclient 3.0.1 or trying to wrap up the commons logging myself.
Yuck.
> 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.
[jira] Commented: (LOGGING-124) Commons logging does not work in an
osgi environment
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOGGING-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623172#action_12623172 ]
Christian Schneider commented on LOGGING-124:
---------------------------------------------
I have read some more about the different logging engines. As it seems people agree that commons-logging has many class loading issues. What is the opinion of the people here on the project? Should people switch to slf4j and use the commons-logging compatibility or is it better to solve the classloading issues in commons-logging?
> 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.