mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <ted.dunn...@gmail.com>
Subject Re: Build failed in Hudson: Mahout-Quality #593
Date Mon, 31 Jan 2011 17:33:31 GMT
I checked on infra early in the weekend and they said that this had to do
with migrating to more recent maven versions.

The black-listing likely only affects timed builds.  Triggered builds
shouldn't be affected.

What does anybody say about temporarily disabling clover?

On Mon, Jan 31, 2011 at 8:48 AM, Sean Owen <srowen@gmail.com> wrote:

> I also see talk of "project is banned due to previous failures". Maybe we
> also need to be un-blacklisted? Either could be the issue.
>
> On Sun, Jan 30, 2011 at 4:24 PM, Isabel Drost <isabel@apache.org> wrote:
>
> > On 29.01.2011 Ted Dunning wrote:
> > > > [ERROR] Failed to execute goal
> > > >
> > com.atlassian.maven.plugins:maven-clover2-plugin:2.6.3:instrumentInternal
> > > > (default-cli) on project mahout: Failed to load resource as file
> > > > [/clover.license]: Could not find resource '/clover.license'. ->
> [Help
> > 1]
> >
> > Looks like it can't find the clover license to build the code coverage
> > reports.
> > Did some configuration on Hudson with respect to the location of Apache's
> > clover
> > license change?
> >
> > Isabel
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message