[
https://issues.apache.org/jira/browse/JENA-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448352#comment-16448352
]
ASF GitHub Bot commented on JENA-1524:
--------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/401
I don't see a split package in `org.apache.jena.atlas` - it has classes and
sub-packages in `jena-base` and separate sub-packages in `jena-arq` but I don't
see a package being split. That should not be a problem, should it?
Given this is retrofitting, we have to balance change with continuity for
existing users. Calling it `org.apache.jena.base` follows the general
automatic module style. "base" is code that is RDF-independent and is more for
internal Jena use.
> 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)
