Github user christopher-johnson commented on the issue:
https://github.com/apache/jena/pull/401
In working with the automatic modules, I have also found a split
with`org.apache.jena.atlas`. This is between `org.apache.jena.arq` and
`org.apache.jena.base`.
Would it make sense to create a separate project and artifact for
`org.apache.jena.atlas`?
I realize that this sort of package refactoring is a slippery slope.
However, the new module idiom was to enforce a semantic relationship between
the project structure, the artifact(s) it produces and the package(s) it
provides. I have found furthermore that it is consistent to name a project in
accordance with the qualified module name (without the top level group). So,
the traditional "-" naming semantic could be replaced in archives with a "."
---
