-
AADL model units are currently contributed via an extension point. We need a registry that can be populated programmatically to operate in standalone mode.
child of #1538
-
When an end to end flow refers to a data access, an error is reported complaining that data access references are only permitted at the beginning or end of an end to end flow. This validation doesn't …
-
I have a new download of osate2 2.3.4 on debian 9. The first example I pulled into and AADL project was the embedded controller (as I wanted to play with the prism export). Embedded-control and embe…
-
OSATE 2.4.1
I was editing a file that contained AADL text with Syntax errors.
When I did a save it threw away some of the text with the syntax errors.
Example: I copied into a property set
v…
-
## Summary
When I create array ports, connect them, and use those in a flow, the instantiated flow has only source and sink and not the connections.
## Expected and Current Behavior
The instance …
-
A very simple AADL system.
```
package test
public
system sin
end sin;
system implementation sin.impl
end sin.impl;
end test;
```
I select `System Impl sin.impl`, right click, and sele…
-
- Created fresh development environment per instructions on osate.org.
- Received errors in org.osate.aadl.modelsupport and org.osate.analaysis.flow.tests projects.
- Those projects are configured t…
-
We should remove all unnecessary plug-in dependencies.
-
## Summary
When I open the following in the editor, the Outline view only shows declarations down through System.Refine2. System.Refine3 and System.Refine4 are shown in the editor but do not appear …
-
## Summary
OSATE allows an index when associating properties with a connection even though AADL doesn't have connection arrays.
## Expected and Current Behavior
AADL code like the following shoul…