-
Notifications
You must be signed in to change notification settings - Fork 109
Description
With Java 9 and now 10 out, it's time to think of a module name for this project, and everything else I have. Stephen Colebourne has some good opinions on things in his blog (eg: http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html) so I might take some inspiration from there.
So far I've relied on Maven to take care of all of this for me, eg: the artifactId of this project is thymeleaf-layout-dialect, and the packages within are nz.net.ultraq.thymeleaf. Where that falls flat is that I've used the package of nz.net.ultraq.thymeleaf to pretty much every other Thymeleaf-related project I've created. With JPMS, I can't assign nz.net.ultraq.thymeleaf to one project because it then means I can't use it in another.
So maybe something like nz.net.ultraq.thymeleaf.layoutdialect? (You can't use dashes in module names unfortunately 😭 ) And then I move the source code to follow to a similarly-named package structure so I can have nicer exports declarations? And then I have to do the same to every other Thymeleaf-related project under my name?
🤷♂️
- First step: come up with a name and slap that into the
Automatic-Module-Nameentry inMANIFEST.MF - Then, move all of the files around so that I can write a
module-info.javafile with the appropriate exports/imports