Skip to content

ci: fetch Vineflower by the plugin's coordinates, and try a failed fetch again - #2030

Merged
swapnilpaliwal-sd merged 1 commit into
devfrom
ci/java-decompiler-fetch
Nov 19, 2026
Merged

swapnilpaliwal-sd merged 1 commit into
devfrom
ci/java-decompiler-fetch

Conversation

@swapnilpaliwal-sd

Copy link
Copy Markdown
Contributor

Refs #2029

What changed

The Java engine job fetches Vineflower (the decompiler --library auto uses for class jars) with mvn -q dependency:get. Maven resolves the dependency: prefix from Maven Central's plugin-group metadata, and when that read fails it stops with:

[ERROR] No plugin found for prefix 'dependency' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] ...

The job then fails before any Java case runs. This happened on #2029 (0.2.4 into dev), on the first run and on the rerun of the failed job, while the push of the same commit to dev passed. No other run in the last 40 failed at this step.

  • The step names the plugin in full (org.apache.maven.plugins:maven-dependency-plugin:3.11.0:get), so there is no prefix lookup.
  • A failed download is tried up to three times, 15 s and 30 s apart, with a warning per failed attempt.

Why the goldens moved, or why they did not

No golden moved. Workflow only.

Evidence

Against an empty local repository and plain Maven Central settings, the new command downloads org/vineflower/vineflower/1.10.1/vineflower-1.10.1.jar and exits 0. The workflow file parses as YAML.

@swapnilpaliwal-sd
swapnilpaliwal-sd merged commit f52944b into dev Nov 19, 2026
12 checks passed
@swapnilpaliwal-sd
swapnilpaliwal-sd deleted the ci/java-decompiler-fetch branch November 19, 2026 05:17
…tch again

`mvn dependency:get` resolves the `dependency` prefix from Maven Central's
plugin-group metadata. When that read fails, Maven stops with "No plugin
found for prefix 'dependency'" and the Java engine job fails before a test
runs. It happened on the pull request that merged 0.2.4 into dev, on the
first run and on the rerun, while the push of the same commit passed.

The step now names maven-dependency-plugin 3.11.0 in full, so no prefix
lookup takes place, and tries the download up to three times.
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