Skip to content

Releases: overturetool/overture

The Overture Tool version 2.0.8

21 May 13:09
Compare
Choose a tag to compare

19 May 2014

What's New?

This release is minor bugfix release. See the fix list 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 info@overturetool.org, 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

Bug fixes

Please note that the interactive list is at https://github.com/overturetool/overture/issues?milestone=16&state=closed

The Overture Tool version 2.0.6

01 Apr 10:26
Compare
Choose a tag to compare

1 April 2014

Please note that this is the abbreviated release note: a longer note with more information is available in the main repository at https://github.com/overturetool/overture/tree/development/documentation/releasenotes.

What's New?

This release is minor bugfix release to improve the accuracy of the typechecker.

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 info@overturetool.org, 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

Bug fixes

Please note that the interactive list is at https://github.com/overturetool/overture/issues?milestone=15&state=closed

The Overture Tool version 2.0.4

12 Mar 08:35
Compare
Choose a tag to compare

Overture 2.0.4 Release Notes — 11 March 2014

Please note that this is the abbreviated release note: a longer note with more information is available in the main repository at https://github.com/overturetool/overture/tree/development/documentation/releasenotes.

What's New?

This release is bugfix release --- many old bugs have been cleared, and some interface issues have been fixed.

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 info@overturetool.org, 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

Bug fixes

Please note that the interactive list is at https://github.com/overturetool/overture/issues?milestone=14&state=closed.

#258 Coverage markers are out by one character
#254 Standard Eclipse user interface features "missing" from 2.0.0
#246 The bus declarations given in the vdm real time log produced by the interpreter are incorrect
#207 Editor gives errors while editing a VDM-SL model (with errors)
#198 Inconsistent editor tabstops in Linux/Windows
#195 Warnings with IDE at startup with a large existing workspace
#193 Projects in working sets don't get error marker updates
#188 Syntax error highlightling sometimes goes to first line
#184 VDM++ Editor not correctly showing error locations
#156 External editor doesn't give hover text for error/warnings
#154 Saving
#144 Latex coverage table wrong for overloaded names
#143 Some VDMUnit error strings cause parser errors
#133 Extended explicit functions missing from launchers
#118 Generating coverage with .doc files is broken
#108 Tab expansion in Word coverage output is wrong
#96 Process console not selected when starting a debug
#63 Coverage display japanese chars
#34 UTF-VDM RT Realtime Log can't display UTF-8 Chars

The Overture Tool version 2.0.2

31 Jan 19:03
Compare
Choose a tag to compare

Overture 2.0.2 Release Notes — 31 January 2014

What's New in Overture 2.0.2?

This release is primarily bugfix release --- our main goal was to incorporate fixes from VDMJ that had been made since we prepared v2.0.0. A list of the bugs fixed is at the end of this release note.

New in this release is the preliminary inclusion of a constraint solver feature that uses the ProB model checker to broaden the executable subset of VDM that we cover.

System Requirements

Overture is based on the Eclipse platform. To run it, you must have a Java runtime system installed, version 6 or later.

Download & Installation

Documentation, including tutorials and a language manual, are bundled in the download package, and are also available from the Overture website.

Overture can be downloaded from the SourceForge site, at https://sourceforge.net/projects/overture/files/Overture_IDE/2.0.2/.

The download file is a ZIP archive. To install the tool, unzip the file in a convenient location. The main executable is in the top level directory, called Overture.

We will be making an exe-based installer available for Windows user at a future point.

Upgrading:

  • ATTENTION: If you are using the ZIP archive to update and if your workspace was located inside the previous installation directory, DO NOT FORGET TO BACKUP the workspace or it will be lost when the old version is deleted.
  • If you are upgrading with the ZIP archive: do not unzip the latest version on top of the oldest one. You will need to delete the previous version before continuing the installation.

Uninstalling

To uninstall Overture, remove the contents of the directory where you installed it. There are no other files stored on the system, apart from any workspace files you may have created.

For Windows users, if the Overture installer was used previously, it is possible to uninstall via the uninstall shortcut created by the installer in the start programs or via the Uninstall menu in the Control Panel.

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 info@overturetool.org, 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.

Frequently Asked Questions

  • Who's behind Overture?

    Overture was written by the members of the Overture project, a group of industry and academic researchers interested in the use of VDM.

  • How is Overture licensed?

    Overture is open source. It is released under a GPLv3 license.

  • What can I do to help?

    If you are interested in helping you can drop a mail to info@overturetool.org. You are also very welcome to fork our code on GitHub and send us pull requests.

  • Where is Overture source code?

    Overture source code is hosted by GitHub, within the overturetool organisation account.

