Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rollback issue #305

Merged
merged 2 commits into from
Sep 24, 2019
Merged

Rollback issue #305

merged 2 commits into from
Sep 24, 2019

Conversation

MSementsov-Ibk
Copy link
Contributor

BehaviorCommand: Commands need to be rolled back from last to first.

Signed-off-by: Michael Sementsov michael.sementsov@ibykus.de

Signed-off-by: Michael Sementsov <michael.sementsov@ibykus.de>
@fgdrf
Copy link
Contributor

fgdrf commented Oct 1, 2018

It would be great to have an unit test for this behavior, would you provide it?

@fgdrf fgdrf added this to the 2.1.0 milestone Oct 1, 2018
With timestamps, so you can check which command was executed first (and rolled back first).

Signed-off-by: Michael Sementsov <michael.sementsov@ibykus.de>
@fgdrf
Copy link
Contributor

fgdrf commented Oct 16, 2018

Waiting for Jenkins feedback : https://ci.eclipse.org/udig/job/uDig-PR/31/

@fgdrf fgdrf added the bug label Oct 23, 2018
@fgdrf fgdrf merged commit abc0dc4 into locationtech:master Sep 24, 2019
fgdrf pushed a commit to fgdrf/udig-platform that referenced this pull request Dec 23, 2019
* Rollback needs to be done in reverse order

Signed-off-by: Michael Sementsov <michael.sementsov@ibykus.de>

* Rollback test

With timestamps, so you can check which command was executed first (and rolled back first).

Signed-off-by: Michael Sementsov <michael.sementsov@ibykus.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants