Published JARs for versions 2.2.0 and 2.3.0 have an invalid module name in MANIFEST.MF

[anderswisch]

Published JARs for versions 2.2.0 and 2.3.0 have an invalid module name in MANIFEST.MF.

Both contain this line:

Automatic-Module-Name: emailaddress-rfc2822

Because it contains a - character, it is not a valid identifier. Running jar --describe-module --file emailaddress-rfc2822-2.2.0.jar gives output:

Unable to derive module descriptor for: emailaddress-rfc2822-2.2.0.jar
Automatic-Module-Name: emailaddress-rfc2822: Invalid module name: 'emailaddress-rfc2822' is not a Java identifier

[anderswisch]

I think this comes from https://github.com/bbottema/standard-project-parent/blob/master/pom.xml#L60 (artifactId can contain dashes)

[anderswisch]

This problem also affects version 1.0.1 of https://github.com/bbottema/jetbrains-runtime-nullability-annotations

[bbottema]

Hmm, that's a problem. I'm not sure how to get the unique project name without dashes and I don't really have the time lately to do research. Any suggestions?

[anderswisch]

I put up a clumsy fix for this in bbottema/standard-project-parent#10. Let me know what you think. It's been awhile since I tried to do this kind of thing in Maven.

[bbottema]

Fixed by aea17f8

[bbottema]

Fix released in 2.3.1