uAAL Pax Runner - universAAL/tools.eclipse-plugins GitHub Wiki

Like the Pax Runner Tool this tools also uses the Pax Runner specifications and runtime to start an OSGi application. But in opposite to the other tool this one is more suited to the special needs of universAAL (this is why we call it uAAL Pax Runner) and also be able to automatically create run-configurations for given projects from the workspace.

To create a start-configuration for universAAL you need to use the according menu entry in the universAAL main-menu like shown below:

If you are not using the menu entry some parameters (mainly the program arguments) will not given to the configuration and it can not be ensured that universAAL will start without trouble. In the following dialogue you can give an arbitrary name that is not already given to an other configuration (you not necessary need to select a project here) and continue. Now the new configuration is being created and you should see something like given in the following figure:

At the top you can select to middleware version that you are going to use in your project, but you can also let detect this automatically. In the Features box we will in future provide special attachments for the runtime like the inclusion of the UI-Bus, CHE and so on. In the Workspace Projects box at the left are all projects from the workspace included. Using the buttons in the middle you can add them to the start-configuration or remove them. If you are adding a project the Runner automatically try to detect the used middleware version if it is not already given and warn you if there you are mixing different one. For every added projects the needed bundles are automatically added to the Additional Libraries box at the bottom. This can for example have a look like this:

Here you can see that some bundles are gray. These are needed to run universAAL and therefore can not be removed are changed. Beside of this the Additional Libraries box is more or less what you already know from the original Pax Runner Tool. You can sort the list either alphabetically or by level. The level-numbers should be determined automatically. The basic assumptions for all if this is that you need to have included all bundles that are needed during run-time in at least one Maven dependency (direct or indirect).

There are many cases to be covered like mixed versions of middleware bundles, indirect dependencies, the wrap-parameter for non-bundles and so on. We tried to cover as much as we found and had have resources, but there may be many new issues when starting applications we never thought about. To read existing configurations may be a problem and we suggest to first have a try creating a new one. Also using composites may lead to trouble even if we tried to include as good as possible (up to now). So if applications do not running with a manual effort in the Additional Libraries box, there is trouble in changing the middleware version or anything else please report us!