TAPAAL

Path to verifytapn should be hardcoded

Bug #784757 reported by Morten Jacobsen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
TAPAAL
Fix Released
Low
Unassigned
TAPAAL 2.0.0

Bug Description

Since verifytapn is going to be distributed with TAPAAL, we should hardcode the path to it before releasing a new version, so users don't have to locate the executable themselves.

Revision history for this message
Kenneth Yrke Jørgensen (yrke) wrote :

Might be a good idea with a default location, but the user should still be able to specify an alternativ location.

Changed in tapaal:
status: New → Triaged
importance: High → Low
Revision history for this message
Morten Jacobsen (mortenja) wrote :

I don't see why that should be the case? The engine will be distributed with TAPAAL, following a scheme similar to UPPAAL, so I don't see the benefit of allowing this path to be changed..

Verifyta path setup should of course stay as it is, since verifyta is not distributed with TAPAAL.

Revision history for this message
Jiri Srba (srba) wrote :

The issues has been sorted out (both verifytapn and verifyta are treated in the same way but we hardcode
the location of verifytapn in the script that runs the application, but it can be changed.

Changed in tapaal:
status: Triaged → Fix Committed
Kenneth Yrke Jørgensen (yrke)
Changed in tapaal:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.