Bug 1858080

Summary:	resteasy fails to build with java-11-openjdk
Product:	[Fedora] Fedora	Reporter:	jiri vanek <jvanek>
Component:	resteasy	Assignee:	Dinesh Prasanth <dmoluguw>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	alee, ascheel, dchen, decathorpe, dmoluguw, edewata, java-maint-sig, java-sig-commits, jvanek, markku.korkeala, puntogil, sgehwolf, stewardship-sig, weli
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	resteasy-3.0.26-4.fc33	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-22 08:32:17 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:	1825969

Description jiri vanek 2020-07-16 21:56:21 UTC

resteasy fails to build with java-11-openjdk as sytem JDK. See https://fedoraproject.org/wiki/Changes/Java11 .
See especially part about known failures: https://fedoraproject.org/wiki/Changes/Java11#common_issues_packagers_can_face_and_gathered_solutions

For the build logs, see: https://koji.fedoraproject.org/koji/taskinfo?taskID=47161929
We run the rebuild longer then 10days ago. Log may be gone. Also your package may be passing in regular rawhide.
To reproduce, simply: fedpkg clone resteasy; cd resteasy;  fedpkg build --target f33-java11; #The target is crucial.

We run two reruns your package failed both.


We had tried 650 packages, and 500 had passed, so the java-11-openjdk will be system JDK in f33, 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 f33 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 2020-07-17 04:04:06 UTC

highlight: This was rebuild in sidetag f33-java11. Thus --target is really necessary to reproduce failure.
please note: This side tag, f33-java11, will be merged to main f33 buildroot in aprox 14 days.

Comment 2 Markku Korkeala 2020-07-21 18:35:17 UTC

Build fails due to missing native2ascii tool, see below the RPM build error. The tool is removed from JDK11:
The native2ascii tool has been removed from the JDK. Because JDK 9 and later re‐leases support UTF-8 based properties resource bundles, the conversion tool forUTF-8 based properties resource bundles to ISO-8859-1 is no longer needed.

Is the "Fixing JDK7 ASCII issues" still relevant for JDK11?

Build log:

RPM build errors:
+ for f in ${files}
+ native2ascii -encoding UTF8 resteasy-jaxrs/src/main/java/org/jboss/resteasy/annotations/Query.java resteasy-jaxrs/src/main/java/org/jboss/resteasy/annotations/Query.java
/var/tmp/rpm-tmp.bufPIw: line 182: native2ascii: command not found
error: Bad exit status from /var/tmp/rpm-tmp.bufPIw (%prep)
    Bad exit status from /var/tmp/rpm-tmp.bufPIw (%prep)
Finish: rpmbuild resteasy-3.0.26-3.fc33.src.rpm

Comment 3 Severin Gehwolf 2020-07-22 06:48:22 UTC

(In reply to Markku Korkeala from comment #2)
> Build fails due to missing native2ascii tool, see below the RPM build error.
> The tool is removed from JDK11:
> The native2ascii tool has been removed from the JDK. Because JDK 9 and later
> re‐leases support UTF-8 based properties resource bundles, the conversion
> tool forUTF-8 based properties resource bundles to ISO-8859-1 is no longer
> needed.
> 
> Is the "Fixing JDK7 ASCII issues" still relevant for JDK11?
> 
> Build log:
> 
> RPM build errors:
> + for f in ${files}
> + native2ascii -encoding UTF8
> resteasy-jaxrs/src/main/java/org/jboss/resteasy/annotations/Query.java
> resteasy-jaxrs/src/main/java/org/jboss/resteasy/annotations/Query.java
> /var/tmp/rpm-tmp.bufPIw: line 182: native2ascii: command not found
> error: Bad exit status from /var/tmp/rpm-tmp.bufPIw (%prep)
>     Bad exit status from /var/tmp/rpm-tmp.bufPIw (%prep)
> Finish: rpmbuild resteasy-3.0.26-3.fc33.src.rpm

I'd suggest to try building without the conversion. Failing that, try using iconv instead like I've proposed for bug 1857991. It remains to be seen whether or not that's the only issue.

Comment 4 Fabio Valentini 2020-07-22 08:32:17 UTC

Yeah, it built fine without native2ascii conversion, and some minor modifications for APIs that were removed in OpenJDK 11.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1544749