Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9532#issuecomment-180977355
Yeah, this is what I saw too. It's not a problem with the build of the code
itself, since as you say it passes locally. It's a problem that occurs when
MiMa builds previous code to evaluate API differences. I didn't quite
understand the fix. Your change is a clue; it may relate to Maven's
closest-first dependency rules.
In that case, I suspect the right place to add the explicit dependency is
in `sql`, not `core`. That's where it used so technically this must be declared.
In any event you don't need to repeat the version, and in fact should not.
---
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]
