directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Horal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSTUDIO-1068) Bundles are not resolved on Eclipse Mars
Date Fri, 20 Nov 2015 11:11:10 GMT

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

Pavel Horal commented on DIRSTUDIO-1068:
----------------------------------------

How to make things work till a proper fix in place:

 * delete {{slf4j.api_1.7.10.jar}} and {{slf4j-log4j12-1.7.10.jar}} from {{eclipse/plugins}}
 * update slf4j dependency to *1.7.2* in the following files (under {{eclipse/plugins}}):
 ** {{org.apache.directory.api.asn1.ber_1.0.0.M30.jar}}
 ** {{org.apache.directory.api.ldap.extras.aci_1.0.0.M30.jar}}
 ** {{org.apache.directory.api.ldap.schema_1.0.0.M30.jar}}
 ** {{org.apache.mina.core_2.0.9.jar}}

Updating dependency means unzipping contents of the JAR, opening {{META-INF/MANIFEST.MF}},
updating version in {{Import-Package}} and repackaging the manifest back to the JAR.

> Bundles are not resolved on Eclipse Mars
> ----------------------------------------
>
>                 Key: DIRSTUDIO-1068
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1068
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-updatesite
>            Reporter: Robert Munteanu
>         Attachments: DIRSTUDIO-1068.patch, eclipse-mars-error.log
>
>
> I have an Eclipse Mars install and installed Directory Studio using the Eclipse Marketplace.
> After the installation is performed I have multiple error FrameworkEvents logged regarding
bundle installations. All of them bubble down to a uses constraint violation.
> {noformat} Bundle was not resolved because of a uses contraint violation.
>   org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to
resolve resource slf4j.api [osgi.identity; osgi.identity="slf4j.api"; type="osgi.bundle";
version:Version="1.7.10"] because it exports package 'org.slf4j.helpers' and is also exposed
to it from resource org.slf4j.api [osgi.identity; osgi.identity="org.slf4j.api"; type="osgi.bundle";
version:Version="1.7.2.v20121108-1250"] via the following dependency chain:
>   slf4j.api [osgi.identity; osgi.identity="slf4j.api"; type="osgi.bundle"; version:Version="1.7.10"]
>     import: (&(osgi.wiring.package=org.slf4j.impl)(version>=1.6.0))
>      |
>     export: osgi.wiring.package=org.slf4j.impl; uses:=null
>   org.slf4j.api [osgi.identity; osgi.identity="org.slf4j.api"; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"]
>     require: (&(osgi.wiring.bundle=ch.qos.logback.classic)(&(bundle-version>=1.0.7)(!(bundle-version>=1.0.8))))
>      |
>     provide: osgi.wiring.bundle; bundle-version:Version="1.0.7.v20121108-1250"; osgi.wiring.bundle="ch.qos.logback.classic"
>   ch.qos.logback.classic [osgi.identity; osgi.identity="ch.qos.logback.classic"; type="osgi.bundle";
version:Version="1.0.7.v20121108-1250"]
>     import: (&(osgi.wiring.package=org.slf4j.helpers)(version>=1.7.0))
>      |{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message