[SYSTEMDS-1139] Tighten maven integration for python artifact

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: SystemML 0.12
• Component/s: Build
• Assignee: Jon Deron Eriksson
• Reporter: Jon Deron Eriksson
• Created: 02/Dec/16 02:28
• Updated: 02/Mar/17 01:43
• Resolved: 07/Dec/16 01:15

Description

To integrate cleanly with our maven-based build system, the python artifact could use the following enhancements:

1) bind to package phase (in the distribution profile) rather than post-integration-test phase so 'mvn clean package -P distribution' will build the python artifact along with the other distribution artifacts
2) python artifact should end up in target directory so that it is in the expected location for generated maven artifacts
3) since python is being run under src/, clean up temporary files under src/ used to create the artifact (this is preferred to gitignoring them)
4) 'mvn clean' should remove the artifact
5) artifact version number (and name) should ideally be coming from pom.xml file to eliminate the need to manage an additional version number in setup.py
6) update license to include wink and antlr licenses since they are included in the SystemML.jar within the python artifact