Jump to: navigation, search

EMF Compare/Logical Resources

Logical resource support will allow EMF Compare to better handle fragmented models. Among others, this support will allow EMF Compare to prevent comparison/synchronize/commit actions without taking into account the whole set of resources the target depends on. For example, you wouldn't be able to compare a fragment without considering its parent if there are links between the two.

Concerned actions

The VCS we aim at are CVS and Git (through the eGit plugin). For each of those, these are the actions that will be concerned (and, thus, should be tested) by the logical resource support :

CVS

  • Synchronize
  • Commit
  • Update
  • Create patch
  • Apply patch
  • Compare with (all)
  • Replace with (all)

Git

Git patches, and fetch/pull are commit-based. Handling commit and synchronization/comparison should be enough ... We still need to check on fetch and pull that the whole logical resource is being retrieved from the remote repository in case the person that committed that resource didn't use the logical resource integration her/himself.

  • Synchronize
  • Commit
  • Fetch
  • Pull
  • Compare with (all)
  • Replace with (all)