On Sat, 24 Sept 2022 at 01:16, Gary Gregory <garydgreg...@gmail.com> wrote:
> I never build releases on Java 17, only Java 8 these days. Could this be
> addressed in a profile?
>
But we test on all LTS versions. This breaks the JDK 17 build on RNG on
certain platforms.
Maven configuration is harder to remove than add when using profiles. I
think the links section is not required as it only contains standard links
added correctly by the javadoc plugin. Without it the javadoc still renders
as expected.
For example if I remove the section from CP, and then remove the duplicate
links added in the commons-lang POM:
<links>
<link>https://commons.apache.org/proper/commons-text/apidocs</
link>
<link>https://docs.oracle.com/javase/8/docs/api</link>
<link>https://docs.oracle.com/javaee/6/api</link>
</links>
When you render the javadoc for [lang] all the links to JDK objects still
work. Here the only extra link required is the one to [text] (although that
also seems unnecessary as no objects from [text] are ever imported; the
links are hard coded as anchors in the source files of the lang3.text
package).
Alex
