You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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-Name entry in MANIFEST.MF
Then, move all of the files around so that I can write a module-info.java file with the appropriate exports/imports
The text was updated successfully, but these errors were encountered:
I've set Automatic-Module-Name to be nz.net.ultraq.thymeleaf.layoutdialect, and that's as far as I've managed to get. There are a bunch of issues still floating around w/ Gradle subprojects, Java modules, Groovy, and even IntelliJ IDEA that makes working and testing a full Java module build annoyingly difficult 😕
The most I've managed is to get a simple Java 11 project (I tried converting the benchmark subproject from Groovy -> Java) running with a module-info.java file that included the addition above, running it all via the CLI.
So this issue will stay open beyond the 3.0.0 release since going full module just isn't possible right now with my setup. Not sure what else I should be trying? Maybe updating packages so that it can work better with how I understand Java modules should be.
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 arenz.net.ultraq.thymeleaf
. Where that falls flat is that I've used the package ofnz.net.ultraq.thymeleaf
to pretty much every other Thymeleaf-related project I've created. With JPMS, I can't assignnz.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?🤷♂️
Automatic-Module-Name
entry inMANIFEST.MF
module-info.java
file with the appropriate exports/importsThe text was updated successfully, but these errors were encountered: