[Bug 2028448] New: I've used maven-local-openjdk11, but xmvn still uses JDK17 as toolchain for org.fedoraproject.xmvn:xmvn-mojo:javadoc
https://bugzilla.redhat.com/show_bug.cgi?id=2028448
Bug ID: 2028448 Summary: I've used maven-local-openjdk11, but xmvn still uses JDK17 as toolchain for org.fedoraproject.xmvn:xmvn-mojo:javadoc Product: Fedora Version: rawhide Status: NEW Component: xmvn Assignee: mizdebsk@redhat.com Reporter: didiksupriadi41@gmail.com QA Contact: extras-qa@fedoraproject.org CC: java-sig-commits@lists.fedoraproject.org, mat.booth@gmail.com, mizdebsk@redhat.com, msrb@redhat.com Target Milestone: --- Classification: Fedora
Description of problem: I've used `maven-local-openjdk11`, but apparently `xmvn` still uses JDK17 as toolchain for org.fedoraproject.xmvn:xmvn-mojo:javadoc.
Happens when I tried to build `apache-ivy` (requires Pack200 class) here: https://download.copr.fedorainfracloud.org/results/jvanek/java17:pr:7/fedora...
but explicitly overriding JAVA_HOME to JDK11 fixed it: https://download.copr.fedorainfracloud.org/results/jvanek/java17:pr:8/fedora...
Version-Release number of selected component (if applicable): 4.0.0-4
How reproducible: always
Steps to Reproduce: For instance, we'd build `apache-ivy` using jvanek-java17-fedora-rawhide-x86_64.cfg [1] 1. $ fedpkg clone `apache-ivy` 2. $ sed -i 's/maven-local/maven-local-openjdk11/g' apache-ivy.spec 3. $ fedpkg mockbuild --root jvanek-java17-fedora-rawhide-x86_64.cfg
Actual results: https://download.copr.fedorainfracloud.org/results/jvanek/java17:pr:7/fedora...
Expected results: https://download.copr.fedorainfracloud.org/results/jvanek/java17:pr:8/fedora...
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=2028448
Didik Supriadi didiksupriadi41@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Comment|0 |updated
--- Comment #0 has been edited ---
Description of problem: I've used `maven-local-openjdk11`, but apparently `xmvn` still uses JDK17 as toolchain for org.fedoraproject.xmvn:xmvn-mojo:javadoc.
Happens when I tried to build `apache-ivy` (requires Pack200 class) here: https://download.copr.fedorainfracloud.org/results/jvanek/java17:pr:7/fedora...
but explicitly overriding JAVA_HOME to JDK11 fixed it: https://download.copr.fedorainfracloud.org/results/jvanek/java17:pr:8/fedora...
Version-Release number of selected component (if applicable): 4.0.0-4
How reproducible: always
Steps to Reproduce: For instance, we'd build `apache-ivy` using jvanek-java17-fedora-rawhide-x86_64.cfg [1] 1. $ fedpkg clone `apache-ivy` 2. $ sed -i 's/maven-local/maven-local-openjdk11/g' apache-ivy.spec 3. $ fedpkg mockbuild --root jvanek-java17-fedora-rawhide-x86_64.cfg
Actual results: https://download.copr.fedorainfracloud.org/results/jvanek/java17:pr:7/fedora...
Expected results: https://download.copr.fedorainfracloud.org/results/jvanek/java17:pr:8/fedora...
Additional info:
[1] https://raw.githubusercontent.com/judovana/FedoraSystemJdkBump/main/scritps/...
https://bugzilla.redhat.com/show_bug.cgi?id=2028448
Mikolaj Izdebski mizdebsk@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Triaged Doc Type|--- |If docs needed, set a value
--- Comment #1 from Mikolaj Izdebski mizdebsk@redhat.com --- Confirmed - XMvn Javadoc MOJO ignores Maven toolchains. Forwarded upstream: https://github.com/fedora-java/xmvn/issues/142
https://bugzilla.redhat.com/show_bug.cgi?id=2028448
--- Comment #3 from Ben Cotton bcotton@redhat.com --- This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it.
Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
https://bugzilla.redhat.com/show_bug.cgi?id=2028448
Ludek Smid lsmid@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |EOL Last Closed| |2023-05-25 17:59:43
--- Comment #4 from Ludek Smid lsmid@redhat.com --- Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.
Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field.
If you are unable to reopen this bug, please file a new report against an active release.
Thank you for reporting this bug and we are sorry it could not be fixed.
java-sig-commits@lists.fedoraproject.org
-
bugzilla＠redhat.com