[Android-tools-devel] Bug#1012103: Any volunteer to port android-framework-23 and android-platform-external-doclava (maybe more) to recent JDK?

[Andreas Tille]

Hi,

we have

  #1011567: android-framework-23: FTBFS with OpenJDK 17 due to com.sun.javadoc removal
  #1012103: android-platform-external-doclava: FTBFS with OpenJDK 17 due to com.sun.javadoc removal

(and maybe more related packages).  It seems the

Hans-Christoph Steiner <hans at eds.org> wrote[1]

  Looks like doclava would need to be ported to use the API that replaces 
  com.sun.javadoc:
  https://docs.oracle.com/en/java/javase/11/docs/api/jdk.javadoc/jdk/javadoc/doclet/package-summary.html#migration
  If someone does the migration, I can take care of the packaging updates.

Thank you Hans-Christian I would help as well but as you analysed in the
android-platform-external-doclava bug report[2]

  Doclava, which does not work with Java newer than 11.  Upstream still builds it 
  with java8. As in Android 13 still uses java8 in the build.  Is there any hope?

I've checked upstream Git[3] and found this commit

commit c8be8c65ab9dab2c4d3ec6ee2e717a3fae01c93d
Author: Nikita Iashchenko <nikitai at google.com>
Date:   Mon Feb 6 15:47:35 2023 +0000
 
    doclava17: Update gradle build/test infrastructure
    
    Root project has two subprojects that share common doclava
    sources except Doclava.java: 'doclava8' for original build
    with jdk11, and 'doclava17' – with new com.sun.javadoc
    implementation and building/running with jdk17.
    
    Also added an end-to-end test target e2eTestAOSP that runs
    old and new doclavas on same set of inputs for easier
    debugging and comparison.
    
    Bug: 260694901
    Test: ./gradlew doclava17:test
    Test: ./gradlew e2eTestAOSP
    Test: ./gradlew :doclava8:e2eTestAOSP :doclava17:e2eTestAOSP
    Merged-In: Iad2aed1940cf293f8766310b21b34cc8885feb2d
    Change-Id: Iad2aed1940cf293f8766310b21b34cc8885feb2d


This is even more recent than

   android-platform-external-doclava (9.0.0+r42-1) experimental
   -- Kai-Chung Yan <seamlik at debian.org>  Wed, 24 Jul 2019 22:27:11 +0200

(which does not build any more as well).  So from my naive point
of view there might be chances that fetching a later upstream
release (I do not understand their versioning scheme) or some
later Git commit might help.

Is there anyone who could have some educated look into this?

Kind regards
   Andreas.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011567#19
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012103#18
[3] https://android.googlesource.com/platform/external/doclava

-- 
https://fam-tille.de