-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Class issues when using aut-0.17.0-fatjar.jar #313
Comments
@ruebot, what was the build environment where the 0.17.0 release was performed? I checked out the 0.17.0 release branch, built it, and ran the same test, and did not receive an error. However, I do receive the error when using the released fatjar. I think the problem is that the wrong SLF4J binding is being included in the fatjar. See this issue, and this background. It's not clear to me why I can't replicate the error when I build 0.17.0, though. Side issue: I think we can drop |
@jrwiebe it would have been my laptop or desktop; Ubuntu 18.04, and OpenJDK 8 probably. Yeah, the SLF4J binding makes since. It came up for me this morning in a quick cursory google. ...good catch on cobertura. That pom haunts me sometimes 😄 |
Helping out a team here at the datathon. This worked, so maybe we're fine on master?
|
As I mentioned yesterday, when I built the 0.17.0 release I also had no problem. I tried this with OpenJDK 8 under Linux (Ubuntu 18.04 and OS X) and with Oracle JDK 8 (just OS X). |
Describe the bug
java.lang.NoClassDefFoundError
andjava.lang.NoClassDefFoundError
errors are produced when usingaut-0.17.0-fatjar.jar
. Looks like a potential class conflict in the fatjar, but not when the using--packages
.To Reproduce
spark-shell --jars /home/nruest/Downloads/aut-0.17.0-fatjar.jar
RecordLoader.loadArchives
:Expected behavior
Well, this shouldn't happen. It should work.
Environment information
--jars
spark-shell --jars /home/nruest/Downloads/aut-0.17.0-fatjar.jar
Additional context
@edsu notes in Slack that the
0.16.0
fatjar works.The text was updated successfully, but these errors were encountered: