I'm also curious if it works if you change the two 'jacoco:prepare-agent'
to 'org.jacoco:prepare-agent'. Master has built off of this fine, so I'm
wondering if there's a difference in that build that breaks the plugin
resolution.

On Wed, May 3, 2017 at 11:35 AM, Ryan Merriman <merrim...@gmail.com> wrote:

> You might want to try clearing the mvn cache.  I've had travis get into a
> bad state before because of corrupt maven artifacts.
>
> On Wed, May 3, 2017 at 10:26 AM, Otto Fowler <ottobackwa...@gmail.com>
> wrote:
>
> > https://travis-ci.org/ottobackwards/incubator-
> metron/builds/228364894?utm_
> > source=email&utm_medium=notification
> >
> > On May 3, 2017 at 11:12:15, Justin Leet (justinjl...@gmail.com) wrote:
> >
> > > Jacoco is introduced from
> > > https://github.com/apache/incubator-metron/pull/459.
> > >
> > > I'm not sure why you'd be getting a plugin error for it though, because
> > > it's available in the standard repos and I was able to build off a
> > > completely clean maven cache (and Travis has been able to build it as
> > > well).
> > >
> > > What exactly you were running?
> > >
> > > On Wed, May 3, 2017 at 11:03 AM, Otto Fowler <ottobackwa...@gmail.com>
> > > wrote:
> > >
> > > Anyone know what this is?
> > >
> > > [ERROR] No plugin found for prefix 'jacoco' in the current project and
> in
> > > the plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
> available
> > > from the repositories [local (/home/travis/.m2/repository), central (
> > > https://repo.maven.apache.org/maven2)] -> [Help 1]
> > >
> > >
> >
>

Reply via email to