Support java modules for thrift

[jrhee17]

Motivation:

We received a report that thrift modules do not support java 9 modules.
When checking the specification, it seems like a identifier needs to start with a JavaLetter.
ref: https://docs.oracle.com/javase/specs/jls/se16/html/jls-7.html#jls-7.4

Unfortunately, our thrift modules contain a dot followed by a digit, which isn't a JavaLetter.
i.e. thrift0.9 where 9 isn't a digit.

I propose that for thrift modules, the last dot is omitted to avoid this issue.
i.e. thrift0.9 -> thrift09

Modifications:

• Introduced a automaticModuleNameOverride so that the override configuration can live inside each module
• automaticModuleName is now null if not configured, or a provider if configured. This change is necessary so that the actual value of automaticModuleName is not determined at configuration time, giving each module a chance to configure its own ext property.
• Each Jar task now configures Automatic-Module-Name at execution time as opposed to configuration time. This is also necessary so that each module can configure its own ext property prior to setting the name.
• Each thrift module now sets its own automaticModuleNameOverride

Result:

• Closes Invalid Automatic-Module-Name for armeria-thrift0.9 #6075

[github-actions]

🔍 Build Scan® (commit: 6b7fcad)

Job name	Status	Build Scan®
build-ubicloud-standard-16-jdk-8	✅	https://ge.armeria.dev/s/sgn72ezmv7om4
build-ubicloud-standard-16-jdk-21-snapshot-blockhound	✅	https://ge.armeria.dev/s/4jduqe2yunsfy
build-ubicloud-standard-16-jdk-17-min-java-17-coverage	✅	https://ge.armeria.dev/s/fpgv7nestarhq
build-ubicloud-standard-16-jdk-17-min-java-11	✅	https://ge.armeria.dev/s/trdveiqiv6w3g
build-ubicloud-standard-16-jdk-17-leak	✅	https://ge.armeria.dev/s/r6bd4wzrmp5tc
build-ubicloud-standard-16-jdk-11	✅	https://ge.armeria.dev/s/4pkpyhteh3r4u
build-macos-latest-jdk-21	✅	https://ge.armeria.dev/s/ezm6asglqgsag

[ikhoon]

When checking the specification, it seems like a identifier needs to start with a JavaLetter.
ref: docs.oracle.com/javase/specs/jls/se16/html/jls-7.html#jls-7.4

What do you think of normalizing Automatic-Module-Name by using _ instead of . if the first character of an artifactIdComponent starts with a number?
It seems that the generated names for Scala modules violate the specification.

Manifest-Version: 1.0
Automatic-Module-Name: com.linecorp.armeria.sangria_2.12

[jrhee17]

My initial thought was that we can't rewrite to support all of the rules defined by the jls. Having said this, assuming we won't be adding modules frequently I guess a simple rule is fine. Updated

[minwoox]

👍 👍 👍