Starting older JOSM on newer config files generally results in a crash

[anonymous]

I've been developing on JOSM, and occasionally accidentally start an older version. Usually it is a boom as here:

Debian-Release: 0.0.svn3751-2ubuntu1
Build-Date: 2011-04-16 16:13:34
Revision: 3751
Is-Local-Build: true

Identification: JOSM/1.5 (3751 en)
Memory Usage: 89 MB / 1328 MB (71 MB allocated, but free)
Java version: 1.6.0_24, Sun Microsystems Inc., Java HotSpot(TM) 64-Bit Server VM
Operating system: Linux

Plugin: utilsplugin2

java.lang.ArrayIndexOutOfBoundsException: 1

at org.openstreetmap.josm.io.MirroredInputStream.checkLocal(MirroredInputStream.java:179)
at org.openstreetmap.josm.io.MirroredInputStream.<init>(MirroredInputStream.java:63)
at org.openstreetmap.josm.io.MirroredInputStream.<init>(MirroredInputStream.java:35)
at org.openstreetmap.josm.data.imagery.ImageryLayerInfo.load(ImageryLayerInfo.java:42)
at org.openstreetmap.josm.gui.preferences.ImageryPreference.initialize(ImageryPreference.java:746)
at org.openstreetmap.josm.Main.<init>(Main.java:223)
at org.openstreetmap.josm.gui.MainApplication.<init>(MainApplication.java:64)
at org.openstreetmap.josm.gui.MainApplication.main(MainApplication.java:231)

[skyper]

I wonder how you can start an old josm version on accident.

1. You do not need the ubuntu package if you use tested, latest or own builds.
2. If you really need the ubuntu package, you could set an alias in your shell config file (for .bashrc):

   alias josm='/usr/local/bin/josm-latest'
   alias old_josm='/usr/bin/josm'
   

   ,for example. I copied the shell script /usr/bin/josm to josm-latest with some small changes but basicly you need:

   java -jar [path to file]/josm-latest
   

[skyper]

Closed as duplicate of #6216.