You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2019/05/10 20:14:00 UTC
[jira] [Assigned] (QPID-8282) [JMS AMQP 0-x] Java 11 build/runtime
failure due to use of javax.xml.bind.DatatypeConverter
[ https://issues.apache.org/jira/browse/QPID-8282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy reassigned QPID-8282:
--------------------------------
Assignee: Alex Rudyy
> [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
> Assignee: Alex Rudyy
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org