Fix variable reference in Ant build file

[Vampire]

No description provided.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: b92a583e-6f82-48f5-a614-7ea9e90aa787

📥 Commits

Reviewing files that changed from the base of the PR and between 99fb674 and 1105a9e.

📒 Files selected for processing (1)

• build.xml

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.

---

📝 Walkthrough

Walkthrough

The test target now uses the valid ${test.resource.dir} property reference. The test resources directory resolves correctly and is added to the JUnit launcher classpath.

Changes

Test classpath correction

Layer / File(s)	Summary
Correct test resource property reference build.xml	The junitlauncher configuration now uses ${test.resource.dir} instead of the malformed §{test.resource.dir} reference.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 1105a

The Ant test target now includes test resources through the valid property reference. No current merge-readiness risk remains.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided, so the change intent is not documented in the description.	Add a brief description stating that the invalid §{test.resource.dir} reference was corrected to ${test.resource.dir} in the Ant test target.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the change to the Ant build file variable reference.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the classpath line
The test resources now align
One curly brace is placed with care
JUnit finds the files there
Hop, hop, green builds everywhere}

_{Comment @coderabbitai help to get the list of available commands.}