[ 
https://issues.apache.org/jira/browse/HADOOP-19402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18037719#comment-18037719
 ] 

ASF GitHub Bot commented on HADOOP-19402:
-----------------------------------------

zhtttylz commented on PR #8038:
URL: https://github.com/apache/hadoop/pull/8038#issuecomment-3521893948

   > given trunk is now java17+ only, do we need to have a java17 source tree 
and profile?
   > 
   > We can just delete all java8 code and put this in its place. I would 
support this as it keeps the codebase cleaner
   
   Agreed. I’ll remove all Java 8 code and replace it with the Java 17 
implementation.




> [JDK11] JDiff Support JDK11
> ---------------------------
>
>                 Key: HADOOP-19402
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19402
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: build, documentation
>            Reporter: Shilun Fan
>            Assignee: Shilun Fan
>            Priority: Major
>              Labels: pull-request-available
>
> JDiff is a tool used to generate Java API documentation and display 
> differences between Java classes, primarily for detecting changes in Java API 
> across versions. However, JDiff does not support JDK 9 and above, and there 
> are no plans for further updates.
> Maven version: JDiff 1.0.9
> https://mvnrepository.com/artifact/jdiff/jdiff/1.0.9
> Official website: JDiff
> https://jdiff.sourceforge.net/
> During JDK 11 support, the changes in HADOOP-15304 allowed the project to 
> compile successfully but skipped JDiff. However, generating the JDiff XML is 
> still an essential step in the release process.
> To release Hadoop for JDK 11 and above, we need a tool similar to JDiff to 
> handle API comparison and detect version changes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to