The original ESROCOS workflow is intended to compile an aadl file for each imported types package and import those aadl files into the tast gui / developed component.
As the TASTE gui does not seem to support including multiple aadl files at the moment tool development switched to a different approach where the asn files are compiled into a single (monolithic) aadl file which is then included in the TASTE gui.
Development takes place on the respective monolithic_asn branches.
The original ESROCOS workflow is intended to compile an aadl file for each imported types package and import those aadl files into the tast gui / developed component.
As the TASTE gui does not seem to support including multiple aadl files at the moment tool development switched to a different approach where the asn files are compiled into a single (monolithic) aadl file which is then included in the TASTE gui.
Development takes place on the respective monolithic_asn branches.