You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you follow the new docs on calling Frege from Java (and you should, because the old one won't work anymore with new Frege code), you need 3.24-7.xx (or 3.24.xx, but then java8 is required), and the patch number xx is supposed to be immaterial unless you need a certain patch.
I have no good explanation for the NoSuchMethodError , as a method with that signature actually does exist. Maybe you can share some code so we can find out what is going on here.
The frege distribution that I currently push to Maven Central has OSGi exports in the manifest ( would be good to get them as part of the standard build/release, and fix that whole process ) and this example project gives an activator that calls Frege etc.
I also made a very short video about this a number of years ago:
Hi
[Wait - I should have read the new docs on calling Frege from Java -sorry - hold this issue!]
My OSGi Frege application needs a dependency on the Frege runtime but without opening a workbench.
Obviously I can't depend on frege-ide because this depends on a full Eclipse workbench being started.
Frege 3.23.422-ga05a487 from Maven doesn't have run7, so I get a noclassfounderror: frege/run7/Lazy
Frege 3.24.7-30 from Maven has run7, but this is too new and I get a
java.lang.NoSuchMethodError: frege.run7.Thunk.shared(Lfrege/run7/Lazy;)Lfrege/run7/Lazy;
Is there a correct runtime jar of the same version within regec.jar but without workbench activation available somewhere?
Robert
The text was updated successfully, but these errors were encountered: