Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9503#issuecomment-155344851
I found this Manifest class-path issue to be extremely puzzling, but it
looks like other people have hit it as well:
https://dzone.com/articles/jar-manifest-class-path-is-not-for-java-applicatio
Quote:
> A JAR with a Class-Path manifest header will make those classpath entries
available to the Java classloader regardless of whether that JAR is executed
with java -jar ... or is simply placed on the classpath of a larger Java
application.
This puzzling behavior is described a bit more explicitly in [Java 8's JAR
specification](https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath).
---
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]
