Closed juli1 closed 13 years ago
The project needs an XText nature: right click on the project, Configure > Add XText nature. AADL files must have extension .aadl2 in this snapshot. Then the text editor should mark errors, etc. We forgot to put this in the release notes. AAXL files are gone for declarative AADL models they only exist for instance models.
Hi,
I tried, it works. However, automatically adding the XText nature would be useful :) So, now, text is recognized but I'm not able to create aaxl2 files or even instance files. How can I do ?
First, right click on the .aadl2 file > Open with... > Aadl2 Editor. That should give you an outline view. Then, in the outline view, right click on a system implementation. That context menu has actions for instantiation. It also has a save as XMI action, which creates an aaxl2 file. Both actions are also available in the context menu in the aadl text editor.
Indeed, you're right. So, I am able to instantiate the system, no problem at all for that and it creates a .aaxl2 with the instantiated system. However, I don't see the aaxl2 file that correspond to my textual .aadl2 file, is it normal ?
Yes, that's normal, we don't need them any more. If you want the aaxl file, use the "Save as XMI" command form the context menu (AADL editor or outline view).
When I start OSATE2 and start a new AADL project, I am not able to either create an AADL file or even create a new package. Then,if I create the AADL file by myself (using the resources perspective), the AADL perspective does not recognize the syntax and I cannot generate any AAXL file (unavailable option).