[
https://issues.apache.org/jira/browse/SPARK-8933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Rosen resolved SPARK-8933.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
Issue resolved by pull request 7374
[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
> Fix For: 1.5.0
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
