Skip to content

bin/install-deps: pinned Point Blue libraries from their releases - #128

Merged
jcombs-pointblue merged 1 commit into
masterfrom
install-deps
Nov 11, 2026
Merged

jcombs-pointblue merged 1 commit into
masterfrom
install-deps

Conversation

@jcombs-pointblue

Copy link
Copy Markdown
Contributor

Building from source meant working out the order of the five repositories and checking out the right tag of each, because none of the Point Blue libraries is on Maven Central (feedback from a user building the set).

  • bin/install-deps reads the versions a pom pins (tracecore.version, simulator.version, dirxmldev.version, console.version) and installs each jar from its GitHub release into ~/.m2 with a flat pom. Only curl and mvn are needed (no gh). A version already installed is kept, so a jar you built yourself wins. Options: --force, --list, --dry-run, --pom FILE, or name the libraries to install.
  • docs/install.md §2.0 covers the repositories, their order, which pom pins what, and building one yourself from its tag. README, install.md §2.1/2.2 and agent-assisted-setup now use the script. The agent setup prompt never installed the trace parser before.
  • CI uses the script for the trace parser in both jobs, replacing gh release download plus install:install-file.
  • DirXMLDevWeb carries an identical copy; that PR is separate.

Tested: against an empty local repository, the script installed all four libraries the web's pom pins in about 6 s. With that repository, the web's mvn test and core's mvn -Pidm.portable test (73 tests) both passed. Also checked: --list, the "already installed" skip, an unknown name, a name the pom doesn't pin, and a release that doesn't exist (404, with a message to build it from the tag instead).

🤖 Generated with Claude Code

Building from source meant building the trace parser, the simulator,
console-auth and dirxml-dev from the right tags in the right order, since
none of them is on Maven Central. bin/install-deps reads the versions a pom
pins and installs each jar from its GitHub release into ~/.m2 with a flat
pom (curl + mvn install:install-file, what CI already did by hand). A jar
already installed is kept; --force, --list, --dry-run, --pom.

docs/install.md §2.0 gives the five repositories, their order and pins.
README, install.md and agent-assisted-setup use the script; CI uses it for
the trace parser in place of gh release download.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jcombs-pointblue
jcombs-pointblue merged commit 1ec7f6d into master Nov 11, 2026
4 checks passed
@jcombs-pointblue
jcombs-pointblue deleted the install-deps branch November 11, 2026 14:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant