[
https://issues.apache.org/jira/browse/SPARK-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993407#comment-13993407
]
Guoqiang Li edited comment on SPARK-1776 at 5/9/14 5:39 AM:
------------------------------------------------------------
Even so, there are many maintenance costs.We should not use two build tools at
the same time, only use maven is better
was (Author: gq):
But I would think only use maven is better
> Have Spark's SBT build read dependencies from Maven
> ---------------------------------------------------
>
> Key: SPARK-1776
> URL: https://issues.apache.org/jira/browse/SPARK-1776
> Project: Spark
> Issue Type: New Feature
> Components: Build
> Reporter: Patrick Wendell
> Assignee: Prashant Sharma
> Fix For: 1.1.0
>
>
> We've wanted to consolidate Spark's build for a while see
> [here|http://mail-archives.apache.org/mod_mbox/spark-dev/201307.mbox/%[email protected]%3E]
> and
> [here|http://apache-spark-developers-list.1001551.n3.nabble.com/DISCUSS-Necessity-of-Maven-and-SBT-Build-in-Spark-td2315.html].
> I'd like to propose using the sbt-pom-reader plug-in to allow us to keep our
> sbt build (for ease of development) while also holding onto our Maven build
> which almost all downstream packagers use.
> I've prototyped this a bit locally and I think it's do-able, but will require
> making some contributions to the sbt-pom-reader plugin. Josh Suereth who
> maintains both sbt and the plug-in has agreed to help merge any patches we
> need for this.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
