Open anuraaga opened 2 years ago
Context on the change in javadoc
https://bugs.openjdk.java.net/browse/JDK-8259530
It looks like there is undocumented option --legal-notices=none
which can restore the old behavior. I don't know which is more compliant :) Appreciate any advice.
@open-telemetry/java-maintainers @open-telemetry/java-instrumentation-maintainers: the OpenJDK bug appears to be fixed. Can you confirm?
As far as I can tell the openjdk bug was provided only for context. Resolution of that bug does not affect the original question raised in this issue, which is that portions of the javadoc jar content are not apache licensed. Besides the html file javadoc jar includes a bunch of js, some of these js files are licensed under GPLv2 with Classpath exception.
I noticed that the javadoc jars we publish have a
legal
folder including a GPLv2 with Classpath exception licensehttps://javadoc.io/doc/io.opentelemetry/opentelemetry-context/latest/legal/LICENSE
This has been the case since v1.7, when we updated our build toolchain from Java 11 to 17 which appears to have that behavior.
I think our artifacts are generally supposed to be Apache-2.0 so want to confirm this is ok. I don't think there is any setting, it just seems to be reality since Java 17.