You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/07/13 17:44:04 UTC

[jira] [Commented] (SPARK-8933) Provide a --force flag to build/mvn that always uses downloaded maven

    [ https://issues.apache.org/jira/browse/SPARK-8933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624816#comment-14624816 ] 

Apache Spark commented on SPARK-8933:
-------------------------------------

User 'brennonyork' has created a pull request for this issue:
https://github.com/apache/spark/pull/7374

> Provide a --force flag to build/mvn that always uses downloaded maven
> ---------------------------------------------------------------------
>
>                 Key: SPARK-8933
>                 URL: https://issues.apache.org/jira/browse/SPARK-8933
>             Project: Spark
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Patrick Wendell
>            Assignee: Brennon York
>
> I noticed the other day that build/mvn will still use the system maven if "mvn" binary is installed. I think this was intentional to support just using zinc and using the system maven (and to match the semantics of sbt/sbt). It would be nice to have a flag that will force it to use the downloaded maven. I was thinking it could have a --force flag, and then it could swallow that flag and not pass it onto maven.
> This is useful in some cases like our test runners, where we want to coerce a specific version of maven is used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org