Fail jar task on invalid 'Automatic-Module-Name' in MANIFEST

[sormuras]

The default/core jar task should fail when the generated archive contains an invalid 'Automatic-Module-Name' entry.

Similar to what the JDK jar tool yields, when running jar --describe-module --file JAR-FILE.

Unable to derive module descriptor for: xyz.jar
Automatic-Module-Name: no-dash: Invalid module name: 'no-dash' is not a Java identifier

See https://sormuras.github.io/blog/2018-11-16-invalid-automatic-module-names for details.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[sormuras]

https://github.com/sormuras/modules/tree/main/doc/suspicious#illegal-automatic-module-name-manifest-entries

Let me find out what build tools those projects use...

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[sormuras]

Still valid. (Erm, invalid. Invalid module names are still slipping through, afaict.)