Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/1402#issuecomment-48877650
It's set that way just because it is only used by Hadoop's FileSystem to
access S3. Code shouldn't call it directly. Maven should therefore include it
in the runtime classpath and assembled jars, but not the compile classpath.
I seem to distantly recall that sbt doesn't quite do this. I hope there is
an equivalent for sbt as that's the right thing to do. It's not the end of the
world to make jets3t appear on the compile classpath.
(So I assume the sbt assembly still has to be supported? the Maven one
should be OK in this regard)
---
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.
---
