[jbosstools-issues] [JBoss JIRA] (JBDS-4162) unresolved bundles - slf4j

Nick Boldt (JIRA) issues at jboss.org
Thu Nov 17 17:08:00 EST 2016


     [ https://issues.jboss.org/browse/JBDS-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt resolved JBDS-4162.
------------------------------
    Resolution: Done


I've put slf4j 1.7.2 back into the install so that it need not be installed whenever an unrelated thing gets installed/updated into the rpm install via an update site.

https://github.com/jbdevstudio/jbdevstudio-product/commit/a30844e56cd68128923f0565b9f9a864378666c1

Resolving.

> unresolved bundles - slf4j 
> ---------------------------
>
>                 Key: JBDS-4162
>                 URL: https://issues.jboss.org/browse/JBDS-4162
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Bug
>          Components: rhscl, rpm, target-platform
>            Reporter: Václav Kadlčík
>            Assignee: Nick Boldt
>             Fix For: 10.2.0.GA
>
>         Attachments: who-uses_ch.qos.logback.slf4j_1.0.7.png, who-uses_slf4j.impl.log4j12_1.7.2.png
>
>
> Vaclav said:
> {quote}
> Just an update on unresolved bundles. I looked at rh-eclipse46-devstudio-10.2-0.20161103.0650.el7.x86_64.rpm and the only ones are:
> ch.qos.logback.slf4j
> org.slf4j.impl.log4j12{quote}
> Both of those bundles declare
> {code}Fragment-Host: org.slf4j.api;bundle-version="[1.7.2,1.7.3)"{code}
> And since we're now using slf4j.api_1.7.4.jar, which has in its MANIFEST.MF:
> {code}
> Export-Package: org.slf4j;version=1.7.4, org.slf4j.spi;version=1.7.4, 
>  org.slf4j.helpers;version=1.7.4
> Import-Package: org.slf4j.impl;version=1.6.0;resolution:=optional
> Bundle-SymbolicName: slf4j.api
> {code}
> I suspect we need to find newer versions of those that can use slf4j 1.7.4 instead of 1.7.2.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)



More information about the jbosstools-issues mailing list