Compare project repository (emf.compare)
Java HTML Other
Latest commit 9749f4c Jan 11, 2018 @planger planger [529413] Extension point for defining files included in EMFModelProvider
This change replaces the enablement expression listing all file
extensions explicitly, as used before this change for enabling the
EMFModelProvider for certain files, with a property tester that reads
the files to be included from an extension point instead.

This allows other plug-ins to contribute inclusions of files. These
third-party plug-ins can specify a tester in the form of a content type
or a file extension that shall be handled by the EMF Model Provider, or
in the form of a class that determines whether to include a file or not
at runtime.

The dynamic testers enables third-party plug-ins to perform a more
fine-grained analysis to whether or not include a file, for instance,
Papyrus may not only specify that ALL properties files shall be handled
by the EMFModelProvider but only those where an equally named di file
exists.

Bug: 529413
Change-Id: Id572261fdc4e3b8057b5293338b160230a59815b
Signed-off-by: Philip Langer <planger@eclipsesource.com>

README.textile

EMF Compare

Installation

Prerequesites

EMF Compare can be installed on the following Eclipse platforms :

  • Eclipse version 3.5 (Galileo) to Eclipse version 4.4 (Luna)
  • Java 1.5 to Java 1.7

Compatibility

Take note that parts of the EMF Compare optional supports can only be installed on later Eclipse versions. Namely :

Feature Eclipse 4.4 (Luna) Eclipse 4.3 (Kepler) Eclipse 4.2 (Juno) Eclipse 3.7 (Indigo) Eclipse 3.6 (Helios) Eclipse 3.5 (Galileo)
EMF Compare Core X X X X X X
EMF Compare RCP UI X X X X X X
EMF Compare IDE UI X X X X X X
EMF Compare UML integration X X X
EMF Compare GMF integration X X X
EMF Compare EcoreTools integration X X X
EMF Compare Papyrus integration X X X

Reporting Bugs

There may be errors in the /.metadata/.log or even on stdout that can help you track down and problem.
When reporting errors, please include stack traces when applicable and the commit id or the version your plugin is built from, or the version of the plugin if it does not contain a date.

Build

EMF Compare can be built using maven from within the org.eclipse.emf.compare-parent sub-folder of this repository :

mvn clean package -Pmars

The above example will build the EMF Compare binaries against a Mars platform. Select the appropriate profile according to the platform you wish to install EMF Compare on, one in [mars, luna, kepler, juno, indigo, helios, galileo].

You can also check the tests using

mvn verify -Pmars --fail-at-end -Dmaven.test.failure.ignore=true

Contributing

  • You need an Eclipse user account. You already have one if you are an Eclipse commiter or have a Bugzilla account. Otherwise, use this form.
  • Sign the Eclipse Contributing License Agreement (CLA) : Please go to your user page , then to the CLA tab once you’re logged in and follow the instructions.
  • Make sure you use the proper user information on your git clone’s configuration :
    • $ cd <path/to/repository>
    • $ git config --local user.name "<Full Name>"
    • $ git config --local user.email "<your.mailyourmail.com>"@
  • Make small logical changes.
  • Provide a meaningful commit message.

EMF Compare uses gerrit for peer reviews.
To configure it on your repository, please look up how to setup your SSH keys and remote on the wiki .
A detailed guide on the commit message’s format can be found further down this same page.

Once properly configured, you will be able to request a review by simply pushing your commit on this new remote.

A comprehensive contributor guide can also be found on the project’s wiki