Github user rcsenkbeil commented on the pull request:
https://github.com/apache/spark/pull/1929#issuecomment-53369528
Ah, it appears that I run into your issue when I create a class in Scala
and attempt to import. My previous tests had been with Java.
So, when I use code like this:
```
package test
class Test {
def runMe = println("I'm Scala and I was also run!")
}
```
And build a jar in the same manner as previously done with Java, I run into
your issues. I'll investigate this to see if I can figure out what is causing
the difference (or at least what is triggered by running an import before
adding the jar to see if I can duplicate that behavior).
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
