You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the attached patch, one may discard the classes that use it, but perhaps you will want to rework the code in the classes instead of removing them. I know for instance that picard is using part of them -- anyway, at the moment I will also remove the 2 concerned classes in picard for the same reason.
Best wishes,
Pierre
The text was updated successfully, but these errors were encountered:
@pgrt I've actually just started looking into what we need to do to migrate these obsolete doclet(s) and remove the dependencies on deprecated APIs. It may take some time though, and we can't remove the classes in the interim because we have downstream projects that rely on these for both documentation and code generation.
Thanks so much for your answer to my concern. I plainly understand the constraint linked to downstream projects.
My sole intent was to help by investigating the issue from my side, but of course you know far more about barclay than I do!
Please feel free to close the issue is it more convenient for your workflows.
Hello,
In Debian we are getting prepared to adopt OpenJDK 17 as the new standard soon (?).
So I built barclay against it and I met issues as the com.sun.javadoc package will disappear -- it is already deprecated in sooner JDKs.
com_sun_javadoc_removal_in_openjdk17.txt
With the attached patch, one may discard the classes that use it, but perhaps you will want to rework the code in the classes instead of removing them. I know for instance that picard is using part of them -- anyway, at the moment I will also remove the 2 concerned classes in picard for the same reason.
Best wishes,
Pierre
The text was updated successfully, but these errors were encountered: