The Overture Tool version 2.2.0
Overture 2.2.0 Release Notes — 11 February 2015
What's New?
This release of the Overture tool marks the transition of tool to use the Java SE 7 runtime system. There are also several small fixes as recorded below.
Reporting Problems and Troubleshooting
Please report bugs, problems, and other issues with the tool at https://github.com/overturetool/overture/issues.
If you encounter a problem with the Overture IDE itself, please contact the Overture project and we will try to help. You can contact us at [email protected], or use StackOverflow — we monitor for questions using the vdm
, vdm++
, or vdmrt
tags.
If you encounter a problem with a VDM specification, please try to make a small example that illustrates the problem before you contact us. If you are sure the bug is not already known in the GitHub issues list, you can create a new bug report.
Other Resources and Links
- Overture Community site
- VDM Tutorials
- VDM Examples
- Wikipedia on VDM
- Overture Developers Wiki on GitHub
- The Old Overture Wiki for developers
Bug fixes
Please note that the interactive list is at https://github.com/overturetool/overture/issues?q=milestone%3Av2.2.0
- #411 Problem with object binds in traces
- #410 Internal error in the trace interpreter
- #409 Problems with filtering of tests in traces
- #408 Div rem and mod do not detect division by zero
- #407 scope of inherited constant values
- #406 Problem with type check of set ranges
- #405 Problem with access specifiers in traces
- #404 Problem with pretty printing of POs
- #386 Build: target JavaSE1.7 instead of 1.6
- #289 Type information does not seem to be fully taken into account in POG