Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/6770#issuecomment-111562931
Is it an inconvenience if we just always download and use Maven, instead of
checking for a local install first? We already do that for Zinc and Scala, so I
don't see that we need to ever fail the build for using an out of date version
of Maven.
As long as we always download our own version of Maven, then the only time
a developer might still use an out-of-date version is if they already
downloaded one using `build/mvn` before we make this update. Not a big deal as
they can just delete the one downloaded to `build/` and rerun `build/mvn`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
