Repository navigation
bin/install-deps: pinned Point Blue libraries from their releases - #128
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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-depsreads the versions a pom pins (tracecore.version,simulator.version,dirxmldev.version,console.version) and installs each jar from its GitHub release into~/.m2with a flat pom. Onlycurlandmvnare needed (nogh). 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.gh release downloadplusinstall:install-file.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 testand core'smvn -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