JOSM dev here, please note I read a machine-translated version of this thread, so there might be some misunderstandings on my end.
Covering the points one-by-one:
When I open JOSM, I do it with a *.bat file.
The bat file appears to be using WebStart (most likely Oracle WebStart). I would highly recommend using OpenWebStart instead of Oracle WebStart.
- Memory shortage to open “simple” Aerial Aerial News Ortho layer
It looks like you are setting the maximum memory manually in the batch file. Assuming you have 4GB of memory or more, this should not be necessary. Otherwise, I’d recommend upgrading, possibly to a Raspberry Pi (~70 USD, some assembly required). This would also come with some power savings.
If you do have 4GB of memory or more, I’d need to see the JOSM status report, just to verify what the actual memory usage is, what Java version is being run, and what instruction set the Java version was compiled for.
Best guess: the default java
application on your machine is a 32-bit installation, and, even though you have installed a newer java
version, you are still running JOSM with the older 32-bit java
version. Which is probably Java 8. Try uninstalling older Java versions, assuming you have no other Java applications besides JOSM.
- In the meantime (temporarily) the Windows version installed, I notice that my “remote control” (data download from browser to JOSM does not (anymore) work.
You might have had another copy of JOSM running when you started the windows version. Right now, JOSM remote control is greedy, in so far as it will not relinquish control to another instance of JOSM.
Java 8 is now obsolete, and many Java programs stop supporting them. - This is normal.
Some of our dependencies are starting to move away from Java 8, which means we will, at some point, be forced to move away from Java 8. Right now, it is just a suggestion – we still support Java 8, but we really want to have as few people as possible on it. Also, if we can move to Java 17, there are some things that we can do that may improve performance for everyone.
Soon we will be able to use all the new functionality that has been added in the intervening years in the knowledge that all users have at least Java 17.
We are probably going to be on Java 11 for a bit – the current Debian stable is not shipping with Java 17 as the default, unfortunately. This might change after Bookworm is released (Java 17 by default).
Regardless, we are probably going to update the JRE in the installers to the latest LTS release, and the links in the update prompts to the latest LTS release.
Unfortunately, because the clumsy build environment is a huge barrier to third-party contributions.
All you have to run to do a build is ant build
. It is a bit more complicated for IDE builds (you have to either run ant build
once or a specific subset, I’d just run ant build
once). We do have wiki pages for the bigger IDEs.