Modify

Opened 4 years ago

Closed 4 years ago

#2510 closed enhancement (fixed)

[Patch] ConflictItem - Refactoring

Reported by: Gubaer Owned by: Gubaer
Priority: minor Component: Core
Version: latest Keywords: conflict resolution merge
Cc: karl.guggisberg@…

Description (last modified by stoecker)

1JOSM 1 Server JOSM 2
2Create
amenity=biergarten
testkey=value1
and upload
amenity=biergarten
testkey=value1
id=1
version=1
3amenity=biergarten
testkey=value1

id=1
version=1
Downlad
amenity=biergarten
testkey=value1
id=1
version=1
4Update
amenity=biergarten
testkey=value2
id=1
version=1
and upload
amenity=biergarten
testkey=value2
id=1
version=2
5amenity=biergarten
testkey=value2
version=2
Update
amenity=biergarten
testkey=value3
version=1
6amenity=biergarten
testkey=value2
version=2
Download and merge results in a conflict as expected
7Resolve conflict and decide to keep my value, i.e. testkey=value3
8Upload results in 409 conflict. Local version is still version 1

The problem is in step 7. If the user decides to keep his value the local version is not updated to the higher version from the server.

See patch for a fix.

Attachments (2)

property-conflict.patch (1000 bytes) - added by Gubaer 4 years ago.
conflict-resolution.patch (2.4 KB) - added by Gubaer 4 years ago.

Download all attachments as: .zip

Change History (8)

Changed 4 years ago by Gubaer

comment:1 Changed 4 years ago by Gubaer

  • Cc karl.guggisberg@… added

comment:2 follow-up: Changed 4 years ago by anonymous

  • Resolution set to fixed
  • Status changed from new to closed

Applied in r1567. I have also made the same change for the DeleteConflict and PositionConflict classes. We should perhaps investigate moving that functionality up in the class hierarchy?

comment:3 in reply to: ↑ 2 Changed 4 years ago by Gubaer

  • Priority changed from major to minor
  • Resolution fixed deleted
  • Status changed from closed to reopened
  • Summary changed from [Patch] Bug when keeping local (my) value in property conflict resolution to [Patch] ConflictItem - Refactoring
  • Type changed from defect to enhancement

Replying to anonymous:

Applied in r1567. I have also made the same change for the DeleteConflict and PositionConflict classes. We should perhaps investigate moving that functionality up in the class hierarchy?

like so? => see patch

Changed 4 years ago by Gubaer

comment:4 Changed 4 years ago by stoecker

  • Description modified (diff)

Actually I do not know what to do with this ticket? Does this still apply? Karl, can you take care of it yourself?

comment:5 Changed 4 years ago by Gubaer

  • Owner changed from team to Gubaer
  • Status changed from reopened to new

This reminds me that the new extended conflict resolution dialog does net yet resolve conflicts due to different positions or different deleted states!

I'll take care of it.

comment:6 Changed 4 years ago by Gubaer

  • Resolution set to fixed
  • Status changed from new to closed

r1654 includes merge support for coordinate conflicts and conflicts in deleted state, too.

This ticket is outdatet and the the patch attachment:conflict-resolution.patch is not needed anymore.

=> Closing

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed .
as The resolution will be set. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.