Bug 1397483 - require-bundle directives in OSGi metadata are not strict enough
Summary: require-bundle directives in OSGi metadata are not strict enough
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: lucene
Version: rh-java-common
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Michael Simacek
QA Contact: Lukáš Zachar
URL:
Whiteboard:
Depends On: 1395709
Blocks: 1389302
TreeView+ depends on / blocked
 
Reported: 2016-11-22 15:55 UTC by Kiersten (Kerri) Anderson
Modified: 2016-12-05 09:29 UTC (History)
11 users (show)

Fixed In Version: rh-java-common-lucene-4.8.0-6.8.el6 rh-java-common-lucene-4.8.0-6.8.el7
Doc Type: Bug Fix
Doc Text:
Previously, the presence of both Lucene versions 4 and 5 in the same OSGi environment caused problems, for example, when using multiple Eclipse plug-ins that each depended on a different Lucene major version. Consequently, the given OSGi bundle (Eclipse plug-in) terminated unexpectedly due to bytecode verification errors. With this update, Lucene OSGi metadata has been changed to contain stricter version requirements. As a result, it is now possible to use multiple Eclipse plug-ins depending on different major versions of Lucene within a single OSGi runtime (Eclipse).
Clone Of: 1395709
Environment:
Last Closed: 2016-12-05 09:29:46 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2851 0 normal SHIPPED_LIVE rh-java-common bug fix update 2016-12-05 14:29:19 UTC

Comment 4 errata-xmlrpc 2016-12-05 09:29:46 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2851.html


Note You need to log in before you can comment on or make changes to this bug.