[
https://issues.apache.org/jira/browse/JENA-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449845#comment-16449845
]
ASF GitHub Bot commented on JENA-1524:
--------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/401
> Compilation in JPMS requires a module-info.java and is distinct from
compiling in JDK 9+.
The issue is for trellisldp to solve surely? The transitivity is an
indirect jena-osgi dependency and a direct jena dependency.
Or a PR to improve `jena-osgi` (which does not get much use or at least not
much user@ questions). You may also wish to take that up with CommonsRDF. I'm
not sure OSGi is helping here.
`jena-osgi` does not affect the oaj.atlas issue between `jena-arq` and
`jena-base`.
This PR is for the org.system split package. This seems completed. I'd like
to get this merged and other matters taken up in separate issues/JIRA so we can
make incremental progress.
> org.apache.jena.system is split by org.apache.jena.arq and
> org.apache.jena.core
> -------------------------------------------------------------------------------
>
> Key: JENA-1524
> URL: https://issues.apache.org/jira/browse/JENA-1524
> Project: Apache Jena
> Issue Type: Bug
> Components: Jena
> Affects Versions: Jena 3.7.0
> Reporter: Christopher Johnson
> Priority: Major
>
> a JPMS module cannot require both org.apache.jena.arq and
> org.apache.jena.core since org.apache.jena.system can be read from both.
> This cannot be resolved with --patch-module since arq and core provide
> different implementations. Suggestion is to make a distinction by renaming
> system to sys in either one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
