[
https://issues.apache.org/jira/browse/JENA-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448851#comment-16448851
]
ASF GitHub Bot commented on JENA-1524:
--------------------------------------
Github user christopher-johnson commented on the issue:
https://github.com/apache/jena/pull/401
re: `org.apache.jena.atlas` dependents in `org.apache.jena.arq` (namely
`org.apache.jena.riot`)
I attach an excerpt from a `jdep`s output looking at `jena-arq-3.7.0.jar`,
sorted by package dependency.
The attached just includes the packages that depend on
`org.apache.jena.atlas` in `org.apache.jena.arq`
This is convenient to analyse interpackage relationships (that you probably
know of). It shows non-module deps as "not found", but indicates the package
name.
[arq-atlas-jdeps.txt](https://github.com/apache/jena/files/1939950/arq-atlas-jdeps.txt)
Perhaps this is useful. I guess the atlas question is a new issue?
> 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)
