Purging new objects purges relations containing those objects

[ShadowFoxNixill]

What steps will reproduce the problem?

1. Download a relation that contains at least one way
2. Split the way (if the relation contains more than one way, you may split any single way)
3. Purge the newly created way (not the one that keeps the history of the way)

What is the expected result?

JOSM should treat the purging of the way as if it's a deletion - in that it confirms if you want to remove the object from the relation.

What happens instead?

JOSM purges the relation instead.

Please provide any additional information below. Attach a screenshot if possible.

This only happens if you purge *newly created* objects that are part of relations. Purging an existing, but modified, object does not cause a relation purge.

It also happens if the new object that is purged is a node or is itself a relation (including relations that were purged by the purging of newly created objects).

URL:http://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2017-08-26 02:54:56 +0200 (Sat, 26 Aug 2017)
Build-Date:2017-08-26 01:33:58
Revision:12664
Relative:URL: ^/trunk

Identification: JOSM/1.5 (12664 en) Windows 10 64-Bit
OS Build number: Windows 10 Education 1703 (15063)
Memory Usage: 247 MB / 247 MB (43 MB allocated, but free)
Java version: 1.8.0_131-b11, Oracle Corporation, Java HotSpot(TM) Client VM
Screen: \Display0 1920x1080, \Display1 1920x1080
Maximum Screen Size: 1920x1080
VM arguments: [-Djava.security.manager, -Djava.security.policy=file:<java.home>\lib\security\javaws.policy, -DtrustProxy=true, -Djnlpx.home=<java.home>\bin, -Djnlpx.origFilenameArg=%UserProfile%\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\31\583aa85f-330a2f35, -Djnlpx.remove=false, -Djava.util.Arrays.useLegacyMergeSort=true, -Djnlpx.splashport=50577, -Djnlp.application.href=https://josm.openstreetmap.de/download/josm-latest.jnlp, -Djnlpx.jvm=<java.home>\bin\javaw.exe]
Dataset consistency test: No problems found

Plugins:
+ apache-commons (33517)
+ ejml (32680)
+ geotools (33380)
+ jts (32699)
+ opendata (33519)
+ turnrestrictions (33537)
+ utilsplugin2 (33522)

Tagging presets:
+ https://josm.openstreetmap.de/josmfile?page=Presets/PublicTransportOneClick&zip=1

Map paint styles:
+ https://github.com/bastik/mapcss-tools/raw/osm/mapnik2mapcss/osm-results/mapnik.zip
- https://josm.openstreetmap.de/josmfile?page=Styles/PublicTransport&zip=1
- %UserProfile%\GoogleDrive\JOSM\publictransport.mapcss
- %UserProfile%\GoogleDrive\JOSM\publictransport2.mapcss

Last errors/warnings:
- W: Invalid jar file ''<josm.pref>\plugins\turnrestrictions.jar.new'' (exists: false, canRead: false)
- W: Invalid jar file ''<josm.pref>\plugins\opendata.jar.new'' (exists: false, canRead: false)
- W: Invalid jar file ''<josm.pref>\plugins\apache-commons.jar.new'' (exists: false, canRead: false)
- W: Invalid jar file ''<josm.pref>\plugins\utilsplugin2.jar.new'' (exists: false, canRead: false)
- W: Warning: Failed to scan file 'site-svn.openstreetmap.org-_applications_editors_josm_plugins_opendata_modules.txt' for module information. Skipping.

[skyper]

Yes, somehow inconsistent. Setting purge.add_relations_with_only_incomplete_members to false does only purge some of the relations.
I really wish for an option to remove objects from the dependent object list.

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2022-12-12 22:38:24 +0100 (Mon, 12 Dec 2022)
Revision:18613
Build-Date:2022-12-13 02:30:58
URL:https://josm.openstreetmap.de/svn/trunk