New package: josm-19439
Testing the changes
- I tested the changes in this PR: YES
New package
- This new package conforms to the package requirements: YES
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.
Builded and installed, but when I launch it:
Using /usr/lib/jvm/openjdk17/bin/java to execute josm.
Error occurred during initialization of boot layer
java.lang.module.FindException: Module javafx.web not found
Launching it manually, without this debian scipt installed in /usr/bin/josm works properly
Could you try with the latest version I just pushed? It has a patch that strips out the Debian-specific stuff from /usr/bin/josm. That is the only change I made.
...which of course means we should just be using Void's canonical way of finding the correct jre, which is of course just using the java available on path, which is what you were saying in the first place. I'll update this to just do that when I get a chance instead of using the unnecessary included script.
now it works :)
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.
bump
bump
I've tested it, it works but, I'm getting message about using java version that soon will be deprecated josm has booted with 11, I have also 17 and 21 installed, but it's not using it by default Is there a way for josm to use newer java by default? Maybe some changes in the boot script?
Currently it uses whatever jdk is set by xbps-alternatives.
Using the xbps virtual?java-runtime is imperfect since we depend on at least 11, meaning it would break if the user tried to use openjdk8. But there is no way to specify a version guard with the virtual dependency. Probably the best solution is to hard depend on one version of java.
I pushed an updated version that depends directly on openjdk17-jre. Please test if you can.
I pushed an updated version that depends directly on
openjdk17-jre. Please test if you can.
This has been working fine for me in my testing.
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.