On Fri, Feb 15, 2019 at 08:22:14PM +0100, Markus Koschany wrote:
> Am 15.02.19 um 15:42 schrieb tony mancill:
> [...]
> > Any thoughts on whether we should focus on fixing javadoc generation or
> > look at other ways to mitigate the FTBFS?
>
> Like burning all those -doc packages? :)
>
> In my op
Hi tony!
Am 15.02.19 um 15:42 schrieb tony mancill:
[...]
> 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
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, fo
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
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
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.
I
6 matches
Mail list logo
