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
Since apparently no one feels responsible anymore for putting recent frege releases to Maven, and since this is also apparently not possible or desirable to do in an automated fashion, I propose the following for frege-repl and frege-interpreter alike:
Let gradlew check some relative path (i.e. lib/frege3.24-latest.jar) for a frege jar to work with, and fetch it from github if not present. It'd certainly be best to use the same one in the repl as in the interpreter, of course.
This way, we would not have to rely on Maven. There could be one and only one place where the jar to download would be specified. (This would be documented in the README.md, of course.) And people needing a most recent frege jar or even one that is just in development could use the repl with that one as well.
The text was updated successfully, but these errors were encountered:
Since apparently no one feels responsible anymore for putting recent frege releases to Maven, and since this is also apparently not possible or desirable to do in an automated fashion, I propose the following for frege-repl and frege-interpreter alike:
Let gradlew check some relative path (i.e. lib/frege3.24-latest.jar) for a frege jar to work with, and fetch it from github if not present. It'd certainly be best to use the same one in the repl as in the interpreter, of course.
This way, we would not have to rely on Maven. There could be one and only one place where the jar to download would be specified. (This would be documented in the README.md, of course.) And people needing a most recent frege jar or even one that is just in development could use the repl with that one as well.
The text was updated successfully, but these errors were encountered: