error hint for JPMS modules with Automatic-Module-Name manifest entry: module not found
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 935
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 17
Description
### Apache NetBeans version
Apache NetBeans 23
### What happened
I have jars with an Automatic-Module-Name entry in the manifest file. Using maven I can compile the stuff, but Netbeans shows an error hint within my module-info when I config the useage of this library:
```
require mylib;
```
### Language / Project Type / NetBeans Component
_No response_
### How to reproduce
Try to reference a third party jar with an Automatic-Module-Name.
### Did this work correctly in an earlier version?
No / Don't know
### Operating System
Windows 11
### JDK
17, 21
### Apache NetBeans packaging
Apache NetBeans provided installer
### Anything else
_No response_
### Are you willing to submit a pull request?
No
Contributor guide
Research direction
Reproduce the issue in NetBeans 23 with a third-party JAR whose manifest contains Automatic-Module-Name, then inspect the module-info reference and its module-not-found hint. Compare the IDE result with Maven compilation using JDK 17 or 21. Done means the valid automatic module is resolved without an erroneous hint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100