IBM Streams 4.3.0

Build process

In IBM® Streams, by default the build process allows users to write and build toolkits without having to manually manage the toolkit dependencies.

This behavior has the following implications:

All toolkit projects open in Streams Studio are considered to be implicitly dependent upon each other.
All toolkit projects are also implicitly dependent on toolkits added to Streams Explorer.
In the SPL Graphical Editor palette, you can use artifacts from all implicitly dependent toolkits.
Content assist in both the SPL Editor and the Properties view lists artifacts from all implicitly dependent toolkits.
The project's dependencies do not need to be stored in the info.xml file.
The build process uses dependencies that are listed in the info.xml as an aid in determining the correct version of the toolkit to use as an implicit dependency.
The build process adds all possible toolkit dependencies to the compiler's include path (-t option). The compiler determines which toolkits are needed to complete the build.

Restriction: Multiple toolkit projects cannot define artifacts that have the same name within the same namespace. Otherwise, the build process fails.

Tip: Close toolkit projects that are not being used to prevent build errors due to name conflicts. Use different Eclipse workspaces to separate unrelated toolkit projects.

Using a specific toolkit version

This build process provides the user the ability to maintain multiple versions of the same toolkit in the workspace. The projects that do not have any dependencies that are listed in the info.xml file automatically become dependent on the highest version of each toolkit in the workspace. If a project requires a specific toolkit version, that toolkit can be explicitly defined in the info.xml file that is found in the project. The build process calculates the dependencies using the toolkit version that is found in the info.xml file.

Changing the default build process

If you are working with a toolkit that requires a specific set of dependencies, the build process can be changed to add only toolkits that are defined in the info.xml file to the compiler's toolkit include path. Working with this alternative build process has the following implications:

You need to ensure that the info.xml file contains an updated list of dependencies.
You can use the artifacts from toolkits that are not explicitly defined by using the SPL Graphical Editor palette and content assist.
You must manually update the info.xml file with the necessary toolkit dependencies or the build might fail.

To change the build process:

In Streams Studio, navigate to Window > Preferences.
Within the navigation tree, expand IBM Streams and select SPL Build.
Within the SPL Build area, change the Toolkit lookup path(s) option to either Include all toolkits or Include direct/indirect toolkits only.