Releases: Periteleios/rascal-intellij-debugger-releases
Releases · Periteleios/rascal-intellij-debugger-releases
Release list
v0.1.5
Fixed the Rascal REPL launch command being silently truncated by a PTY line-length limit on projects with large classpaths (missed the debug port and language server entirely, with no error shown anywhere) -- now passed via a Java argument file instead.
v0.1.4
- Fixed the debug REPL and language server launching Rascal's own jars
via a barejavaresolved by whatever's first on the shell's/IDE
process's PATH, which could be an unrelated, much older JDK.
Now uses IntelliJ's own bundled runtime (guaranteed modern enough)
via an absolute path instead. - Hardened lsof invocation (macOS debug-port discovery) the same way
as the earlier mvn fix, pre-resolving its absolute path.
v0.1.3
- Fixed mvn resolution on macOS: 0.1.2's environment-map fix wasn't
sufficient on its own (a bare command name is resolved against the
launching IDE process's own PATH, not the child's configured
environment). Now pre-resolves the absolute path tomvninstead.
v0.1.2
- Fixed classpath computation (used by both the language server and the
debug REPL launcher) failing to findmvnwhen IntelliJ is launched
as a GUI app on macOS (as opposed to from a terminal), which inherits
a minimal PATH missing wherever Homebrew/SDKMAN installed Maven. Now
populates the subprocess environment from the user's real login shell.
v0.1.1
- Fixed the plugin's own build: it was silently compiled to Java 25
bytecode regardless of declared compatibility, breaking on any IDE
whose own boot JDK was older (e.g. 21). Now correctly targets Java 17. - Fixed the bundled TextMate grammar's
modulerule, which was
unreachable (shadowed by a generic keyword match) and, once reachable,
gave real Rascal module bodies no token boundaries -- could manifest
as an entire file appearing to select/underline as one token. - Added macOS support for automatic debug-port discovery (previously
Linux-only, via /proc; now useslsofon macOS).
Initial Release
Add updatePlugins.xml manifest and README for v0.1.0 Points at the v0.1.0 release asset that needs to be published on GitHub (tag v0.1.0, zip attached) to make this manifest actually resolve -- see README for the release steps.