I thought turning the gradle-module-plugin into a JPMS module was the most advanced project mrJar was applied in. Well it was, up until I ported a three-module JAX-RS/DropWizard RESTFul AuthN API to its SpringBoot equivalent with mrJar tying it all together.
All three of those projects were excellent functional tests for mrJar v0.0.12, v0.0.13 and v0.0.15. Getting mrJar to work in them meant the plugin had to up its game for each one. Which improved the overall functionality of the plugin amazingly.
That same usage-driven development process also paid off handsomely with this most recent super productive functional testing iteration informed by @Graou74’s 3D modelling application.
I stumbled across mrJar’s latest most advanced functional test case so far in this Stackoverflow question. @Emily describes the problem she’s seeking a solution to, as: „migration of a large code base from Java 8 to modular (JPMS) Java 11“.
mrJar handled the JPMS migration of such „a large code base“ with such relative ease that even I was surprised at how little time and effort it took!
Not so surprising though is that, just like the other functional test projects, @Emily’s presented some technical requirements that would never have occurred to me if I’d never come across her Li Song Mech Lab project.
So, sincere thanks to all of those projects (@tlinkowski, @siordache, et al) for helping mrJar improve.