frankfliu opened a new pull request #13626: Re-organize Scala maven build
URL: https://github.com/apache/incubator-mxnet/pull/13626
 
 
   This is a follow up of: https://issues.apache.org/jira/browse/MXNET-1224
   A design was posted: 
https://cwiki.apache.org/confluence/display/MXNET/Scala+maven+build+improvement
   
   1. Automatically detect which platform to build for scala.
   2. Remove platform dependend submodules
   3. Fix cyclic module dependencies
   4. Fix scalatype style check
   5. Now mvn can be executed in submodule
   6. Maven build can be executed from any directory not only in root project
   7. Checkin javah header file, and use verify task to detect native API 
changes
   8. Improve incremental build performance
   9. Remove unittest and integration-test profile, use proper task instead
   10. Delete generated scala file during maven clean.
   
   ## Checklist ##
   ### Essentials ###
   Please feel free to remove inapplicable items for your PR.
   - [X] Changes are complete (i.e. I finished coding on this PR)
   - [X] All changes have test coverage:
   - Unit tests are added for small changes to verify correctness (e.g. adding 
a new operator)
   - Nightly tests are added for complicated/long-running ones (e.g. changing 
distributed kvstore)
   - Build tests will be added for build configuration changes (e.g. adding a 
new build option with NCCL)
   - [X] Code is well-documented: 
   - For user-facing API changes, API doc string has been updated. 
   - For new C++ functions in header files, their functionalities and arguments 
are documented. 
   - For new examples, README.md is added to explain the what the example does, 
the source of the dataset, expected performance on test set and reference to 
the original paper if applicable
   - Check the API doc at 
http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
   - [X] To the my best knowledge, examples are either not affected by this 
change, or have been fixed to be compatible with this change
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to