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 build have two choices:
#1, Apply this patch allowing v1.6.2 to be build as previous
#2, Apply PR #14066 bumping maven to 3.3.9 (btw this PR misses updating the
pom.xml
The purist in me thinks #1 is the correct approach, but I'll defer to
general wisdom
@srowen thoughts ?
---
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
