[
https://issues.apache.org/jira/browse/JENA-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17580204#comment-17580204
]
Andy Seaborne commented on JENA-2343:
-------------------------------------
The next release is in-progress and it's too late for this. Jena release on a
clock tick every three or four months - conditional on finding time to do a
release because everyone is volunteering their own time.
It seems to place a requirement on every java package having a
{{package-info.java}}. It affects contributions.
Can this be automated?
Can the maven enforcer plugin check that the presence of these files?
I'm hoping to see trial use of this by other parties. This is something that
has a long-term implication of support so I feel it needs validation as the
right approach. Are there alternative approaches?
Other parties involvement also shows there will be some level of long-term
sustainability; the usual software engineering concerns: tool-chains change,
new requirements come along, security reports need addressing etc. This was the
main factor for the previous OSGi bundle.
We _might_ be able to add something as a _reversible_ change into development
so snapshots start getting the changes and then downstream can test it out
rather than have to do a local build.
> 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]
