Bug 2051166

Summary:	javassist fails to build with java-17-openjdk
Product:	[Fedora] Fedora	Reporter:	jiri vanek <jvanek>
Component:	javassist	Assignee:	Sergio Basto <sergio>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	36	CC:	agrimm, alexander.m.scheel, didiksupriadi41, java-maint-sig, java-sig-commits, jhuttana, jmagne, john5342, jvanek, mizdebsk, mkdineshprasanth, pmikova, sergio, sgehwolf, zmiklank
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	javassist-3.28.0-4.fc36	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-10 11:38:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2024265

Description jiri vanek 2022-02-06 14:45:18 UTC

javassist 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=82428395
https://kojipkgs.fedoraproject.org/work/tasks/8552/82428552/mock_output.log
https://kojipkgs.fedoraproject.org/work/tasks/8552/82428552/hw_info.log
https://kojipkgs.fedoraproject.org/work/tasks/8552/82428552/state.log
https://kojipkgs.fedoraproject.org/work/tasks/8552/82428552/build.log
https://kojipkgs.fedoraproject.org/work/tasks/8552/82428552/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 javassist; cd javassist;  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/javassist
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.

Comment 1 jiri vanek 2022-02-06 14:50:01 UTC

[INFO] -------------------------------------------------------------
[ERROR] /builddir/build/BUILD/javassist-rel_3_28_0_ga/src/test/test2/Inner.java:[7,48] package java.rmi.activation.ActivationGroupDesc does not exist
[ERROR] /builddir/build/BUILD/javassist-rel_3_28_0_ga/src/test/test2/Inner.java:[8,28] package java.rmi.activation does not exist
[ERROR] /builddir/build/BUILD/javassist-rel_3_28_0_ga/src/test/test2/Inner.java:[9,32] package java.rmi.activation does not exist
[INFO] 3 errors 


Hm. if this would be prt from jdk8 tojdk11, I would advice you to use jakarta java EE rebranded codebase. ..but...


from jek17 pages: is no replacement for the RMI Activation mechanism in the Java Platform. Users of RMI Activation are advised to migrate their applications to other technologies.

Soudns like time to seal thsi pkg with jdk11 or try to find some library reimplementing it:(

Comment 2 Ben Cotton 2022-02-08 20:12:47 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 3 Zuzana Miklankova 2022-03-09 09:18:46 UTC

An upstream issue exists for failing to build javassist with jdk17[1], but does not seem to be much alive.



[1] https://github.com/jboss-javassist/javassist/issues/400

Comment 4 Zuzana Miklankova 2022-05-10 11:38:55 UTC

That issue is tracking some other problem with jdk17. I have created a new issue for RMI deprecation[1]. Until the issue is solved the javassist package will be built without running the dependent tests.
As the javassist built with openjdk17 is in rawhide, I am closing this BZ.


[1] https://github.com/jboss-javassist/javassist/issues/413

Comment 5 Fedora Update System 2022-05-14 13:22:35 UTC

FEDORA-2022-33fdc8bf9b has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-33fdc8bf9b

Comment 6 Fedora Update System 2022-05-15 01:40:29 UTC

FEDORA-2022-33fdc8bf9b has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-33fdc8bf9b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-33fdc8bf9b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-05-23 01:14:20 UTC

FEDORA-2022-33fdc8bf9b has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.