-
Bug
-
Resolution: Fixed
-
P2
-
jfx17
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8274164 | jfx17.0.1 | Johan Vos | P2 | Resolved | Fixed | |
JDK-8273833 | jfx17.0.0.1 | Johan Vos | P2 | Resolved | Fixed |
It turns out that with the current approach of publishing platform agnostic jars, empty jars need this entry[2]. A better alternative to empty jars is still been discussed. It will need both time and effort.
Until an alternative is finalized, it is best revert the change made in
[1] https://bugs.openjdk.java.net/browse/JDK-8264998
[2] https://mail.openjdk.java.net/pipermail/openjfx-dev/2021-September/031934.html
- backported by
-
JDK-8273833 Re-introduce Automatic-Module-Name in empty jars
- Resolved
-
JDK-8274164 Re-introduce Automatic-Module-Name in empty jars
- Resolved
- duplicates
-
JDK-8274103 javafx-base-17.jar and javafx-base-17-win.jar recognized as the same module
- Closed
-
JDK-8274254 Javafx no longer possible to use with moditect for non-modular projects
- Closed
- relates to
-
JDK-8264998 Empty Jars shouldn't have Automatic-Module-Name
- Resolved
- links to
-
Commit openjdk/jfx17u/9bd87081
-
Commit openjdk/jfx/3a677c41
-
Commit openjdk/jfx/7329279e
-
Review openjdk/jfx17u/11
-
Review openjdk/jfx/623
-
Review openjdk/jfx/625