Unglue: ask the user about tags/membership

[skyper]

Right now you can easily break relations with unglueing.

I am not sure if another warning is the best solution but at least in "normal" mode some hint would be nice.

[simon04]

Should there be a warning when the node or one way is part of a relation, or both?

[skyper]

Replying to simon04:

Should there be a warning when the node or one way is part of a relation, or both?

Mmh, difficult.

I would go for a warning if the node is part of and otherwise if two ways are part of.
Think there exist some code for turn-restrictions already.

My prior intension was to prevent breaking route-relations - well let me think about the nodes.

[simon04]

Ticket #11124 has been marked as a duplicate of this ticket.

[simon04]

In 9292/josm:

see #8838 - Unglue: ask the user about tags/membership

Let the user decide whether the tags/memberships of the existing node should afterwards be at
the existing node, the new nodes, or all of them.

[Don-vip]

Replying to simon04:

In 9292/josm:

see #8838 - Unglue: ask the user about tags/membership

Let the user decide whether the tags/memberships of the existing node should afterwards be at
the existing node, the new nodes, or all of them.

There's an undocumented parameter:
jenkins/job/JOSM/lastCompletedBuild/jdk=JDK8/warnings4Result

Sorry, Jenkins is now a vicious steward who doesn't miss a thing :)

[simon04]

In 9315/josm:

see #8838 - Javadoc

[Don-vip]

is it fixed?

[simon04]

I fixed an aspect which was not requested.

This one is open – Replying to skyper:

My prior intension was to prevent breaking route-relations - well let me think about the nodes.

[simon04]

I'll copy the original indent to a separate ticket → #12304.

Then this is fixed ;)

[Don-vip]

great :) OK for new tested release then?

[simon04]

Alright – no objections from my side :)