-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the Lucene jar an OSGi bundle [LUCENE-7522] #8573
Comments
Dawid Weiss (@dweiss) (migrated from JIRA) If you search the mailing list I think the last consensus was that we simple are not enough of OSGi experts to maintain the metadata in a reasonable way, so instead the plan was to release plain JARs and leave OSGi (and any other packaging) for downstream maintainers. |
Uwe Schindler (@uschindler) (migrated from JIRA) In addition the current structure of packages inside those JARS is incompatible with OSGI (duplicate package names). This will be an issue with the module system of Java 9, but we are focusing on that instead of OSGI. |
Uwe Schindler (@uschindler) (migrated from JIRA) #2421 was closed in the wrong way. I reopened and fixed the status to "Won't fix". This was an issue of bulk-closing issues. |
Michal Hlavac (@hlavki) (migrated from JIRA) Ok, thanks for clarification. It will be good to think also about OSGi when you will be working on jigsaw issues. Maybe I can help with something. Is there any jira issue about jigsaw problems? |
Dawid Weiss (@dweiss) (migrated from JIRA) From the latest discussion on the mailing list I don't think even the jigsaw folks know how modules fit together with the OSGi classloader isolation model. |
Alexander Kurtakov (migrated from JIRA) Is there hope for this one? |
Add support for OSGi. #2421 added this feature to previous versions, but now lucene jars are not OSGi bundles. There are OSGi bundles from Servicemix, but I think lucene should add this feature.
Migrated from LUCENE-7522 by Michal Hlavac (@hlavki), updated Apr 05 2022
Linked issues:
The text was updated successfully, but these errors were encountered: