[SYSTEMDS-466] bin/systemml vs runStandaloneSystemML

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Abandoned
• Fix Version/s: SystemDS 2.0
• Assignee: Unassigned
• Reporter: Jon Deron Eriksson
• Created: 15/Jan/16 19:11
• Updated: 25/Sep/20 11:13
• Resolved: 25/Sep/20 11:13

Description

Currently standalone mode can be run via (1) the older ./runStandaloneSystemML.sh and .runStandaloneSystemML.bat, and (2) the newer ./bin/systemml and ./bin/systemml.bat.

Probably should move to the newer way of execution and remove the older way to avoid confusion.

However some updates need to be made to bin/systemml and bin/systemml.bat to allow this to happen. For example, the current SYSTEM_ML_JAR=\"${BUILD_DIR}/classes\" requires building the project to generate the classes for the classes directory. This should probably be replaced by the commented #SYSTEM_ML_JAR=$( find $PROJECT_ROOT_DIR/target/system-ml-*-SNAPSHOT.jar ).

In addition, the distributions need to include the bin/systemml* scripts. Currently the standalone zip and tar.gz include the runStandaloneSystemML* scripts but not the bin/systemml* scripts.

Further, documentation will need to be updated since currently it mentions both methods (README mentions bin/systemml and other docs mention runStandaloneSystemML*). This is probably good as a separate task.

Issue Links

• Is contained by: SYSTEMDS-1245 Improve release distribution consumability
• is related to: SYSTEMDS-469 bin/systemml vs sparkDML.sh