Bug ID: 2051188
Summary: maven-scm fails to build with java-17-openjdk
QA Contact: extras-qa(a)fedoraproject.org
CC: dbhole(a)redhat.com, didiksupriadi41(a)gmail.com,
Target Milestone: ---
maven-scm fails to build with java-17-openjdk as sytem JDK. See
See especially part about known failures:
For the build logs, see:
We run the rebuild in side tag f36-java17, but as fail ratio was small, we
expect this side tag to be merged into rawhide 7 or 8 of February 2022.
To reproduce before this date simply: fedpkg clone maven-scm; cd maven-scm;
fedpkg build --target f36-java17; #The target is crucial.
After this date the usual fedpkg build in f36 and up should do.
We run two reruns your package failed both.
We had also run the mass rebuilds in copr since November. We keep all
encountered failures. See them here:
You may find interesting additional informations here. Also we were spamming
maintainers regualrly, check you spam folder.
We had tried aprox 500 packages, and aprox 65 had failed, so the
java-17-openjdk will be system JDK in f36, and you should fix your package if
you want to keep it alive. Usually the fix is simple, and best is to update the
package to latest upstream version.
There will be usual mass rebuild once f36 branches. You may got another FTBFS
Let us know here if you have any questions, here in bug, or at
We'd appreciate help from the people who know this package best, but if you
don't want to work on this now, let us know so we can try to work around it on
our side if needed.
[Bug 2024265] java-17-openjdk as system JDK in F36
You are receiving this mail because:
You are on the CC list for the bug.