Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14543
This is already in `branch-1.6`:
https://github.com/apache/spark/blob/branch-1.6/build/mvn
We can't change releases/tags of course. Yeah, this is because non-current
versions eventually get moved
Github user rickalm commented on the issue:
https://github.com/apache/spark/pull/14543
Was considering withdrawing the PR. Here are my thoughts
Tag v1.6.2 specifies mvn 3.3.3 (unless user intentionally overrides). Users
who previously built wanting to replicate their previous
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14543
Can one of the admins verify this patch?
---
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 feat
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/14543
cc @srowen for build update
---
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 wis
