> On Apr 5, 2022, at 05:11, Aleksandar Kurtakov <akurt...@redhat.com> wrote: > I can only encourage everyone to open a ticket for such project and help > them to include OSGi meta-data in the first place instead of putting the > effort else-where, as adding those does not harm the project but helps > integration it with just a few extra lines in the manifest.4 > > One such project is Lucene. I never found the time to report against it so > far. Help is always more than welcome . > https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/issues/136 > > <https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/issues/136> I tried that in 2008. https://issues.apache.org/jira/browse/LUCENE-1344 <https://issues.apache.org/jira/browse/LUCENE-1344>. It failed and was rejected as won't fix. https://issues.apache.org/jira/browse/LUCENE-7522 <https://issues.apache.org/jira/browse/LUCENE-7522> seems to be another attempt.
Some projects aren't as receptive as you'd think. I that case it would still be nice to share the OSGi metadata with other Eclipse projects. -Gunnar -- Gunnar Wagenknecht gun...@wagenknecht.org, http://guw.io/
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
