[
https://issues.apache.org/jira/browse/JENA-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439562#comment-16439562
]
ASF GitHub Bot commented on JENA-1524:
--------------------------------------
Github user christopher-johnson commented on the issue:
https://github.com/apache/jena/pull/399
See https://github.com/apache/jena/pull/401.
If I understood you correctly, the adapter
`jena-arq:org.apache.jena.system.JenaInit` just provides a short cut for using
the renamed ` jena-core:org.org.apache.jena.sys.JenaSystem` in the context of `
jena-arq` (for external implementations).
The `jena-arq `services that formerly used `
jena-core:org.org.apache.jena.system.JenaSystem` and will now use `
jena-core:org.apache.jena.sys.JenaSystem` will continue to do so and not change
their import to the ` jena-arq:org.apache.jena.system.JenaInit` adapter,
correct?
> 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)
