Java model does not properly account for module-info.java inside of Multi-Release jar files
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 935
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 17
Description
### Apache NetBeans version
Apache NetBeans 19
### What happened
If a project using the module system depends on a Maven artifact that contains a module-info.class file inside of a multi-release directory, the using project is not informed of its existence. I assume that the Java model created for the multi-release jar is not properly accounting for its multi-release nature.
### How to reproduce
I have attached a zip file that contains to Maven project: multirelease and app. Their names should be self-explanatory.
[multi-release-model-issue.zip](https://github.com/apache/netbeans/files/12795436/multi-release-model-issue.zip)
### Did this work correctly in an earlier version?
No / Don't know
### Operating System
MacOS 14
### JDK
OpenJDK 64-Bit Server VM Zulu21.28+85-CA (build 21+35, mixed mode, sharing)
### Apache NetBeans packaging
Apache NetBeans provided installer
### Anything else
The same issue is present on my Linux machine.
### Are you willing to submit a pull request?
Yes
Contributor guide
Research direction
Start by opening the attached multi-release-model-issue.zip and reproducing the problem with the multirelease and app Maven projects in NetBeans 19. Investigate how the Java model handles module-info.class in a multi-release directory; done means the using project is informed of the module descriptor in the dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100