Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6770#issuecomment-111559470
Heh, well we have this problem right now:
https://github.com/apache/spark/pull/6492
The reason it's popped up is that Hadoop 1 is now controlled by a profile,
and profile handling behavior is at issue here.
Of course if we didn't support Hadoop 1, this would go away. (See what I
did there?)
Nah, it's really nothing to do with Hadoop 1 per se, but profile handling,
but I do wonder if this would eventually bite again anyway for a different
profile.
I think the only reasonable way forward on this one right now is to, yes,
download and use the latest Maven when that is requested, but not actually fail
the build if 3.3 isn't used. This does mean that someone with 3.2 on their
machine can run into https://github.com/apache/spark/pull/6492, but hey, that
only affects people building for Hadoop 1. Maybe close enough for now.
---
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]
