JavaHamcrest icon indicating copy to clipboard operation
JavaHamcrest copied to clipboard

Java Modules v2.x

Open nhojpatrick opened this issue 7 years ago • 3 comments

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.

nhojpatrick avatar May 26 '18 22:05 nhojpatrick

Do you have any concrete ideas?

sf105 avatar Jun 01 '18 16:06 sf105

  • 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

nhojpatrick avatar Jun 02 '18 19:06 nhojpatrick

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.

nhojpatrick avatar Jun 03 '18 09:06 nhojpatrick