xmvn-connector-ivy fails to build with java-17-openjdk as sytem JDK. See https://fedoraproject.org/wiki/Changes/Java17 . See especially part about known failures: https://fedoraproject.org/wiki/Changes/Java17#common_issues_packagers_can_face_and_gathered_solutions For the build logs, see: https://koji.fedoraproject.org/koji/taskinfo?taskID=82435840 https://kojipkgs.fedoraproject.org/work/tasks/5985/82435985/mock_output.log https://kojipkgs.fedoraproject.org/work/tasks/5985/82435985/hw_info.log https://kojipkgs.fedoraproject.org/work/tasks/5985/82435985/state.log https://kojipkgs.fedoraproject.org/work/tasks/5985/82435985/build.log https://kojipkgs.fedoraproject.org/work/tasks/5985/82435985/root.log 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 xmvn-connector-ivy; cd xmvn-connector-ivy; 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: https://copr.fedorainfracloud.org/coprs/jvanek/java17//package/xmvn-connector-ivy 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 bug. Let us know here if you have any questions, here in bug, or at java-devel.org . 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.
ERROR] org.fedoraproject.xmvn.connector.ivy.DeployTest.publishDeployExceptionTest Time elapsed: 0.258 s <<< ERROR! java.lang.ExceptionInInitializerError at org.fedoraproject.xmvn.connector.ivy.DeployTest.setUp(DeployTest.java:64) Caused by: net.sf.cglib.core.CodeGenerationException: java.lang.reflect.InaccessibleObjectException-->Unable to make protected final java.lang.Class java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) throws java.lang.ClassFormatError accessible: module java.base does not "opens java.lang" to unnamed module @1efed2d at org.fedoraproject.xmvn.connector.ivy.DeployTest.setUp(DeployTest.java:64) Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make protected final java.lang.Class java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) throws java.lang.ClassFormatError accessible: module java.base does not "opens java.lang" to unnamed module @1efed2d at org.fedoraproject.xmvn.connector.ivy.DeployTest.setUp(DeployTest.java:64) [ERROR] org.fedoraproject.xmvn.connector.ivy.DeployTest.publishDeployEffectivePomTest Time elapsed: 0.003 s <<< ERROR! java.lang.NoClassDefFoundError: Could not initialize class org.easymock.internal.ClassProxyFactory$2 at org.fedoraproject.xmvn.connector.ivy.DeployTest.setUp(DeployTest.java:64) [ERROR] org.fedoraproject.xmvn.connector.ivy.DeployTest.publishDeployTest Time elapsed: 0.002 s <<< ERROR! java.lang.NoClassDefFoundError: Could not initialize class org.easymock.internal.ClassProxyFactory$2 at org.fedoraproject.xmvn.connector.ivy.DeployTest.setUp(DeployTest.java:64) [ERROR] org.fedoraproject.xmvn.connector.ivy.DeployTest.publishDeployIvyTest Time elapsed: 0.003 s <<< ERROR! java.lang.NoClassDefFoundError: Could not initialize class org.easymock.internal.ClassProxyFactory$2 at org.fedoraproject.xmvn.connector.ivy.DeployTest.setUp(DeployTest.java:64) [ERROR] org.fedoraproject.xmvn.connector.ivy.DeployTest.publishDeployXmlTest Time elapsed: 0.003 s <<< ERROR! java.lang.NoClassDefFoundError: Could not initialize class org.easymock.internal.ClassProxyFactory$2 at org.fedoraproject.xmvn.connector.ivy.DeployTest.setUp(DeployTest.java:64) [ERROR] org.fedoraproject.xmvn.connector.ivy.DeployTest.publishDeployEffectivePomExeptionTest Time elapsed: 0.003 s <<< ERROR! java.lang.NoClassDefFoundError: Could not initialize class org.easymock.internal.ClassProxyFactory$2 at org.fedoraproject.xmvn.connector.ivy.DeployTest.setUp(DeployTest.java:64) [ERROR] org.fedoraproject.xmvn.connector.ivy.DeployTest.publishDeployEffectivePomFailTest Time elapsed: 0.003 s <<< ERROR! java.lang.NoClassDefFoundError: Could not initialize class org.easymock.internal.ClassProxyFactory$2 at org.fedoraproject.xmvn.connector.ivy.DeployTest.setUp(DeployTest.java:64) [INFO] [INFO] Results: [INFO] [ERROR] Errors: [ERROR] DeployTest.setUp:64 » NoClassDefFound Could not initialize class org.easymock.... [ERROR] DeployTest.setUp:64 » NoClassDefFound Could not initialize class org.easymock.... [ERROR] DeployTest.setUp:64 » NoClassDefFound Could not initialize class org.easymock.... [ERROR] DeployTest.setUp:64 » ExceptionInInitializer [ERROR] DeployTest.setUp:64 » NoClassDefFound Could not initialize class org.easymock.... [ERROR] DeployTest.setUp:64 » NoClassDefFound Could not initialize class org.easymock.... [ERROR] DeployTest.setUp:64 » NoClassDefFound Could not initialize class org.easymock.... [INFO] [ERROR] Tests run: 14, Failures: 0, Errors: 7, Skipped: 0 two issues: one is jdk17 accesibility and second too, or to old easymock. Best would update to usptream verson supporting 17. But the isseus may really b Where te easy mock is test onloy issue for sure, the: net.sf.cglib.core.CodeGenerationException: java.lang.reflect.InaccessibleObjectException-->Unable to make protected final java.lang.Class java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) throws java.lang.ClassFormatError accessible: module java.base does not "opens java.lang" to unnamed module @1efed2d at org.fedoraproject.xmvn.connector.ivy.DeployTest.setUp(DeployTest.java:64) Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make protected final java.lang.Class java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) throws java.lang.ClassFormatError accessible: module java.base does not "opens java.lang" to unnamed module @1efed2d May be hitting issue in jdk17 incompatible production code
This is a known issue with EasyMock: https://github.com/easymock/easymock/issues/274 Workaround is to add the following line to configuration of Maven Surefire Plugin: <argLine>--add-opens=java.base/java.lang=ALL-UNNAMED</argLine> Fixes to similar issues in other packages: https://src.fedoraproject.org/rpms/xmvn/c/f492a6e https://src.fedoraproject.org/rpms/easymock/c/39ccca4 https://src.fedoraproject.org/rpms/mockito/c/8befe76 Severity is low as this only affects running tests. Workaround exists and worst case I can simply disable tests.
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
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.
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.