Closed devkhan closed 8 years ago
This is most likely caused by either a wrong entry in the Manifest file or the class is missing in the JAR. Interstingly, this did work before (there is a downloadable version of EscherConverter). How did you build the JAR?
I'm using the maven assembly plugin, and there have been no changes in its configuration since the start.
I went through the old commits, building them one by one, see when it stopped working, and I found out that it was when you add the reconfigured the libs here. Maybe there is some problem with the pom files, I'm not really sure. Can you check?
It is not evident to me what exactly happened in that commit.
This is almost solved now with the latest commit. There is now just one problem that needs to be solved, namely it doesn't find one resource file, but the POM builds an executable Jar.
Solved in fc8a5031775af926c00774b776f94b466d03e44a
If you stumble across this issue years later like I do, remember to build the JAR using
mvn clean compile assembly:single
If I run the
EscherConverter.main(String...)
from the IDE or command-line(like in Travis), everything works fine. But if I try to run the exported runnable JAR, it throws:I don't what's causing this, but this is a big problem as it will be released as a JAR, so it needs to be resolved. @draeger Can you look into what might be causing this? The manifest is also correct.