[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wink-dev
Subject:    [jira] Resolved: (WINK-330) Change slf4j api import to a range to
From:       "Bryant Luk (JIRA)" <jira () apache ! org>
Date:       2011-01-10 21:21:46
Message-ID: 10521653.264871294694506178.JavaMail.jira () thor
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/WINK-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Bryant Luk resolved WINK-330.
-----------------------------

    Resolution: Fixed
      Assignee: Bryant Luk

Looks good.  I applied the patch and made the commit.  If you see any other issues, \
let us know.  Thanks!

> Change slf4j api import to a range to make it more user friendly.
> -----------------------------------------------------------------
> 
> Key: WINK-330
> URL: https://issues.apache.org/jira/browse/WINK-330
> Project: Wink
> Issue Type: Improvement
> Components: Build
> Affects Versions: 1.1.2
> Reporter: Shawn Jiang
> Assignee: Bryant Luk
> Attachments: 0001-WINK-330-Change-slf4j-api-import-to-a-range-to-make-.patch
> 
> 
> Current slf4j import in wink bundles was binded to1.6.1 because of \
> maven-bundle-plugin genereate the manefest file based on maven dependency.  This in \
> turn will force any wink user in OSGi environment upgrade their slf4j to 1.6.1.     \
> This is not easy in some cases.   As you know,  many OSGi users(including geronimo) \
> are using PAX-logging as log bridge to OSGi log service.  The slf4j export version \
> in PAX-logging is 1.5.3. If wink could change the slf4j import to  a range with a \
> lower starting version.   It would be more OSGi user friendly.   Following is an \
> example with wink-common module.  Please review it. If you agree, I will open a \
> JIRA and attach a complete patch for it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[prev in list] [next in list] [prev in thread] [next in thread]