[
https://issues.apache.org/jira/browse/QPID-8282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832883#comment-16832883
]
ASF subversion and git services commented on QPID-8282:
-------------------------------------------------------
Commit 948ef002b4404a66d8164e0c47517567f8a1c1e3 in qpid-jms-amqp-0-x's branch
refs/heads/master from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-jms-amqp-0-x.git;h=948ef00 ]
QPID-8282: Bump parent apache pom version to 21 and upgrade maven plugin
versions
> [JMS AMQP 0-x] Java 11 build/runtime failure due to use of
> javax.xml.bind.DatatypeConverter
> -------------------------------------------------------------------------------------------
>
> Key: QPID-8282
> URL: https://issues.apache.org/jira/browse/QPID-8282
> Project: Qpid
> Issue Type: Bug
> Components: JMS AMQP 0-x
> Affects Versions: qpid-java-client-0-x-6.3.3
> Reporter: Robbie Gemmell
> Priority: Minor
> Fix For: qpid-java-client-0-x-6.3.4
>
>
> In setting up a new system, I happened to make attempt to build the JMS AMQP
> 0-x client using Java 11. It failed to compile due to use of
> javax.xml.bind.DatatypeConverter for Base64 handling in the SCRAM-SHA
> mechanisms. This prevents building on Java 11, and would break use of
> SCRAM-SHA while running on Java 11 assuming nothing else stopped things
> working.
> Although the 0-x client is essentially in maintenance/legacy mode at this
> point, blockers as trivial as Base 64 handling would be nice to resolved if
> it made using Java 11 possible, if only to simplify migrations later.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
