commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOGGING-124) Commons logging does not work in an osgi environment
Date Sat, 23 Feb 2013 14:44:13 GMT

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

Christian Schneider commented on LOGGING-124:
---------------------------------------------

About the symbolic name. I was just setting it so you can see how to do it. It may be a good
idea to leave it on the default value which I think is groupId.artifactId.
Packaging bundle allows the bundle plugin to tap into more lifecycle phases. I am not sure
if it is absolutely necessary but it is the recommended way to run the bundle plugin.

With the several packagings we may have some problems if a package is exported by e.g api
and full. So the better way would be to have API and impl jars that have no common packages.
In OSGi a package of a certain version can only come from one bundle. Of course it is not
a good idea to change the packaging in a bugfix release but perhaps this could be considered
for the next minor or majpr release.
                
> 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

Mime
View raw message