[JAVA-5213] Invalid automatic module name for mongo-scala-bson and mongo-scala-driver Created: 20/Oct/23 Updated: 10/Jan/24 Resolved: 27/Oct/23 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 4.11.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Fernando Correia | Assignee: | Slav Babanin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Documentation Changes: | Not Needed |
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
| Description |
Summarymongo-scala-bson and mongo-scala-driver have invalid characters in the "Automatic-Module-Name" field of their META-INF/MANIFEST.MF files. This causes some builds to fail with the error "cannot determine module name" . This happens on a Bazel project using JDK 17. This is present in the latest version of these two libraries, i.e. version 4.11.0. How to Reproduce
Additional BackgroundThe character "-" is not valid. For a description of the valid characters see:
_Similar issue: https://jira.mongodb.org/browse/JAVA-5202_ Suggested fix: replace "-" with a dot: ".". |
| Comments |
| Comment by Slav Babanin [ 27/Oct/23 ] |
|
Thank you fernandoacorreia@gmail.com for reporting this issue. The fix will be included in the 4.11.1 patch release. |
| Comment by Githook User [ 26/Oct/23 ] |
|
Author: {'name': 'Viacheslav Babanin', 'email': 'frest0512@gmail.com', 'username': 'vbabanin'}Message: Add explicit automatic module name configuration. (#1232)
|
| Comment by Fernando Correia [ 23/Oct/23 ] |
|
I found an additional reference about what valid module names are: > A module name consists of one or more Java identifiers (§3.8) separated by "." tokens. https://docs.oracle.com/javase/specs/jls/se17/html/jls-7.html#jls-7.7
|
| Comment by PM Bot [ 20/Oct/23 ] |
|
Hi fernandoacorreia@gmail.com, thank you for reporting this issue! The team will look into it and get back to you soon. |