Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3103#issuecomment-61821028
Beeline just looks for MANIFEST.MF from the jar it is loaded from, and
print whatever written in `Implementation-Version`. Thus merely adding
implementation fields into the manifest "solves" the Beeline problem.
However, IMO, the Beeline version info problem is not that important. What
are important are two other things:
- SPARK-4225, which breaks master Maven build (fixed in #3105 without
solving the MANIFEST.MF issue)
- Spark assembly jar built by Maven should have a legitimate MANIFEST.MF
(even a merged version? Unfortunately I'm really not an expert on this, tried
several approaches, but none worked out :( )
---
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]
