As part of rearranging the code, I'd like to propose we have module
"jena-base"
It would be non-RDF related code, seeded with what is currently
org.apache.jena.atlas which is in jena-arq and is then used by TDB and
SDB and others. RIOT uses it so it is a prequiste for moving RIOT.
Depends on:
jena-shaded-guava
Is depended on by:
jena-core
which can then use the cache code, based on guava via oaj.atlas.
Now we have java8, it is quite possible that stuff in oaj.atlas can be
slimmed down and also oaj.atlas renamed.
"jena-commons" is also a possible name but in trying this out, I found
some code using configuration settings, based on Context. A JVM wide
Context would be useful. So its role is not just library code but also
some small amount of state.
And JenaException
While in theory, it should be simple to migrate code, there are some
dependencies out of atlas that have sneaked in.
I would start by moving a package at a time, clean ones first. This can
happen incrementally.
Andy
