3.3.1
EMF Compare 3.3.1 mainly brings improvements on our integration with EGit and the diagram comparisons through Papyrus.
The performance of comparisons for models under git version control have been increased, mainly on fragmented models. The detection of parts of the logical model has also been improved notably for the files that may not be in direct correlation such as Payrus di and notation files.
The conflict detector has also seen a major overhaul so that it scales better for models with a large number of differences.
The project leadership certifies that the APIs in this release are "Eclipse Quality".
Continuous Integration
The project is built from the EMF Compare HIPP through Tycho. A nightly is built once a day if the SCM polling sees a change from the last build.
Unit Tests
2000+ unit tests launched on every build.
Code coverage is about 75% of the code base.
Code Quality
Common formatter and compiler configuration used throughout the whole project's plug-ins.
Checkstyle activated on all distinct plug-ins.
Eclemma used on a regular basis to ensure and improve code coverage from the unit tests.
Yourkit java Profiler used on a regular basis to improved performances and avoid bottlenecks.
Findbugs launched on a regular basis to avoid detectable bugs.
Javadoc represents about 40% of the java source code.
An analysis of the code base is available on Open Hub.
EMF Compare is conforming to the Eclipse user interface guidelines.
Localization : integrated into Babel
There are no outstanding issues with the API state of this release. All mehods and classes that face deletion have been marked as deprecated with instructions on how to switch to the new behavior, and will stay in the code base until the next release.
No standard exists concerning the model comparison, though EMF Compare works nicely with any standard-based metamodel.
Since the 1.2 release a specific support for the UML standard is included in EMF Compare. This is also included in the 3.* stream.