Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/3103#issuecomment-61770853
It's not good to depend on MANIFEST.MF if it's avoidable. I don't
understand the discussion about changing Guava's MANIFEST.MF. Surely that's
irrelevant. Maven does *not* use Guava's MANIFEST.MF in assembly; it does
combine entries from dependency manifests. Are you saying that the combined
MANIFEST.MF includes these fields from Guava, not HiveThriftServer?
Really, the combined MANIFEST.MF should blank these values if anything.
It sounds like we can avoid this mechanism entirely, except for Beeline,
but, does that cause a problem other than logging "???" ?
---
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]
