"-Djdeploy.file.limit=8192 --ui" was a single args entry, so the launcher
handed it to main as one unknown argument; LaunchOptions read it as a
subcommand and started headless, printing the usage and exiting with no
window. Each argument now has its own entry.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011xpLSeYKKHX6o16jzYLgZv
Integrates DevToolsFX as a development-time debugging tool bound to F12.
The inspector shows the live node tree, attributes, CSS origins, and
highlights hovered elements—replacing code re-reading with browser-like
inspection. Disabled by default; enabled with --pholio.dev-tools.enabled.
Introduces native installer generation for Windows, macOS, and Linux
using jDeploy. The packaging is driven by package.json and a GitHub
Actions workflow that builds platform-specific bundles with embedded
Azul Zulu FX JRE 26.
Key additions:
- package.json descriptor with jDeploy configuration targeting 7
platforms (excludes windows-arm64 due to missing Azul FX build)
- jdeploy-maven-plugin behind a profile to sync descriptor fields
from POM without requiring Node in default builds
- GitHub workflow triggered by v* tags (versioned releases) or
*-snapshot branches (rolling prereleases)
- Version-free finalName (pholio.jar) so jar path stays stable
- Launcher reads package-info.json from jdeploy tag for auto-update
The spring-boot-maven-plugin's mainClass is the single source of
truth for the entry point: it lands in the repackaged jar's manifest
as Start-Class, which jDeploy's native launcher uses to bootstrap.
chris.gitea
