Hi everyone,
This is to let you know that a change was made to how the builtin and sample applications are packaged and staged for installation. The applications are now delivered via a .oar file (ONOS Application aRchive). This ZIP file is produced automatically by the build process using the app.xml file in the module base directory and includes the app.xml, features.xml and any bundle artifacts contributed/needed by the application. The oar file is also installed into maven repository, which means upon release, they will also be available in the Maven central.
Part of this change means that the overall features.xml file no longer defines any application specific features. Instead, each application can either define its own set of features in feature.xml file (also in the module base directory) or if the application is a single-bundle one, the features.xml file will be automatically generated to include the project bundle.
The shell utilities onos-setup-karaf and onos-package both stage all *.oar files in the apps directory to make them available as pre-installed applications at run-time. As before, ONOS_APPS variable can be used at onos-setup-karaf/onos-install/onos-configure time to tailor which apps will be marked as activated.
A new CLI has been added ‘app install <url>’ which allows installation of apps from a URL via command-line. Wiki will be updated shortly with these (and more) details.
The onos-app shell utility & REST API continues to work as it did before.
Cheers...
Thomas