[
https://issues.apache.org/jira/browse/LOGGING-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Neidhart resolved LOGGING-124.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.1.2
Finally applied your patch wrt symbolicName to match the current maven
groupId/artifactId in r1452934.
Closing this now for the 1.1.x branch. If there will ever be a 1.2 or 2.0
version of commons-logging, proper OSGi support has to be taken into account
from the beginning.
> 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
> Fix For: 1.1.2
>
> 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
