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? Regards, Markus
Attachment:
signature.asc
Description: OpenPGP digital signature