Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6770#issuecomment-111358755
I believe we'd also need to require Maven 3.3 in the build, and in enforcer
plugin? to actually fail if used with a local version that's not high enough?
3.3 is fairly new and most dev environments won't have it. I suppose that's
why `build/mvn` exists too. It may still cause some surprise since most `mvn
...` would fail then.
Not enforcing this risks people hitting the issue that prompted this, I
suppose, without knowing. then again, otherwise, earlier versions of Maven
appear fine.
Hm. What do you guys think about the tradeoffs?
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
