Skip to content

Developer information

davidcok edited this page Nov 12, 2026 · 7 revisions

The repository's CONTRIBUTING.md states how to contribute and what a pull request needs. This page gives background.

Branches

  • dev -- development; pull requests target it. Work is done on feature branches made from dev.
  • master -- releases. dev is merged into master when a release is ready.
  • gh-pages -- the project website.

Code organization

  • SMT -- the jSMTLIB library and command-line tool (make build builds jSMTLIB.jar)
  • SMTlsp -- a language server for SMT-LIB, built on the library
  • SMTTests -- tests of the library and the language server (see its README)
  • SMTPlugin, SMTFeature, SMTUpdateSite -- the Eclipse plug-in, its feature and its update site

Building and testing

The build needs a JDK (21 or later) and make. In SMT/, make build builds the jar and make test runs the test suite. Tests with real solvers need the solver binaries from the Solvers repository; SMTTests/README.md describes how they are found and chosen.

Continuous integration builds and tests each push to dev and master on Linux, macOS and Windows, and runs CodeQL static analysis.

Creating a release

The release number is in SMT/version.txt. A push to master builds and tests the release and uploads jSMTLIB.jar to a draft GitHub release with that number. The release manager writes the release notes and publishes the release, then increments SMT/version.txt so the released version cannot be overwritten.