Install Anserini Dev Env

Install Anserini Dev Env

Overview

Use this skill to prepare Anserini for source development, not just fatjar execution. Prefer normal Java tooling over Python-style virtual environments: pin/select JDK 21, use Maven 3.9+, then build with Anserini's scripts or Maven.

Do not assume a released fatjar is sufficient for source-development requests; use the checkout when local code, tests, or snapshots matter.

Workflow

1. Verify requirements first:
   • Require java to report major version 21.
   • Require mvn to report version 3.9 or newer.
   • Check for git.

java -version
mvn -v
git --version

2. If Java is missing or not exactly 21, select or install JDK 21 with the user's existing version manager when possible:
   • Prefer mise, sdkman, asdf, or jenv if already present.
   • On macOS, Homebrew Temurin/OpenJDK 21 is acceptable when no Java version manager is in use.
   • Do not create a Python virtual environment for Java development.
3. If Maven is missing or older than 3.9, update Maven using the host's package manager or version manager. Anserini does not currently rely on a checked-in Maven wrapper.
4. Clone the repository:

git clone https://github.com/castorini/anserini.git

If the user has already provided an empty destination directory and wants the checkout there, clone into the current directory:

git clone https://github.com/castorini/anserini.git .

5. Build from the repository root. Prefer Anserini's checked-in build scripts when present:

bin/qbuild.sh

Use bin/qbuild.sh for a quick build; it skips tests and Javadocs.

After a successful quick build, expect the shaded artifact at target/anserini-*-fatjar.jar.

bin/build.sh

Use bin/build.sh for a full build; it runs all tests and can take a while. While it runs, provide periodic progress updates. Track completed Surefire tests from Maven output or target/surefire-reports when possible, and report the final aggregate Tests run: N count when the build finishes.

If a script is unavailable or the user explicitly asks for Maven, use:

mvn clean package

Verification

After setup, re-run the explicit requirement checks. Then run the lightest verification that matches the user's goal: bin/qbuild.sh for a build-ready checkout, bin/build.sh for full validation, or targeted Maven tests for a code change. If dependency downloads fail because network access is sandboxed, rerun the build command with escalation instead of changing project files.

If a build was run, a concise final sanity check is:

git status --short --branch --ignored
ls -lh target/*fatjar.jar

For a functional smoke test after a successful build, run the CACM prebuilt-index reproduction command:

bin/run.sh io.anserini.search.SearchCollection \
  -index cacm \
  -topics cacm \
  -output run.cacm.bm25.txt \
  -hits 1000 \
  -bm25

Treat a successful run and generated run.cacm.bm25.txt file as proof that the checkout can execute Anserini search end to end. This command may download the small CACM prebuilt index and topics on first use, so skip it when the user only wants a local build check.

Then evaluate the run with Anserini's Java trec_eval wrapper:

bin/run.sh io.anserini.eval.TrecEval \
  -c \
  -m map \
  -m P.30 \
  cacm \
  run.cacm.bm25.txt

Expected scores are:

map     all     0.3123
P_30    all     0.1942

To verify them mechanically:

bin/run.sh io.anserini.eval.TrecEval \
  -c \
  -m map \
  -m P.30 \
  cacm \
  run.cacm.bm25.txt | tee eval.cacm.bm25.txt

grep -q $'map\tall\t0.3123' eval.cacm.bm25.txt
grep -q $'P_30\tall\t0.1942' eval.cacm.bm25.txt

For CLI examples after setup, use $anserini-cli.

Troubleshooting

• If java -version and mvn -v disagree about Java versions, fix JAVA_HOME and PATH so Maven uses JDK 21.
• On Windows, use WSL2 for Anserini builds.
• Avoid commands that trigger large prebuilt index downloads unless the user explicitly asks for retrieval experiments; Anserini can download large indexes on demand.
• Treat Anserini's current README as the source of truth for version requirements if it differs from this skill.