Other Resources and Links

Bug fixes

Please note that the interactive list is at https://github.com/overturetool/overture/issues?milestone=13&state=closed

#260 Type check of operations
#259 Suppress warnings from tycho about default env
#257 Missing type error for value definitions calling operations
#256 Polymorphic measure functions are not called
#252 VDM-SL traces fail when referencing state data
#248 Move module template readmes into place
#242 Outline of large structures (modules/classes) collapses and unfolds if source is changed and saved
#241 Combinatorial Testing with Japanese characters in module/class and traces names does not work
#239 Correction to atomic evaluation with class invariants
#238 Correction to satisfiability POs
#237 Removed the "nil" type from the parser
#236 Allow breakpoints on class invariant expressions
#235 Correct type checking of static calls to non static operations
#234 Allow static operation postconditions to use "old" static data
#233 Corrected scheduling policy unfairness that affects stop ordering
#232 Only allow stop to work on the same CPU as the caller
#231 Fix breakpoints with "for" statement without "by" clause
#230 Correction to type checking of nil returns
#229 Type checker correction for "while true" loops
#228 Corrections to type check of static operation guards
#227 Correction for sync guards on static operations
#226 Correction for two successive stop calls
#225 Correction for deadlocked CT test cases
#224 Correction to stopped thread handling
#223 First cut of RM#18, sporadic threads
#222 First cut of RM#20, thread stop statements
#220 Suppress stderr output in CT tests
#219 Correction to traces running in VDM-RT
#218 Clean up threads properly with exit statements
#216 Some class invariants cause thread scheduling problems
#215 Incorrect satisfiability POs
#214 Remove the nil type from the parser
#213 Correct type checking of static calls to non static operations
#212 Allow static operation postconditions to use "old" static data
#211 Corrected scheduling policy unfairness that affects stop ordering
#210 Type checker correction for "while true" loops
#209 Problem with sync guards on static operations
#173 Operations/functions in a flat SL spec are marked as unused.
#106 Breakpoints on initializers don't work
#71 Self update site name is missing
#13 VDMJ function variable scoping error

The Overture Tool version 2.0.0

04 Dec 14:15
Compare
Choose a tag to compare

This is the new release of the Overture Tool based on a unified internal abstract syntax tree. Ready to run packages are available at https://sourceforge.net/projects/overture/files/Overture_IDE/2.0.0/

What's New in Overture 2.0.0?

This release is a re-engineering of the internal structure of Overture
to use a single AST across all components in the system.

System Requirements

Overture is based on the Eclipse platform. To run it, you must have a
Java runtime system installed, version 6 or later.

Downloading

Overture can be downloaded from the SourceForge site, at
https://sourceforge.net/projects/overture/files/Overture_IDE/2.0.0/.

Documentation, including download instructions, tutorials and a
language manual, are bundled in the download package, and are also
available from the Overture website.

Installing

The download file is a ZIP archive. To install the tool, unzip the
file in a convenient location. The main executable is in the top
level directory, called Overture.

We will be making an exe-based installer available for Windows user at
a future point.

Upgrading:

  • ATTENTION: If you are using the ZIP archive to update and if your
    workspace was located inside the previous installation directory, DO
    NOT FORGET TO BACKUP the workspace or it will be lost when the old
    version is deleted.
  • If you are upgrading with the ZIP archive: do not unzip the latest
    version on top of the oldest one. You will need to delete the
    previous version before continuing the installation.

Uninstalling

To uninstall Overture, remove the contents of the directory where you
installed it. There are no other files stored on the system, apart
from any workspace files you may have created.

For Windows users, if the Overture installer was used previously, it
is possible to uninstall via the uninstall shortcut created by the
installer in the start programs or via the Uninstall menu in the
Control Panel.

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 info@overturetool.org, 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.

Frequently Asked Questions

  • Who produced Overture?

    Overture was written by the members of the Overture project, a group
    of industry and academic researchers interested in the use of VDM.

  • How is Overture licensed?

    Overture is open source. It is released under a GPLv3 license.

  • What can I do to help?

    If you are interested in helping you can drop a mail to
    info@overturetool.org. You are also very welcome to fork our code
    on GitHub and send us pull requests.

  • Where is Overture source code?

    Overture source code is hosted by GitHub, within the
    overturetool organisation
    account.

Other Resources and Links