[
https://issues.apache.org/jira/browse/HDDS-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17986830#comment-17986830
]
Ivan Andika commented on HDDS-13342:
------------------------------------
The error can be reproduced on compile(11), compile(17), compile(21). See:
https://github.com/ivandika3/ozone/actions/runs/15966061635/job/45027340910
> Replace DatatypeConverter.printHexBinary with Hex.encodeHexString
> -----------------------------------------------------------------
>
> Key: HDDS-13342
> URL: https://issues.apache.org/jira/browse/HDDS-13342
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ivan Andika
> Assignee: Chia-Chuan Ho
> Priority: Minor
>
> When trying to use DatatypeConverter.printHexBinary and build it on JDK21
> environment on the ozone-manager module, I encountered the following exception
> {code:java}
> [ERROR] Failed to execute goal
> dev.aspectj:aspectj-maven-plugin:1.14.1:compile (default) on project
> ozone-manager: AJC compiler errors: 3369
> [ERROR] error at import javax.xml.bind.DatatypeConverter;
> The import javax.xml.bind.DatatypeConverter cannot be resolved{code}
> This seems to be related javax.xml.bind removal in the newer JDK and
> aspectj-maven-plugin compiler being more strict than the normal javac
> compiler.
> To prevent this issue we can replace DatatypeConverter.printHexBinary with
> the Hex.encodeHexString instead. We need to ensure that the behavior remains
> unchanged, especially need to check the lowercase handling (e.g.
> Hex.encodeHexString by default will automatically return the result in
> lowercase). Afterwards, we can ban javax.xml.bind.DatatypeConverter in
> pom.xml.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org
For additional commands, e-mail: issues-h...@ozone.apache.org
