My last comment on https://issues.apache.org/jira/browse/DERBY-6945
proposes how we could decompose Derby into Jigsaw-ready modules. Mostly,
these correspond to the existing release jars. However, one additional
module (and jar file) is proposed; it corresponds to the code currently
shared across several product jars.
The user experience of Derby would change slightly: In situations where
the user currently needs only one jar file, the user will need two jar
files in the future: the original jar file plus the jar file which
consolidates the previously cloned code.
Your advice and views would be appreciated.
Thanks,
-Rick
