Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Fix Automatic-Module-Name

See original GitHub issue

https://github.com/thymeleaf/thymeleaf-spring/issues/179 broke the JPMS compatibility adding invalid characters in the Automatic-Module-Name.

Please change the “-” with “.” character.

Error:

Unable to derive module descriptor for: thymeleaf-spring5-3.0.10.RELEASE.jar
Automatic-Module-Name: thymeleaf-spring5: Invalid module name: 'thymeleaf-spring5' is not a Java

Issue Analytics

State:
Created 5 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

danielfernandezcommented, Oct 22, 2018

Already in 3.0.11-SNAPSHOT

0reactions

pangacommented, Oct 22, 2018

Awesome! Thank you!

Top Results From Across the Web

Automatic-Module-Name: Calling all Java Library Maintainers

This first step boils down to picking a module name, and adding it as Automatic-Module-Name: <module name> entry to the library's MANIFEST. MF. ......

Invalid Automatic-Module-Name s

TLDR: Run jar --describe-module --file ARTIFACT. jar to verify the selected module name adheres at least valid Java syntax before publishing.

Automatic module name containing number [duplicate]

1 Answer 1 ... The problem is that the module system does not identify 2_0 as a version number and hence doesn't strip...

Define JPMS automatic module name for all modules · Issue #47

The problem is that if a library doesn't declare an Automatic-Module-Name in the Jar MANIFEST the library falls into the unnamed module, and...

Automatic-Module-Name: Calling All Java Library Maintainers

This first step boils down to picking a module name and adding it as an Automatic-Module-Name: <module name> entry to the library's MANIFEST. ......