ject: Re: broken test in maven-javadoc-plugin
> To: "Maven Developers List"
> Date: Saturday, July 30, 2011, 7:22 AM
> This sounds VERY much like the
> problem Richard Vowles reported awhile back which is solved
> by ungrading Maven to use Aether 1.12.
>
> The
This sounds VERY much like the problem Richard Vowles reported awhile back
which is solved by ungrading Maven to use Aether 1.12.
The problem lies in having some artifcts downloaded directly, some from a
mirror. Maven generates a metadata file which includes a references to the
upstream reposi
yes, I tried too and couldn't find (then chose to continue on m-site-p...), but
your conclusion is really plausible
I tried on every CI failures, fixed what I could fix, but actual failures are
really hard to fix (AFAIK, were the same on previous Sonatype's CI, then there
is really some logic i
it more work, and I'd rather do that in an integration test
> and not via a unit test.
Yup, that's the way to go. I found the tests overly complicated for
being just unit tests.
>
> LieGrue,
> strub
>
> --- On Fri, 7/29/11, Dennis Lundberg wrote:
>
>> F
unit test.
LieGrue,
strub
--- On Fri, 7/29/11, Dennis Lundberg wrote:
> From: Dennis Lundberg
> Subject: Re: broken test in maven-javadoc-plugin
> To: "Maven Developers List"
> Date: Friday, July 29, 2011, 9:59 PM
> Hi Mark
>
> I spent a couple of hour
Hi Mark
I spent a couple of hours debugging this earlier this week.
Unfortunately I wasn't able to crack it. But I find your conclusion very
plausible.
On 2011-07-29 16:22, Mark Struberg wrote:
> Hi!
>
> This is a sum-up of my last 5 hours of debugging.
>
> Currently there is a failing test in
lte
> Subject: RE: broken test in maven-javadoc-plugin
> To: dev@maven.apache.org
> Date: Friday, July 29, 2011, 4:57 PM
>
> I discovered the same issue. The problem didn't show itself
> with a dirty target-folder, but after a "mvn clean test" it
> was easy to repr
t; Date: Fri, 29 Jul 2011 15:22:46 +0100
> From: strub...@yahoo.de
> Subject: broken test in maven-javadoc-plugin
> To: dev@maven.apache.org
>
> Hi!
>
> This is a sum-up of my last 5 hours of debugging.
>
> Currently there is a failing test in the maven-javadoc-plugin
Hi!
This is a sum-up of my last 5 hours of debugging.
Currently there is a failing test in the maven-javadoc-plugin:
JavadocReportTest#testProxy()
This test fails since the last commit but I actually think it only ever worked
by accident. It did rely on a commons-logging-1.0.4.pom which got re
