using Apache Netbeans libraries in JPMS project includes version number
- 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
For instance I use sometimes org.openide.util or org.openide.util.lookup in a JPMS multi module project. Now I have to set my module information to require those jars. Since there is no automatic module name in the jar configured I have to use the automatic from jar file name generated name, which results in
```java
requires org.openide.util.lookup.RELEASE220;
```
The version number is included.
I would suggest including this automatic module name in the manifest file. However, I do not know hot to achieve this using the normal ANT build. Using maven this would be done using somelthing like
```xml
org.apache.maven.plugins
maven-jar-plugin
org.openide.util.lookup
```
### Language / Project Type / NetBeans Component
_No response_
### How to reproduce
Try to reference any external jar without 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
Inspect the Apache NetBeans Ant packaging configuration for the org.openide.util and org.openide.util.lookup JARs, starting with how their manifests are generated. Determine how to add stable Automatic-Module-Name entries without the RELEASE220 suffix, then build the affected libraries and verify that JPMS requires their unsuffixed names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100