Repository navigation
Conversation
Enqueue derives a target's artifact from its version, and Maven had no derivation, so every Maven version was skipped.
Inference kept only the major of a recorded JDK unless the exact key existed, so Build-Jdk 1.8.0_181 built with the latest 8 update. Javac output differs between releases, so pick the same release, or the nearest update of the same major. Build-Jdk now outranks the coarser Build-Jdk-Spec, and a jar tool's Created-By counts as a JDK version. JDK 8 stands in for older releases, which none of the downloads cover. forge-parent: tovwoyqwzpqz
Builds used Debian's Maven, whose default plugin versions differ from the publisher's release and decide much of the output (compiler flags, jar attributes, module-info packages), and fail on old projects outright (antrun 'tasks', source 1.5). Install the release from Maven Central: the one a Maven wrapper pins, else the one a pre-3.x maven-archiver named in the manifest, else the newest out at the ref's commit time. Its global settings mirror Central to HTTPS, which Maven before 3.2.3 does not use. Strategies that name no release get 3.9.9 from Central, the version Debian 13's package had. Export a UTF-8 locale for the JDK, since javac otherwise reads sources and writes class names as ASCII. Check out with CRLF when upstream's copied pom.xml has CRLF and the repository's does not. forge-parent: qttotpppltol
The first build file found at the shallowest depth decided the build tool, so a package.json beside the root pom.xml (log4j) made the release an unsupported npm build depending on file order. Rank the tools at equal depth. forge-parent: tnluwzkxpnmy
Repository inference read only scm>url, which in older POMs is often a
web viewer or a retired host while the connection names the git
repository. Try the connections too, expand ${...} properties, and map
Apache git and Subversion URLs to the project's GitHub mirror when the
mirror exists.
forge-parent: swsnksxtkxmp
pohlarized
approved these changes
Nov 4, 2026
msuozzo
force-pushed
the
push-kwqsotyqmrrz
branch
from
November 5, 2026 20:31
e0c06f4 to
4e93b00
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repository inference read only scm>url, which in older POMs is often a
web viewer or a retired host while the connection names the git
repository. Try the connections too, expand ${...} properties, and map
Apache git and Subversion URLs to the project's GitHub mirror when the
mirror exists.