Java Modules v2.x
Hamcrest future
Following on from #204 start thinking about how packages need to be refactored and what is simple or what would need to be done in a major version release.
Do you have any concrete ideas?
-
basically each jar needs a module name
-
map what jars depend upon what jars and add those requires
-
all classes that should be publicly available to users need to be exported
-
move all internal classes out of the publicly exposed packages
-
create test jar to execute hamcrest functionality
-
build on java 7 or 8
-
execute on java 9 just using modules path and not classpath and see what warnings appear
-
fix warnings or update dependencies declared
-
back to step 2 and repeat till no warnings
Will also need to check all dependencies being used, see if they have a java 9 version yet, or java automatic module name yet, maybe raise issues or pull request with down stream dependencies so they are aware hamcrest would like to support java 9 and see when they plan to.