Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EMF Compare/Specifications/ProvideContentMergeViewerForResourceAttachmentChanges"

(New page: = Evolution Specification: Provide content merge viewer for resource attachment changes = Current status is '''DRAFT''' == Preamble == Provide content merge viewer for resource attachm...)
 
Line 10: Line 10:
  
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=398360 Bug 398360] - Content merge viewer for resource attachment changes
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=398360 Bug 398360] - Content merge viewer for resource attachment changes
 
+
*[https://git.eclipse.org/r/#/c/9930/ Review 9930]
 
== Introduction  ==
 
== Introduction  ==
  

Revision as of 12:16, 25 January 2013

Evolution Specification: Provide content merge viewer for resource attachment changes

Current status is DRAFT

Preamble

Provide content merge viewer for resource attachment changes.

_Relevant tickets_ (links to the Bugzilla tickets which are related to the change):

Introduction

Currently there is no content merge viewers for the resource attachment changes. EMF compare will provide a specific one close to the content merge viewer on non containment reference changes, but displaying the direct contents of the changed resource.

Detailed Specification

TODO.

Backward Compatibility and Migration Paths

Metamodel Changes

TODO. (Document any change to the metamodel. If they require a migration operation, mention it and describe the general idea of how migration process. If any information can be lost during the migration, mention it clearly. If validation rules must be added/modified, mention it also.)

API Changes

TODO. (List every API addition, removal and deprecation. For each removal and deprecation, indicate the migration path for existing code.)

User Interface Changes

TODO. (List every user-visible change in the interface. Here "user" includes not only end-users but also developpers.)

Documentation Changes

TODO. (List every documentation needing an update here, starting by the New and Noteworthy documentation.)

Tests and Non-regression strategy

TODO. (This part of the document should describe the strategy to use to correctly test the evolution and guarantee the non-regression.)

Implementation choices and tradeoffs

TODO. (Any important tradeoff or choice made during the implementation should be referenced here with pros/cons leading to the final decision.)

Back to the top