Simantics 1.29.0 was released on 10.7.2017.
Please find change log at: Simantics 1.29.0
release/1.29.0in Git repositories and
1.29.0in SVN along with a tag called
v1.29.0in both Git and SVN:
- members/simupedia SVN
From release 1.30.0 and onwards the Simupedia repository is kept in Git/Gerrit instead of SVN and releases are made from there as well.
Simantics 1.28.0 was released on 12.6.2017.
Please find change log at: Simantics 1.28.0
release/1.28.0and a tag called
- members/simupedia SVN
Simantics 1.25.0 was released on 18.12.2016.
Please find change log at: Simantics 1.25.0
This is the first ever release made from our new Git/Gerrit system. Most of the platform code has been moved from the old Subversion repository into our Gerrit installation.
For much more information on the migration from Subversion to Git, see http://dev.simantics.org/index.php/Migration_To_Git.
Previously one had to check out org.simantics.db.impl, org.simantics.db.server and org.simantics.db.procore from dev.simupedia.com SVN-repository in order to use javacore. With the changes now the only plug-in one needs from dev.simupedia.com SVN-repository is the org.simantics.db.javacore plug-in.
To use javacore as the database a program argument
-databaseId <javacore/procore> can be used or either modify
SimanticsWorkbenchAdvisor.DEFAULT_DATABASE_ID constant from "procore" to "javacore".
For existing javacore users once updates for org.simantics.db.javacore is taken you will notice a cycle in dependencies. Just checkout org.simantics.db.server, org.simantics.db.impl and org.simantics.db.procore from Simantics SVN to fix these issues. If you want to keep using an existing workspace it is necessary to copy
1.22.0 was in development since the beginning of January 2016 and in the end it became quite a big release. One main reason was fixing the regressions and fallout of the move to the Eclipse 4.5.1 target platform that was done in Simantics 1.21.0. Also having Apros 6.06 built on top of Simantics 1.22 contributed to the amount of improvements and fixes.In retrospect it is also worth mentioning that we had Simantics releases 1.19.0, 1.20.0 and 1.21.0 between November 2015 and January 2016. Here are their change logs:
For developers it is worth mentioning that in addition to Simantics 1.21 making the move to the Eclipse 4.5.1, the platform switch also moved Simantics into the Java 8 world. Since 1.22 most of the code requires or is at least free to use Java 8 features.
After several months of delays, Simantics 1.18.1 has finally been released.
See 1.18.1 change log for the related changes.
In January 2015, a service release 1.13.5 was also made.
A new optional long text field called Release notes has been added for platform issues.
This field will be used in the future for automatic generation of release notes for releases based on the closed issues.
From now on if you resolve platform issues containing changes that users or developers should be aware of, write a concise short description of the issue in the Release notes field.
We've installed the Redmine Tags (https://github.com/ixti/redmine_tags) and Redmine Issue Templates (http://www.r-labs.org/projects/issue-template/wiki/About_en).
Tags can already be seen in use in the issue list. You'll find the current tag cloud in right side link pane. Tags allow us to multi-categorize issues which naturally allows much more powerful issue filtering and workflow handling. See Tags for a list of some standard tags you can use and don't be afraid to make up your own when necessary.
Issue templates have also been put to use. There are now two global templates defined, one for bugs and one for features. You can check them out by going to https://www.simantics.org/redmine/projects/simantics-platform/issues/new and selecting the issue template from the available combo box.
You can find the change log here.
Our ISP is doing network infrastructure changes on Monday 11.11 and the server may not be reachable during the day.
Also available in: Atom