This repository contains the scripts and resources for building and publishing the BaseX release artifacts: the ZIP archive, the Windows installer, the JAR file and the WAR file. The BaseX sources are maintained in the basex repository.
- A checkout of basex next to this repository (
../basex) - JDK 21 and Maven
- Windows: Maven is invoked via
cmd, and the installer is created with the bundled NSIS compiler
basex build.xq
Builds BaseX and writes the artifacts to release/. With -bbuild=war, only the WAR file is built by Maven, and with -bbuild=none, the existing Maven artifacts are reused.
The release workflow runs the same script on GitHub Actions and signs the Windows installer.
basex [-brelease=true] [-bdry=true] [-bclean=true] deploy.xq
Deploys the Maven modules that changed since the last run, creates the release files from the built artifacts and uploads them as snapshot or, with -brelease=true, as release. For releases, version.txt is uploaded to the parent of the target directory, where the version check of the GUI expects it. The server login and target directory are read from the environment variables BASEX_DEPLOY_SERVER and BASEX_DEPLOY_TARGET; -bdry=true prints the commands without executing them. With -bclean=true, the archives and copied libraries of the deployed modules are removed before building; this is always done for releases.
brew bump-formula-pr basex --url https://files.basex.org/releases/12.4/BaseX124.zip
Downloads the release, computes its checksum and opens a pull request for the Homebrew formula.
| Path | Contents |
|---|---|
dist/basex/ |
files copied unchanged into the distribution: readme, sample documents, catalog files, library licenses, XQuery modules |
images/ |
icons |
modules/ |
release and deployment modules |
win/ |
NSIS installer script and compiler |
build.xq |
build script |
deploy.xq |
deployment script |
BaseX is released under the BSD License.