id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
16868	Move svgSalamander out of JOSM	michael2402	Don-vip	"The current problem with this is that we often apply our own fixes / quickfixes and that svgSalamander does not provide a maintained maven repository.

After setting up our git server:

* Clone the main svgSalamander repository
* Apply our patches (if we need to, currently they are in sync)
* Create a branch for our changes (for easier tracking them)
* Add a small gradle build script on our that includes the maven publish task
* Set up our CI to run the publish to our maven server on every commit to that branch.

* Change JOSM to use the maven dependency (using ivy for now)

Afterwards, syncing with upstream svgSalamander is easier."	enhancement	closed	normal	21.07	Core		fixed	hack-weekend-2018-10 maven ivy dependency svg svgsalamander	DevCharly simon04