id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
2637	Unable to resolve conflict in relation	maba.gp@…	team	"Trying to upload, JOSM reported in a popup ""Version mismatch: Provided 88, server had: 89 of Relation 31562"".[[BR]]
(Side problem: JOSM should offer an on-the-spot possibility to solve this problem.)[[BR]]
As it doesn't, I had to locate this relation and make sure it was downloaded again.
So I had a conflict to solve, just as I wanted.[[BR]]
But when I clicked on any of the buttons to solve it, I got what's in the attached log file. Reproducibly, that is. With 1607 as well as 1590. 1567 doesn't throw the exception but still doesn't solve the conflict.[[BR]]
How am I supposed to solve this conflict in the relation???[[BR]]
I've now saved my changes to an .osm file, manipulated the version number and succeeded with the upload this way but that's certainly not the solution for this. Naturally, I also looked up the change done by the other mapper and repeated it."	defect	closed	critical		Core	latest	duplicate	IndexOutOfBoundsException, relation, conflict	Gubaer