The .classpath files that are part of Streams Studio projects, contain absolute paths to JAR files in $STREAMS_INSTALL/lib and $STREAMS_INSTALL/ext/lib. Find a solution to get rid of the already expanded (to /home/xxx/InfoSphere_Streams/4.2.0.0/) environment variables.
In other projects, the required JAR files are copied to the project, for example, opt folder. From my point of view, this is a bad solution because it requires to update the JAR files for each release. Instead, I would prefer that we have some preparation script that must be called before the projects are opened in Streams Studio.
The preparation script could create soft links (ln -s) or copy the files from $STREAMS_INSTALL.
This task is related to issue #3. The build environment that is used from command line, is probably using the direct paths using $STREAMS_INSTALL.
The .classpath files that are part of Streams Studio projects, contain absolute paths to JAR files in
$STREAMS_INSTALL/liband$STREAMS_INSTALL/ext/lib. Find a solution to get rid of the already expanded (to/home/xxx/InfoSphere_Streams/4.2.0.0/) environment variables.In other projects, the required JAR files are copied to the project, for example,
optfolder. From my point of view, this is a bad solution because it requires to update the JAR files for each release. Instead, I would prefer that we have some preparation script that must be called before the projects are opened in Streams Studio.The preparation script could create soft links (
ln -s) or copy the files from$STREAMS_INSTALL.This task is related to issue #3. The build environment that is used from command line, is probably using the direct paths using
$STREAMS_INSTALL.