Anthony Stirling
6e1a7454ca
This is a bring-up branch to validate JPDFium consumption across all Stirling-PDF release targets (server jar, Docker, Tauri desktop). Open as PR for cross-platform CI validation. Source dep - com.stirling:jpdfium:1.0.0-SNAPSHOT (pulled from Maven Central snapshots, fully anonymous — no PAT or GitHub Packages auth needed) - Per-platform natives: linux-x64, linux-arm64, darwin-arm64, windows-x64 All four are added as runtimeOnly so the bootJar carries every platform and NativeLoader picks the right one at startup. The natives jars are hermetic — each bundles its bridge, PDFium component libs, and the third-party deps (pcre2/freetype/harfbuzz/icu/qpdf/pugixml/libunibreak), so no system package install is required at runtime. - TODO follow-up: jpdfium-natives-darwin-x64 (Intel Mac) — dropped from the upstream publish matrix while cross-compile-on-macos-14 setup lands. JDK 25 enforcement - Bump root + subprojects from sourceCompatibility / targetCompatibility 21 -> 25. JPDFium publishes with org.gradle.jvm.version=25 (FFM is final in JDK 22+; JPDFium picks 25 as the floor), and a 21-targeted Stirling-PDF jar would fail Gradle's variant attribute match at compile time. - bootRun jvmArgs: add --enable-native-access=ALL-UNNAMED. JDK 25 warns on restricted FFM methods without it; JDK 26 will hard-fail. Docker - scripts/init-without-ocr.sh: prepend --enable-native-access=ALL-UNNAMED to JAVA_BASE_OPTS so the JAVA_TOOL_OPTIONS env var that the container sets includes it for the running JVM. Idempotent — won't duplicate if already present. Tauri - frontend/src-tauri/src/commands/backend.rs: the sidecar Java spawn now passes --enable-native-access=ALL-UNNAMED. The bundled jlink JRE's module list (desktop.yml JLINK_MODULES) already includes java.desktop and java.net.http which is everything JPDFium's module-info requires. Smoke test - app/common/src/test/java/stirling/software/common/jpdfium/JPDFiumSmokeTest.java Opens the existing common test resource example.pdf via PdfDocument.open and asserts a positive page count. Confirms the dep resolves, the right natives jar lands on the classpath, the bridge + PDFium component libs + third-party deps all load, and the FFM bindings parse a real PDF end-to-end. Runs as part of :common:test on each platform's CI runner.
Frontend
All frontend commands are run from the repository root using Task:
task frontend:dev— start Vite dev server (localhost:5173)task frontend:build— production buildtask frontend:test— run teststask frontend:test:watch— run tests in watch modetask frontend:lint— run ESLint + cycle detectiontask frontend:typecheck— run TypeScript type checkingtask frontend:check— run typecheck + lint + testtask frontend:install— install npm dependencies
For desktop app development, see the Tauri section below.
Environment Variables
Environment variables live in committed .env files at the frontend root:
.env— used by all builds (core, proprietary, and as the base for desktop/SaaS).env.desktop— additional vars loaded in desktop (Tauri) mode.env.saas— additional vars loaded in SaaS mode
These files contain non-secret defaults and are checked into Git, so most dev work needs no further setup.
To override values locally (API keys, machine-specific settings), create an uncommitted sibling .env.local / .env.desktop.local / .env.saas.local. Vite automatically layers these on top of the committed files.
Docker Setup
For Docker deployments and configuration, see the Docker README.
Tauri
All desktop tasks are available via Task. From the root of the repo:
Dev
task desktop:dev
This ensures the JLink runtime and backend JAR exist (skipping if already built), then starts Tauri in dev mode.
Build
task desktop:build
This does a full clean rebuild of the backend JAR and JLink runtime, then builds the Tauri app for production.
Platform-specific dev builds are also available:
task desktop:build:dev # No bundling
task desktop:build:dev:mac # macOS .app bundle
task desktop:build:dev:windows # Windows NSIS installer
task desktop:build:dev:linux # Linux AppImage
JLink Tasks
You can also run JLink steps individually:
task desktop:jlink # Build JAR + create JLink runtime
task desktop:jlink:jar # Build backend JAR only
task desktop:jlink:runtime # Create JLink custom JRE only
task desktop:jlink:clean # Remove JLink artifacts
Clean
task desktop:clean
Removes all desktop build artifacts including JLink runtime, bundled JARs, Cargo build, and dist/build directories.