[
https://issues.apache.org/jira/browse/LUCENE-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044591#comment-13044591
]
Gunnar Wagenknecht commented on LUCENE-3172:
--------------------------------------------
FYI, I usually also create an "umbrella" bundle which has a Require-Bundle
dependency on all the Lucene bundles with such split-package headers. It does
not contain any class files but just re-exports the "merged" packages without a
split-package header. This allows client bundles to do a vanilla
Import-Package. Otherwise, any downstream client will be forced to add the
special split-package info to their Import-Package declaration.
> installation problems on lucene-misc OSGI bundle
> ------------------------------------------------
>
> Key: LUCENE-3172
> URL: https://issues.apache.org/jira/browse/LUCENE-3172
> Project: Lucene - Java
> Issue Type: Bug
> Environment: felix 3.2.2
> Reporter: Luca Stancapiano
> Assignee: Steven Rowe
> Fix For: 3.3, 4.0
>
> Attachments: lucene_trunk.patch
>
>
> lucene-misc contrib module has two package names equals to the core version:
> org.apache.lucene.index and org.apache.lucene.store. For theese modules we
> need to configure the creation of the bundles so that the OSGI repository
> recognize theese packages as merged else we get a 'uses constraint violation'
> error in the installation.
> The solution is to mark the packages as mergeables adding a configuration in
> the maven-bunde-plugin:
> <configuration>
> <instructions>
> <Export-Package>*;-split-package:=merge-first</Export-Package>
> </instructions>
> </configuration>
> the * represents the package names. We could put org.apache.lucene.* too
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
