Closed Inventitech closed 6 years ago
Reading through StackOverflow gave me the following two answers: https://stackoverflow.com/questions/26102649/java-lang-linkageerror-while-using-jgit-and-jsch-for-eclipse-plugin-development and https://stackoverflow.com/questions/2631472/linkageerror-thrown-when-attempting-to-pass-instance-of-class-between-2-eclipse
I have not changed any configuration in the MANIFEST.mf, so it is weird the error is now occuring. Still, trying to remove the double inclusion of the jcommon
dependency in both watchdog.core
and watchdog.eclipse.plugin
should probably fix this issue. Continuing my investigation...
Okay, second thought: maybe we should switch our dependencies over to a p2 repository. That way we can use the regular import-package
and target-platform
, rather than the "anti-pattern" of jar inclusion in the repository. This would thus require us to host our own version of the p2 repository on https://p2repository.testroots.org, which I am not sure if we want to do.
I think this second option is the better solution, but requires significant more work. Therefore I am going to try out the option in my previous comment first.
In a new project (even with read and write intervals), the WatchDogView is broken. We cannot release until this is fixed.
Stacktrace: