Bug 849138

Summary:	mandatory=core attribute in Export-Package header makes bundle unresolvable in Eclipse
Product:	[Fedora] Fedora	Reporter:	Severin Gehwolf <sgehwolf>
Component:	lucene	Assignee:	Alexander Kurtakov <akurtako>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	akurtako, hicham.haouari, java-sig-commits, kdaniel
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-01 09:24:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Severin Gehwolf 2012-08-17 12:02:35 UTC

Description of problem:
Any eclipse plug-in requiring org.apache.lucene.* packages fail to resolve due to mandatory=core attribute in Export-Package OSGi header.

Note that this is only an issue on F17 (F18, rawhide have fixed manifests)

Version-Release number of selected component (if applicable):
$ rpm -q lucene
lucene-2.9.4-8.fc17.noarch

How reproducible:
Always.

Steps to Reproduce:
1. Create Eclipse plug-in with Import-Package: org.apache.lucene.index
2. Attempt to run application
3. Plug-in fails to resolve
  
Actual results:
Resolution errors.

Expected results:
imported lucene packages should resolve

Additional info:
Removing 'mandadory=core' from the metadata in the manifest fixes this.

Comment 1 Alexander Kurtakov 2013-03-01 09:05:53 UTC

Severin, is this fixed now? If not do you plan fixing it?

Comment 2 Alexander Kurtakov 2013-03-01 09:24:03 UTC

Closing as wontfix as there seem to not be no need for this and I would rather prefer not playing with F17 and cause other potential rebuilds. Also the problem doesn't exist on F18 so interested parties should move.