This repository contains the Sireum OSATE Plugin that translates AADL instance models to AIR and then to downstream Sireum tools such as AWAS.
-
Install an OSATE development environment -- the rest of these instructions will refer to this as Eclipse
You'll probably get plugin version errors which usually have to be resolved before you can build the OSATE source. A workaround is to navigate to
Preferences
>Plug-in Development
>API Errors/Warnings
>Version Management
and set all the severity levels toIgnore
. -
Install Sireum Kekinian
-
Clone the repository
git clone --recurse-submodules [email protected]:sireum/osate-plugin.git
-
From the command line
mkdir osate-plugin/org.sireum.aadl.osate/lib ln -s $SIREUM_HOME/bin/sireum.jar osate-plugin/org.sireum.aadl.osate/lib/sireum.jar
-
Launch Eclipse and go to File -> Import...
-
Expand the General folder and select Existing Project into Workspace, then click Next.
-
Enter the path to the directory where you cloned the repository and then select all the available projects from the project listings and click Finish.
-
Navigate to Preferences -> Java -> Installed JREs. Select the JRE that is checked (probably 'jre (default)') and then click Edit.... If you launch Eclipse from the command line (ie. it will inherit your environment variables) then add
-ea -Dorg.sireum.home=${env_var:SIREUM_HOME}
to Default VM arguments, otherwise add-ea -Dorg.sireum.home=<path-to-sireum-home>
. Click Finish then Apply and Close. -
To resolve access restrictions errors related to
UiUtil
-
Navigate to: Preferences -> Java -> Compiler -> Errors/Warnings -> Deprecated and restricted API, and
-
Change Forbidden reference (access rules) from
Error
toWarning
.
-
-
Optional: Rebuild tool jars
-
Awas
git clone --recursive -b master [email protected]:sireum/v3.git sireum-v3 git clone [email protected]:sireum/air.git sireum-v3/aadl/ir git clone [email protected]:sireum/v3-awas.git sireum-v3/awas export SIREUM_HOME=`pwd`/sireum-v3 ./sireum-v3/bin/sbt-launch.sh "project awasJar" assembly cp ./sireum-v3/awasJar/target/scala-2.12/awasJar-assembly-0.1.0-SNAPSHOT.jar <ostate-plugin-dir>/org.sireum.aadl.osate.awas/lib/awasJar-assembly-0.1.0-SNAPSHOT.jar
-
If the OSATE runtime instance looks like this screenshot
then you need to use a JRE that was not built under macOS 14. For example,
Zulu
17.0.10+7
does not exhibit the issue and doing vtool -show java
on it shows it was
built under macOS 11.1
If it takes a long time for the splash screen to appear when launching an OSATE runtime instance, remove the hamcrest entries from the OSATE2 launcher here.
If the slow startup occurs for a plugin unit test, open the unit test's runtime
configuration, select the Plugins
tab, change Launch with:
to
Plug-ins selected below
, search for hamrcrest
and uncheck the
org.hamrcrest.library
entry