[ https://issues.apache.org/jira/browse/SPARK-14867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun updated SPARK-14867: ---------------------------------- Priority: Major (was: Trivial) Description: Currently, `build/mvn` provides a convenient option, `--force`, in order to use the recommended version of maven without changing PATH environment variable. However, there were two problems. - `dev/lint-java` does not use the newly installed maven. - It's not easy to type `--force` option always. If we use '--force' option once, we had better prefer the Spark recommended maven. This issue makes `build/mvn` check the existence of maven installed by `--force` option first. -------- According to [~srowen]'s comment, now this issue aims to remove `--force` option by auto-detection of maven version. was: Currently, `build/mvn` provides a convenient option, `--force`, in order to use the recommended version of maven without changing PATH environment variable. However, there were two problems. - `dev/lint-java` does not use the newly installed maven. - It's not easy to type `--force` option always. If we use '--force' option once, we had better prefer the Spark recommended maven. This issue makes `build/mvn` check the existence of maven installed by `--force` option first. Summary: Remove `--force` option in `build/mvn`. (was: Make `build/mvn` to use the downloaded maven if it exist.) > Remove `--force` option in `build/mvn`. > --------------------------------------- > > Key: SPARK-14867 > URL: https://issues.apache.org/jira/browse/SPARK-14867 > Project: Spark > Issue Type: Improvement > Components: Build > Reporter: Dongjoon Hyun > > Currently, `build/mvn` provides a convenient option, `--force`, in order to > use the recommended version of maven without changing PATH environment > variable. > However, there were two problems. > - `dev/lint-java` does not use the newly installed maven. > - It's not easy to type `--force` option always. > If we use '--force' option once, we had better prefer the Spark recommended > maven. > This issue makes `build/mvn` check the existence of maven installed by > `--force` option first. > -------- > According to [~srowen]'s comment, now this issue aims to remove `--force` > option by auto-detection of maven version. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org