Hi there! We’re pleased to announce a new release of SemanticMerge: 0.9.30 is now out! Grab it here.
This is what is new in 0.9.30:
Improved startup time!
As promised, we’ve greatly reduced the merge startup time. It was all related to GUI operations, so it was not hard to figure out how to make it faster.
Just to give you some numbers: a merge that used to take 5 seconds to show up, is now done in less than 1.4 seconds… Should be pretty acceptable now.
Automatic merge option!
We hold this one for a while until everyone was familiar enough with Semantic. Now it is possible to run merges in automatic mode if there are no manual conflicts to be solved.
In order to launch the tool in the “try to do it as automatic as possible” mode, use the new “--automatic" parameter or “-a” for short.
It won’t deal with conflicts in the body of the methods automatically yet (so you’ll have to run manually these ones even if there are no conflicts in the same line of the body of a method).
Restart diff button
Now a new button ("restart diff") in semantic diff tool is available to allow you to refresh or reload the code.
We’ve closed the corresponding User Voice request.
We’ve also fixed an issue in SemanticMerge: now the textbox of the source contributor is reloaded during the restart merge process.
Null fixed in diff recalculation
Several issues related with the differences recalculation have been fixed. A couple of users have reported this and have already been notified by email. Thanks!
Fixed a null in “unmatch”
We fixed several issues related to matching and unmatching differences. They should be all ironed out now.
Fixed an issue when the JVM wasn’t found
We made several improvements in the Java parsing code: now, the -vm parameter specifies the path to the Java Virtual Machine executable, instead of the path to the directory. This is much easier to understand.
Example: semanticmergetool.exe .... -vm="C:\Program Files\Java\jre7\bin\java.exe"