[OSM-talk] Moving to Java 1.6 not so easy to swallow

[Claudius]

Am 25.03.2010 19:31, Aun Johnsen:
> For me it would be appreciated that JOSM
> was split into another branch, so that we can have JOSM j5 and JOSM j6
> side by side.

Actually that's exactly what the JOSM devs announced:
After the JOSM j5 stable version is finished the j6 development 
continues and if anyone cares he can do backports of all the 
developments. But none of the current JOSM developers wants to do it and 
most probably it will be impossible to backport some of the new features 
because they are only possible with j6 without rewriting most parts of 
the app.

Besides I think there's a lot of fuzz about this move: If you check the 
editor tags in the latest changelog you can see that roughly 50% are 
using JOSM 2055. That's a 7 month old version and was issued stable back 
then. Even without the updated relation support many users seem to be 
able to get along very well. I think that 3155 will be useful at least 
the same amount of time. And if you miss something in winter 2010 you 
can switch to merkaartor or Mapzen 2.0 or OSM2Go or iLoe or OpenMaps or ....

Claudius