This commit adds support for the frege intellij plugin by
exposing the frege compiler jar as a dependency, so the plugin can
recognize the standard library.
adding the name 'fregeRun' as that is used by the plugin to run files
add support for overriding the main module executed by runFrege so
that arbitary files can be run by the plugin
output frege compilation output into the java compilation output
I'm reopening this PR, since it's now been rebased and i dont know how to switch HEAD branches in github.
As to why this PR is neccessary / addressing some of the questions asked in the last PR:
The intellij-frege plugin (https://github.com/IntelliJ-Frege/intellij-frege) uses a build.gradle that contains all the download+build+repl+etc code, and ive been using this plugin as a substitute for that. However, this plugin and the generated build.gradle have a few differences (mainly: fregeRun vs runFrege, and specifying the project property class_name to run a specific module when using the green run arrow), so i added those two changes to the runFrege task.
In addition to that i make both the frege jar and frege dependencies available on the java classpath, since that way they are per default included in the application plugin / shadow jar plugin and that way they are also indexed by intellij.
To that end, i also make the classes task depend on compileFrege so that frege compilation output is captured in the project jar.
This commit adds support for the frege intellij plugin by
output frege compilation output into the java compilation output
I'm reopening this PR, since it's now been rebased and i dont know how to switch HEAD branches in github.
As to why this PR is neccessary / addressing some of the questions asked in the last PR:
The intellij-frege plugin (https://github.com/IntelliJ-Frege/intellij-frege) uses a build.gradle that contains all the download+build+repl+etc code, and ive been using this plugin as a substitute for that. However, this plugin and the generated build.gradle have a few differences (mainly:
fregeRunvsrunFrege, and specifying the project propertyclass_nameto run a specific module when using the green run arrow), so i added those two changes to therunFregetask.In addition to that i make both the frege jar and frege dependencies available on the java classpath, since that way they are per default included in the application plugin / shadow jar plugin and that way they are also indexed by intellij.
To that end, i also make the classes task depend on compileFrege so that frege compilation output is captured in the project jar.