[
https://issues.apache.org/jira/browse/MAHOUT-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239770#comment-16239770
]
ASF GitHub Bot commented on MAHOUT-1999:
----------------------------------------
GitHub user rawkintrevo opened a pull request:
https://github.com/apache/mahout/pull/350
[WIP] MAHOUT-1999 Multi artifact build
### Purpose of PR:
Build multiple binaries of spark in one maven shot.
The issues surrounding SBT wrt MAHOUT-2020 continue, however the produced
artifacts work fine for maven builds, as well as console/Zeppelin integrations.
In short- the distribution module executes `mvn package` twice more, with
Scala-2.11/SPark-2.0 and Scala-2.11/SPark-2.1 switches.
**WHy is this WIP?** We need a way to prevent it from happening on every
run. Imho, the distribution module should be disabled for 'automatically'
running. Docs will need to be updated accordingly.
### Important ToDos
Please mark each with an "x"
- [x] A JIRA ticket exists (if not, please create this
first)[https://issues.apache.org/jira/browse/ZEPPELIN/]
- [x] Title of PR is "MAHOUT-XXXX Brief Description of Changes" where XXXX
is the JIRA number.
- [x] Created unit tests where appropriate
- [x] Added licenses correct on newly added files
- [x] Assigned JIRA to self
- [ ] Added documentation in scala docs/java docs, and to website
- [x] Successfully built and ran all unit tests, verified that all tests
pass locally.
If all of these things aren't complete, but you still feel it is
appropriate to open a PR, please add [WIP] after MAHOUT-XXXX before the
descriptions- e.g. "MAHOUT-XXXX [WIP] Description of Change"
Does this change break earlier versions?
Is this the beginning of a larger project for which a feature branch should
be made?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rawkintrevo/mahout mahout-1999-b
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/mahout/pull/350.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #350
----
commit d4eb83acba2022e9fb21ec6d1ded1d2e3e05ea25
Author: Trevor a.k.a @rawkintrevo <[email protected]>
Date: 2017-11-05T23:38:40Z
MAHOUT-1999 Multi artifact build
----
> Automate Release Process with Build Script
> ------------------------------------------
>
> Key: MAHOUT-1999
> URL: https://issues.apache.org/jira/browse/MAHOUT-1999
> Project: Mahout
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.13.2
> Reporter: Trevor Grant
> Assignee: Trevor Grant
>
> With the proliferation of binaries across multiple Scala / Spark versions- a
> release script should be implemented to support multiple builds.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
