TAPAAL is not working with latest version of UPPAAL
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| TAPAAL |
Fix Released
|
High
|
Kenneth Yrke Jørgensen | ||
Bug Description
TAPAAL is giving a exception
Exception in thread "AWT-EventQueue-0" java.lang.
at java.base/
at dk.aau.
at dk.aau.
at dk.aau.
at dk.aau.
when trying to point it to the latest dev build of UPPAAL.
The verifyta.exe -v header has changed from:
(Academic) UPPAAL 4.1.19 (rev. 5649), September 2014 to
(Academic) UPPAAL 4.1.23 (rev. B6B873040972BC24), September 2019
Now pointing to a git version instead of SVN version. When we parse the version number we expect rev to be an integer, Pattern pattern = Pattern.
We can no longer use the rev to check a version, however dev build now always has a new version number so it should be sufficient to check the version number.
Related branches
- Jiri Srba: Approve
-
Diff: 52 lines (+16/-7)2 files modifiedsrc/dk/aau/cs/verification/UPPAAL/Verifyta.java (+15/-6)
src/pipe/gui/Pipe.java (+1/-1)
| Changed in tapaal: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| Kenneth Yrke Jørgensen (yrke) wrote | #1 |
| Changed in tapaal: | |
| assignee: | nobody → Kenneth Yrke Jørgensen (yrke) |
| Changed in tapaal: | |
| status: | Confirmed → Fix Committed |
| Changed in tapaal: | |
| status: | Fix Committed → Fix Released |
We currently track UPPAAL based on rev.nr.
public static final int verifytaMinRev = 5648;
instead of version number X.Y.Z
I think sometimes they also use X.Y.Z-U