What happens
eoc latex (src/commands/latex.js:20, wired at src/eoc.js:406-413, advertised in README.md:138) runs the Maven goal eo:latex. eo-maven-plugin no longer ships that goal. Its plugin.xml (checked in version 0.62.1, the version currently pinned in eo-version.txt) lists: assemble, atoms-table, clean, compile, format, help, lint, parse, place, print, probe, pull, register, resolve, transpile, unplace, unspile - no latex, and no Mj*Latex class in the jar at all.
Reproduced with a real Maven run:
$ node src/eoc.js --batch --easy -s src -t target latex
...
[ERROR] Could not find goal 'latex' in plugin org.eolang:eo-maven-plugin:0.62.1 among available
goals assemble, atoms-table, clean, compile, format, help, lint, parse, place, print, probe,
pull, register, resolve, transpile, unplace, unspile -> [Help 1]
The command's only test (test/commands/test_latex.js:14) has been disabled with this.skip() since commit cb217ca (2025-06-22), the same commit that bumped the plugin version - so the command has been silently broken for over a year with its own test skipped rather than fixed or removed.
This repo already has a precedent for exactly this situation: #744 ("Could not find goal sodg in plugin org.eolang:eo-maven-plugin:0.58.8") was resolved by #892, which removed the outdated sodg command entirely.
What should happen
Either eoc latex should be removed the same way sodg was (README entry, command file, test, and CLI wiring), or the corresponding eo:latex goal should be restored in eo-maven-plugin. Either way, a user following the README and running eoc latex should not get a Maven MojoNotFoundException after a full register+parse pipeline has already run.
What happens
eoc latex(src/commands/latex.js:20, wired atsrc/eoc.js:406-413, advertised inREADME.md:138) runs the Maven goaleo:latex.eo-maven-pluginno longer ships that goal. Itsplugin.xml(checked in version 0.62.1, the version currently pinned ineo-version.txt) lists:assemble, atoms-table, clean, compile, format, help, lint, parse, place, print, probe, pull, register, resolve, transpile, unplace, unspile- nolatex, and noMj*Latexclass in the jar at all.Reproduced with a real Maven run:
The command's only test (
test/commands/test_latex.js:14) has been disabled withthis.skip()since commitcb217ca(2025-06-22), the same commit that bumped the plugin version - so the command has been silently broken for over a year with its own test skipped rather than fixed or removed.This repo already has a precedent for exactly this situation: #744 ("Could not find goal
sodgin pluginorg.eolang:eo-maven-plugin:0.58.8") was resolved by #892, which removed the outdatedsodgcommand entirely.What should happen
Either
eoc latexshould be removed the same waysodgwas (README entry, command file, test, and CLI wiring), or the correspondingeo:latexgoal should be restored ineo-maven-plugin. Either way, a user following the README and runningeoc latexshould not get a MavenMojoNotFoundExceptionafter a full register+parse pipeline has already run.