The database is updated on doing a SUBMIT in your task editor, the outgoing arrows in task list disappear to indicate this
The concurrent changes in the DB are downloaded on synchronize and will show a change in the task list automatically. A conflict is flagged when the same field is changed.
You can prepare a comment and save it, and that comment will survive most synchronisations. But when you mark a task as completed but not commit, you may get a conflict later.
I believe two sets are maintained, a strict copy of the server, and a copy with local edits. Comparison flags updates, changes and possible conflicts.
Maarten
Op 16 apr 2009, om 08:45 heeft Larry Edelstein het volgende geschreven:
How does Mylyn deal with conflicting changes? If I download a database task to Mylyn, and then I modify the task locally, and it is also modified in the database, what happens when I upload the task?
Does AbstractRepositoryConnector.hasTaskChanged() have something to do with it? If so: what is the contract that this method is supposed to implement?
??
??????
Larry Edelstein
Senior Member of Technical Staff
salesforce.com
_______________________________________________
mylyn-integrators mailing list
mylyn-integrators@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/mylyn-integrators
