Hi Ole, On Fri, Jan 25, 2019 at 08:50:29PM +0100, Ole Streicher wrote: > Hi Matthias, > > on a number of packages, javadoc now fails, which is reported by a > number of bugs. Since you mentioned that this is not a bug in the JDK, > could you give a hint what the problem is? The error message is a bit > mystic, at least to me. And the openjdk commit also does not enlighten me. > > It a bug in the individual packages or one in javahelper? And what > should be done to fix it? > > Best > > Ole > > On 25.01.19 09:26, Matthias Klose wrote: > > so this is not an openjdk error, and should be fixed in the pacakges > > itself. See > > > > 8211916: Javadoc -link makes broken links if module name matches package > > name > > http://hg.openjdk.java.net/jdk-updates/jdk11u/rev/66a53d6047d1 > > > > see the -source 8 passed in the tests.
I'm trying to peel the onion and believe that this is a problem in the maven-javadoc-plugin package. I found the same issue for a project outside of Debian, for example [1], which refers to a JIRA ticket for that plugin [2]. There is a commit [3] referencing that JIRA on the master branch of maven-javadoc-plugin. I would like to try cherry-picking the fix onto our current version of maven-javadoc-plugin to see if it resolves our issue. Or if that gets too complicated, we could look into updating to a snapshot of 3.1.0 (our version would 3.1.0~foo), since it looks like all of these commits will be part of 3.1.0 [4]. I'm not sure how much time I'll have to dedicate to this over the weekend and so would be happy if someone fixes it before I get to it. Cheers, tony [1] https://github.com/oracle/opengrok/issues/2629 [2] https://issues.apache.org/jira/browse/MJAVADOC-555 [3] https://github.com/apache/maven-javadoc-plugin/commit/c3e96e622d4ce0ea6e3ba7fcff9cbd2c555ae716 [4] https://github.com/apache/maven-javadoc-plugin/commit/8e6622f39392577298fa71b02b0194ade70fceb9
signature.asc
Description: PGP signature
