id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
9654	[patch] [build fix] classes that use JMapViewer shoudn't use OsmMercator directly	glebius	team	"Hi!

Fixing #7017 requires that all classes using JMapViewer stop trusting OsmMercator as projection solver. Only tilesources, that know that they are using OsmMercator projection, should use OsmMercator. All upper layers should ask the tilesource for (x,y) ?= (lon, lat) calculations.

I already made this change in the JMapViewer itself. Unfortunately, hiding OsmMercator required its API change as well, so right now JOSM isn't buildable.

The attached patch makes JOSM to use tileSource instead of direct use of OsmMercator, and apparently fixes build as well."	defect	closed	blocker	14.02	Core		fixed