directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hrvoje Habjanic (JIRA)" <>
Subject [jira] [Commented] (DIRAPI-201) Incossistent Import-Package in
Date Thu, 31 Jul 2014 08:59:38 GMT


Hrvoje Habjanic commented on DIRAPI-201:

Eh ... Actually Eclipse release name is LUNA ... not LUNO ... Sorry about that.


> Incossistent Import-Package in
> ------------------------------------------------------------------
>                 Key: DIRAPI-201
>                 URL:
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M19
>         Environment: Eclipse LUNA, standard install of LDAP Browser via update site.
>            Reporter: Hrvoje Habjanic
>            Priority: Critical
>              Labels: LUNO, collections, eclipse, import, package
> Hi.
> It seems that packages in jars import org.apache.commons.collections with
restriction version >= 3.2.1. But, in jar there is
restriction for org.apache.commons.collections with version >= 3.2.0 < 4.0.0.
> In most cases, where you have only one version of org.apache.commons.collections, this
will work fine. But, in my situation i have 3.2.0 installed, as 3.2.1.
> And Eclipse equinox have a problem with this, because it detects that not all requirements
for* can be resolved in the consistent way, and it prevents loading
of those classes. This results in LDAP browser or schema not working, in Eclipse.
> Solution is quite easy - Import-Package directive in
jar needs to be changed to include only 3.2.1 or higher version of org.apache.commons.collection.
> Since this bug prevents from LDAP working in Eclipse LUNO, this should be a critical
> I did manually change jar, and can confirm that with
this change, LDAP stuff is woring in LUNO.
> Regards,
> H.

This message was sent by Atlassian JIRA

View raw message