[
https://issues.apache.org/jira/browse/JENA-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584327#comment-17584327
]
Andy Seaborne edited comment on JENA-2343 at 8/24/22 3:50 PM:
--------------------------------------------------------------
What's the difference between the Felix and BND plugins (why does Felix have
its own?)
One possibility is to use {{{color:#24292f}bndfile{color}}}, or to generate
each MANIFEST.MF once using the tools.
That would meet your PR suggestion for self-organising OSGi users. They could
then over time be refined. It also means the control of OSGi metadata isn't in
the POM which would be more robust. A long config in CDATA is fragile with
respect to non-OSGI PRs.
What is the state of testing that OSGi-zed Jena works in some way in the
release build?
{quote}I just found that Jena seem to embedd several content from other module
{quote}
Could you expand on that?
was (Author: andy.seaborne):
>From its documentation, I don't see how the bnd-plugin can be used in the same
>way (i.e. just generate a MANIFEST). It says it generates other files as well-
>which it didn't when I tried so I didn't try that route.
The BND site refers to Felix.
One possibility is to generate each MANIFEST.MF once using the tools and then
put into git at src.main/resource/META-INF/. That would meet your PR
suggestion for self-organising OSGi users. They could then over time be
refined. It also means the control of OSGi metadata isn't in the POM which
would be more robust. A long config in CDATA is fragile with respect to
non-OSGI PRs.
What is the state of testing that OSGi-zed Jena works in some way in the
release build?
{quote}I just found that Jena seem to embedd several content from other module
{quote}
Could you expand on that?
> Bring back OSGi support to Jena
> -------------------------------
>
> Key: JENA-2343
> URL: https://issues.apache.org/jira/browse/JENA-2343
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Christoph Läubrich
> Priority: Major
>
> With JENA-2165 and the announcement on the mailing list
> [https://lists.apache.org/thread/20h0djofj3h3dwtm728mcclv2zply9jt] OSGi
> support was dropped from the project due to missing expertise.
> I'd like to bring back OSGi support, hopefully in a way that is easier to
> maintain and offer to help if questions arise later on.
> My plan would be the following:
> # Add OSGi header to the Jena artifacts, in contrast to the previous
> approach of generating a fat-jar, this could be done immediately and will not
> harm as it only *enables* the use inside OSGi but users of Jena are
> responsible to provide the missing glues their selfes.
> # I have [proposed a new framework running
> mode|https://github.com/osgi/osgi-test/issues/541] to the osgi-test project,
> that will finally make test-setups much more easier and will allow to run
> test from the current build and inside the usual Jena test-suite, so once
> this is merged I'd like to add tests and even missing pieces to improve OSGi
> user experience so less setup is required to actually use Jena inside OSGi
> I'll also forward this issue to some other people interested in Jean OSGi
> support to get more feedback and attention for this feature.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
