Thank you! And yeah - I'll send a separate email opining on the directions that can go.
The features that should be incorporated/designed for (value classes/string templates/pattern matching) are more clearly in view than they were three years ago when last it was brought up and certainly more real than in 2014 when the JEP was made - so I don't think this isn't a horrible time to start some movement. On Wed, Dec 14, 2022 at 3:14 AM Alan Bateman <alan.bate...@oracle.com> wrote: > On 14/12/2022 03:36, Ethan McCue wrote: > > Hey all, > > > > I'm doodling on JEP-198, and I was wondering if anyone had a line on > > the boilerplate needed to add a new module to the build. > > > > Just adding > > > > src/ > > java.json/ > > share/ > > classes/ > > module-info.java > > java/ > > json/ > > Json.java > > ... > > > > was enough to get it to show up under the output when I run "make > > images", but I can't shake the feeling that I'm missing something. > > Modules with java.* classes must be mapped to the boot or platform class > loader. That mapping is defined in make/conf/module-loader-map.conf. > > java.se is the aggregator module for the APIs for ava SE platform. > You'll see it has a `requires transitive` for each of the standard modules. > > That should be enough to get your doodle going. As per previous mails, > it's very likely that JEP-198 will be withdrawn or replaced with a new > JEP, when the time comes. > > -Alan. >
