Bug 1858113 - xmlstreambuffer fails to build with java-11-openjdk
Summary: xmlstreambuffer fails to build with java-11-openjdk
Alias: None
Product: Fedora
Classification: Fedora
Component: xmlstreambuffer
Version: rawhide
Hardware: All
OS: All
Target Milestone: ---
Assignee: Ankur Sinha (FranciscoD)
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: Java11
TreeView+ depends on / blocked
Reported: 2020-07-16 22:39 UTC by jiri vanek
Modified: 2020-08-10 12:46 UTC (History)
8 users (show)

Fixed In Version: xmlstreambuffer-1.5.4-15.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-08-10 12:46:03 UTC
Type: ---

Attachments (Terms of Use)

Description jiri vanek 2020-07-16 22:39:14 UTC
xmlstreambuffer 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=47164093
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 xmlstreambuffer; cd xmlstreambuffer;  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:08:13 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 Fabio Valentini 2020-07-18 15:16:58 UTC
Looks like there's a real bug in xmlstreambuffer (when fixing -source and -target flags first):

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project streambuffer: Compilation failure: Compilation failure: 
[ERROR] /builddir/build/BUILD/xmlstreambuffer-1.5.4/src/com/sun/xml/stream/buffer/stax/StreamWriterBufferCreator.java:[48,24] package javax.activation does not exist
[ERROR] /builddir/build/BUILD/xmlstreambuffer-1.5.4/src/com/sun/xml/stream/buffer/stax/StreamWriterBufferCreator.java:[276,29] cannot find symbol
[ERROR]   symbol:   class DataHandler
[ERROR]   location: class com.sun.xml.stream.buffer.stax.StreamWriterBufferCreator
[ERROR] /builddir/build/BUILD/xmlstreambuffer-1.5.4/src/com/sun/xml/stream/buffer/stax/StreamWriterBufferCreator.java:[63,8] com.sun.xml.stream.buffer.stax.StreamWriterBufferCreator is not abstract and does not override abstract method writeBinary(java.lang.String) in org.jvnet.staxex.XMLStreamWriterEx
[ERROR] /builddir/build/BUILD/xmlstreambuffer-1.5.4/src/com/sun/xml/stream/buffer/stax/StreamWriterBufferCreator.java:[276,17] writeBinary(DataHandler) in com.sun.xml.stream.buffer.stax.StreamWriterBufferCreator cannot implement writeBinary(java.lang.String) in org.jvnet.staxex.XMLStreamWriterEx
[ERROR]   return type void is not compatible with java.io.OutputStream
[ERROR] /builddir/build/BUILD/xmlstreambuffer-1.5.4/src/com/sun/xml/stream/buffer/stax/StreamWriterBufferCreator.java:[283,25] name clash: class StreamWriterBufferCreator has two methods with the same erasure, yet neither overrides the other
[ERROR]   first method:  writeBinary(DataHandler) in com.sun.xml.stream.buffer.stax.StreamWriterBufferCreator
[ERROR]   second method: writeBinary(javax.activation.DataHandler) in org.jvnet.staxex.XMLStreamWriterEx
[ERROR] -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.

Comment 3 Fabio Valentini 2020-08-10 12:46:03 UTC
Fixed and built by mbooth:

Note You need to log in before you can comment on or make changes to this bug.