Fixing Enso project classpath while updating to IGV 1.20

[JaroslavTulach]

Pull Request Description

Classpath of projects with module-info.java is incorrectly computed and thus we cannot stop on breakpoints in VSCode, NetBeans nor new IGV version 1.20 that was integrated into GraalVM repository. Fixing generator of .enso-source* files, adjusting documentation and functionality.

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  TypeScript,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• Unit tests have been written where possible.

[JaroslavTulach]

There are stop and re-run buttons in the output tab now:

[JaroslavTulach]

89545ef adds tighter integration with IGV:

It checks the properties IGV is using. Obtains the port it listens to and passes that to the JVM executing Enso. If the IGV isn't listening, it asks the user whether listening should be enabled.

[JaroslavTulach]

@Akirathan, @4e6, @hubertp please make sure you upgrade your IGV.

[JaroslavTulach]

@Akirathan, what's the best way to regenerate all .enso-sources* files? Is there a way to compile everything in our sbt based system? Right now I have problems with wrappers like akka-wrapper - Not even clean and compile works for them. At the end I did:

enso$ rm -rf *
enso$ git checkout -f
enso$ sbt
sbt:enso> buildEngineDistribution
sbt:enso> testOnly Nothing
sbt:enso> bench^C

However that's very tedious. Do you think there is a way to invoke all Java compilations only? Moreover just generate the .enso-sources* files, but don't perform any compilation (that might be done with a simple property check in FrgaalJavaCompiler.scala)? E.g. a command to do all Java compilations (main, test, bench, etc.) for all aggregated projects is what I am looking for.

[Akirathan]

akka-wrapper/compile does not do anything on purpose. The "correct" command to compile this project is akka-wrapper/exportedModule. The thing is that it is not possible to change the default behavior of the compile command without breaking everything else in sbt. Therefore, the new command.

But I understand your frustration in the context of this task. Generating .enso-sources* files is currently done in FrgaalJavaCompiler as part of the compile command, but it seems that it is, in fact, independent of the compilation and therefore, can be moved to a completely independent task. If you are interested in this pursuit, please, create an issue for that and assign it to me.

[JaroslavTulach]

I can type sbt:enso> exportedModule - if that is the right command to force compilation even of akka-wrapper.

[Akirathan]

I am not sure that will work. buildEngineDistributionNoIndex works for sure - it invokes exportedModule for all the dependencies that are build into the built-distribution/.../component directory, including all the wrappers.

[JaroslavTulach]

Massive introduction of module-info.java done in #10823 confuses our VSCode & IGV support and breaks debugging. Writing a test to ensure the input property is properly computed and similar regressions are avoided next time.

[JaroslavTulach]

In addition to the test, here is a visual verification. Projects are found and there are no errors among them: