Skip to content

build: pin the patched ANTLR generator jar, drop stale ANTLR remnants#1308

Open
joaodinissf wants to merge 1 commit into
dsldevkit:masterfrom
joaodinissf:chore/remove-stale-readme
Open

build: pin the patched ANTLR generator jar, drop stale ANTLR remnants#1308
joaodinissf wants to merge 1 commit into
dsldevkit:masterfrom
joaodinissf:chore/remove-stale-readme

Conversation

@joaodinissf

@joaodinissf joaodinissf commented Apr 15, 2026

Copy link
Copy Markdown
Collaborator

Makes the ANTLR generator dependency self-contained and removes two stale remnants of the manual-download era.

Pin the generator jar

The MWE2 grammar workflows need the patched ANTLR 3.2 generator. GenerateTestLanguage.mwe2.launch already references com.avaloq.tools.ddk.workflow/antlr-generator-3.2.0-patch.jar on its classpath — but the jar was never committed. In its absence, Xtext's AntlrToolFacade silently downloads it, without checksum verification, from itemis hosting that has already moved once (download.itemis.comartifacts.itemis.cloud) and whose p2 repository is dead (HTTP 404). If that URL ever disappears, no DDK grammar can be regenerated from a fresh clone.

The jar is now committed (1.4 MB, frozen upstream since 2014, BSD-licensed) with its provenance and SHA-256 recorded in antlr-generator-3.2.0-patch.md alongside. The bytes were verified against the URL the Xtext 2.43 sources actually use. The workflow project is not a Maven module, so this has no build impact; the jar matters only for IDE-based grammar regeneration.

GenerateCheck/GenerateCheckCfg launch configs use Eclipse's default classpath and keep the auto-download fallback (cached as a gitignored hidden file); the note documents this. The jar becomes deletable if generation ever moves to xtext-maven-plugin + org.eclipse.xtext:xtext-antlr-generator from Maven Central.

Remove stale remnants

  • ddk-parent/readme.txt — "Download antlr-generator-3.2.0.jar into this folder": names the unpatched jar and a location that no resolution route (classpath, working directory, download cache) ever reads. Nothing references it.
  • ddk-target/ddk-antlr.target — orphaned target definition whose primary location is the dead itemis p2 repository, pinning 2022-era Eclipse/SWTBot/Orbit URLs that contradict the maintained ddk.target. Zero references anywhere in the repo; not wired into the Maven/Tycho build.

🤖 Generated with Claude Code

@joaodinissf joaodinissf force-pushed the chore/remove-stale-readme branch 2 times, most recently from 9a5b925 to dab42af Compare April 20, 2026 08:21
@joaodinissf joaodinissf force-pushed the chore/remove-stale-readme branch 2 times, most recently from 3f4c905 to ebb9454 Compare June 2, 2026 16:56
The MWE2 grammar workflows need the patched ANTLR 3.2 generator. The launch
classpath of GenerateTestLanguage.mwe2.launch references
com.avaloq.tools.ddk.workflow/antlr-generator-3.2.0-patch.jar, but the jar was
never committed - Xtext's AntlrToolFacade silently downloads it (without
checksum verification) from itemis hosting that has already moved once and
whose p2 repository is dead. Commit the jar (SHA-256 pinned in the
accompanying note) so regeneration is self-contained.

Also remove two stale remnants of the manual-download era: ddk-parent/readme.txt
(instructed downloading the wrong jar into a folder no resolution route reads)
and ddk-target/ddk-antlr.target (orphaned target definition referencing the dead
itemis p2 repository; no references anywhere in the repo).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@joaodinissf joaodinissf force-pushed the chore/remove-stale-readme branch from ebb9454 to bb0c518 Compare June 12, 2026 20:01
@joaodinissf joaodinissf changed the title Remove stale ANTLR 3.2 references and readme.txt build: pin the patched ANTLR generator jar, drop stale ANTLR remnants Jun 12, 2026
@joaodinissf joaodinissf marked this pull request as ready for review June 12, 2026 20:01
@joaodinissf joaodinissf requested a review from rubenporras June 12, 2026 20:01
@joaodinissf joaodinissf enabled auto-merge (rebase) June 12, 2026 20:01
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