Generating the external library files

You execute the Automation Decision Services plug-ins to generate the external library files.

Procedure

Open your command-line interface and navigate to the directory that contains the pom.xml file.
Run the mvn install command.
The command runs the import-maven-plugin and the build-maven-plugin.

The import-maven-plugin creates the following directories and files:

A BOM directory that contains the model.b2xa and model.bom files. These files cannot be edited manually. However, you can annotate the model.bom file.
A vocabulary file for each locale that the external library supports. You can annotate the vocabulary files, or manually edit them after moving them to the <referencefolder>/bom directory.
A deployment directory. This directory and the files it contains do not need to be checked or edited.
A resources directory that contains pure function annotations that are deduced from the code.
A reference directory that is empty. You can use this directory to add external annotations and copy a vocabulary file that you would like to edit.

The build-maven-plugin creates the following files:

A deployable JAR that contains the library files. After the JAR file is deployed, the external library is ready to be imported into Decision Designer.
A markdown file that contains the external library documentation. The documentation shows each imported type, along with the verbalization of its constructors, attributes, and methods. The name of this file depends on the local of the external library, for example Complex_en_US.md.

If you are satisfied with the generated external library, you can deploy it and import it into Decision Designer.

Use the mvn clean deploy command to deploy the external library into your archive repository.

If you are not satisfied with the generated files, you can: