Configuring project libraries¶
A model library or library in a Modelio 3 project is a set of non-modifiable model elements that is required for the development of your project, packaged in a single artefact.
A very basic example for Java projects is the JDK. In order to properly model a Java application, many classes from the JDK are used either for extension by inheritance or as parts in the compositions and associations of your model. These required JDK classes are brought into your project via a model library. Obviously, your intention is not to edit or modify the JDK model, which is why the models provided by libraries are read-only.
There are two kinds of libraries in Modelio 3:
- Model Component libraries which are local libraries similar to the former model components of Modelio 2
- HTTP Libraries which are remote libraries, accessible via HTTP and consequently distributed
You can declare as many additional libraries in your project as required, mixing local and remote ones.
Library management is carried out in the Libraries tab of the Project configurator dialog.
Configuring project libraries¶
- Click on “Configuration\Libraries…” or on the  icon then select the ‘Libraries’ tab.
- You can add local libraries to your project, or update, consult or remove existing ones.
- You can add remote libraries to your project, or refresh, consult or remove existing ones.
Adding model components¶
Model components are deployed by users who want to use them in their own projects. When a model component has been deployed in a project, it and the model elements it contains appear in the “Model” view in blue, and are in read- only mode.
To deploy a model component, carry out the steps shown in the screenshots below.
Deploying a model component¶
- Select the model component (*.ramc file) you wish to add to your project.
- Not all mandatory modules have been installed in the project in which you want to deploy the model component. If the model component you want to deploy includes note and tagged value types specific to a given module, then this module must be installed in your project before you deploy the model component. To solve this problem, simply run the “Configuration/Modules” command, and install the module you need.
- A dependency that exists between the model component you want to deploy and another model component which must be deployed first in a project has not been respected. To solve this problem, simply first deploy the other model component (indicated in the “Dependencies” field) in your project, in the exact version stated, and then run the deployment operation for the model component you want to deploy again.
For further information on local libraries (model components), please see “Introducing model components”.
Adding remote libraries¶
Remote libraries are deployed by users wishing to use them in their own projects. When a remote library has been deployed in a project, it and the model elements it contains appear in the “Model” view in blue, and are in read- only mode.
To deploy a remote library, carry out the steps shown in the screenshots below.
Deploy a remote library¶
- Enter the name that will be used for the remote library in the model explorer.
- Enter the remote library URL.
- If necessary, enter the user and password.
- You can check the remote library URL.
For further information on remote libraries (HTTP models), please see “Introducing remote libraries”.