id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
6439	Starting older JOSM on newer config files generally results in a crash	anonymous	team	"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)
"	defect	closed	normal		Core		duplicate	template_report