[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Javadoc -link makes broken links if module name matches package name

On Wed, Feb 13, 2019 at 10:07:34PM +0100, Markus Koschany wrote:
> Hi,
> Am 26.01.19 um 20:07 schrieb tony mancill:
> [...]
> > 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.
> I have updated the maven-javadoc-plugin package to the latest Git
> snapshot and pushed the changes. An update of libplexus-languages-java
> was also necessary (currently in experimental) and tony already took
> care of it. I also had to add a compatibility patch for Debian's version
> of maven-artifact-transfer. A new upstream release just because of some
> minor refactoring seemed to be not the best way forward during the freeze.
> Now I would have expected that libparanamer-java (#920750) just built
> fine again but it doesn't. According to README.source in
> maven-javadoc-plugin maven2-core (should be src:maven?) must be updated
> as well. I'm not sure what button I have to press to make this work
> right now. Any ideas?

Hi Markus,

We independently executed identical experiments, which I'm glad for,
because I would have wanted some external verification before uploading
any of this to unstable.  (I started building the r-build-deps of
libplexus-languages-java using ratt, but my laptop isn't the best place
to build 559 packages and many packages are FTBFS right now anyway due
to the javadoc problems.)

I believe the comment in debian/README.source about updating src:maven
is simply out of date.  I don't see any (obvious) versioned references
to maven-javadoc-plugin in the current maven source package.

So I'm not sure what the next step is, other than continuing to watch
commits to upstream maven-javadoc-plugin and see if I can figure out why
3.1.0~pre0-$foo doesn't work in our environment. 

Or now that we're into the freeze, do we want to talk about actions with
more far-reaching consequences?

Any thoughts on whether we should focus on fixing javadoc generation or
look at other ways to mitigate the FTBFS?


Attachment: signature.asc
Description: PGP signature

Reply to: