More javadoc problems triggered by Automatic-Module-Name.
https://ci-builds.apache.org/job/Jena/job/Jena_Development_Deploy/63/
[ERROR] Exit code: 1 - error: module org.apache.jena.dboe.trans.data
reads package jena from both org.apache.jena.text and org.apache.jena.cmds
(yes, an overlapping package that shouldn't)
I'll take a look as soon as I can.
Andy
On 08/01/2021 17:38, Andy Seaborne wrote:
Status: JENA-2022
One slight problem - on travis-ci.org, the Java11 system is 11.0.2 which
hits a javadoc problem
https://bugs.openjdk.java.net/browse/JDK-8212233
(it says Java12 but it applies to 11.0.1, and 11.0.2, not 11.0.0, the GA
release, or 11.0.3 or later, then 12.0.0, 12.0.1)
I think this is triggered by cross links in Java source code from one
module to another when the modules have Automatic-Module-Name. The fixes
mentioned don't work for Jena.
See also https://issues.apache.org/jira/browse/MJAVADOC-555
There are no problems building with the default Java11 on my machine
(11.0.9)
For now I have switched off javadoc production in the .travis.yml file.
It should be OK on ASF Jenkins because there, we control the JDK (and
only 11.0.9 in various forms is available anyway).
What the travis file does for us is that PRs automatically get a check
applied of running the build with the PR at travis (it can take a while
to get scheduled and run). We didn't ask INFRA for this - recent
infrastructure changes mean it just happens.
Andy
