Releases: Col-E/Recaf-Launcher
Releases · Col-E/Recaf-Launcher
0.5.3 - Logs written to Recaf directory
No other changes, just moving the relative path output to the Recaf/launcher
directory.
0.5.2 - Update target branch for snapshots
No changes from 0.5.1
other than changing the CI snapshot branch target from dev4
to master
now that the main branch has been updated.
0.5.1 - Linux improvements
What's Changed
- Replace Swing JDK chooser with native dialog by @1fexd in #21
- Support following sym-links in Java install selections
- Add a few common paths to scan for installations on Linux
/usr/lib/jvm/*
~/.jdks/*
/etc/alternatives/java
0.5.0 - Splitting the CLI/GUI
This release mainly separates the download option into two. You now can download the CLI and GUI clients individually instead of the behavior of both being bundled into one (and causing problems / confusion).
Additionally a number of bugs and improvements have been made to the actual launcher behavior, and the GUI.
- You can now pick which JVM to launch Recaf with - #14
- JavaFX would fail to download if the latest version was a round number and not a semantic version
0.4.1
Fix JFX not being included in the new JVM's classpath when running Recaf
0.4.0
- Updated instructions / warning messages now that Recaf uses JDK 22 instead of JDK 17
- When running from a JDK that bundles JavaFX the launcher will only ever use that version of JavaFX and not attempt to download a local copy
0.3.0
Add headless flag -x
/--headless
for use when running launcher via javaw
and the GUI is not desired.
0.2.0
Allows specifying a default action to be used when running the launcher via java
. Using javaw
will only ever open the GUI.
Also prevents downloading too new versions of JavaFX that are not compatible with the current Java version.
0.1.4
Fixed some wrong up-to-date checks, moved work off the UI thread when using GUI launcher.
0.1.3
Now includes a basic GUI if you don't want to use it as a CLI