Closed eclipse-qvtd-bot closed 12 hours ago
By Ed Willink on Jun 28, 2020 13:47
Thanks for reporting.
I presume that you are doing New->Example ... QVTr HFSM2FSM
When I do this there are actually two launch files under .settings. Perhaps your package explorer is set to filter "." resources. (The documentation needs a refresh now that there are two launches.)
However when I try to run, all is indeed not well. The internal $primitive$ typed model is not hidden at all, and is perhaps the cause of hier rather than flat being offered.
By Ed Willink on Jun 28, 2020 18:25
(In reply to Ed Willink from comment #1)
The internal $primitive$ typed model is not hidden at all
The new TypedModel.isPrimitove/isThis/isTrace never got used by the dialog support.
and is perhaps the cause of hier rather than flat being offered.
Not really. Somehow an isEnforceable() got changed to isOutput() when potential rather than actual output was indeed correct.
By Ed Willink on Jun 28, 2020 18:42
Fix built as:
https://download.eclipse.org/mmt/qvtd/updates/nightly/0.23.1/
By Steffen Becker on Jun 28, 2020 22:37
Confirmed. It works again. Thank you.
By Ed Willink on Jun 29, 2020 07:49
Thanks for confirming. The maintenance release should occur on Friday.
By Ed Willink on Jul 14, 2020 09:23
(In reply to Ed Willink from comment #5)
Thanks for confirming. The maintenance release should occur on Friday.
Oops. Forgot.
Fix is available now in 0.23.1 and 0.24.0M1.
| --- | --- | | Bugzilla Link | 564671 | | Status | RESOLVED FIXED | | Importance | P3 blocker | | Reported | Jun 25, 2020 22:31 EDT | | Modified | Jul 14, 2020 09:23 EDT | | Reporter | Steffen Becker |
Description
Running the include HFSM2FSM is broken in Eclipse 2020-06. After importing the project, the launch configuration file is missing - in contrast to the description in the help.
Trying to create one does not work. Several issues happen in the create run configuration dialog:
I worked around all issues by using a persisted launch file which I manually changed to the following in a text editor. However, when opening the launch in the UI again, the UI resets all values to invalid options again :-(
--- Working launch config file ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>\