Release Notes / Release

Java 10 wasn't recognized as a valid JVM version, which prevented our Java and C++ parsers to work. We fixed how the Java version is checked, so it should work smoothly now!

The best-match searcher -used by the rename detection- didn't support special characters in declaration identifiers (such as '(', ')' or '\' ). That caused the XML external parser (https://github.com/RalfKoban/xml-semantic-external-parser) to throw some errors. Fixed.

There were some corner cases that caused using/import declarations to be placed at the end of the file or after type declarations. We fixed our merge algorithm so it automatically groups that kind of declarations to prevent them from being scattered all over the document.

"An item with the same key has already been added" exception was thrown when there was a renamed – renamed conflict for a container declaration with changes in the destination contributor. Fixed.

The integrated Java and C++ parsers did not work with Java 9. Fixed.

The XMerge feature of the regular text-based mergetool was not working as expected due to a missing library (Svg.dll). Fixed.

Now the required library is bundled in windows installer.

SemanticMerge showed the license notification through the "Get License" button when the license is an auto-renewal one. Fixed.

The differences were not correctly calculated when an option related to the file content was changed (e.g. reformat source code, encoding). Fixed.

A "No external merge tool has been specified in order to proceed with the merge" warning was shown when the merge was solved using the text-based tool. Fixed.

The automatic installation of semanticmerge for PlasticSCM version control was not working correctly. So, even if PlasticSCM was correctly configured, the tool said it was not. Fixed.