I'm on 3.5 and not having issues with it. On Wed, May 3, 2017 at 2:19 PM, Otto Fowler <ottobackwa...@gmail.com> wrote:
> Did we change the requirements for pre-commit testing to run the command > that way? > I did a commit this morning with the old command. > > > On May 3, 2017 at 14:04:32, Otto Fowler (ottobackwa...@gmail.com) wrote: > > > git checkout -b whyyounowork apache/master > > same issue locally > > > > > On May 3, 2017 at 13:46:14, Justin Leet (justinjl...@gmail.com) wrote: > > Is it just that one branch that's failing, or is it also master? To try > to narrow things down. > > On Wed, May 3, 2017 at 1:43 PM, Michael Miklavcic < > michael.miklav...@gmail.com> wrote: > >> Hahaha, I can't imagine why you wouldn't run that command ¯\_(ツ)_/¯ >> Yeah, mvn clean package or mvn clean install are what I typically run. >> (Install has the added benefit that if you've modified only files in one >> module like metron-parsers, you can choose to build only that project bc >> it >> will grab dependency artifacts from your local cache). I wanted to see if >> we could isolate the problem. >> >> On Wed, May 3, 2017 at 10:51 AM, Otto Fowler <ottobackwa...@gmail.com> >> wrote: >> >> > I am going to be honest, >> > I don’t usually build locally with : mvn -q -T 2C -DskipTests install >> && >> > mvn -q -T 2C jacoco:prepare-agent surefire:test@unit-tests && mvn -q >> > jacoco:prepare-agent surefire:test@integration-tests && mvn -q >> > jacoco:prepare-agent test --projects metron-interface/metron-config && >> > build_utils/verify_licenses.sh >> > >> > I build with mvn package >> > >> > I’m trying it now. >> > >> > >> > On May 3, 2017 at 12:19:34, Michael Miklavcic ( >> michael.miklav...@gmail.com) >> > wrote: >> > >> > Also Otto, are you able to build locally with that branch and same merge >> > with master? >> > >> > On Wed, May 3, 2017 at 9:51 AM, Justin Leet <justinjl...@gmail.com> >> > wrote: >> > >> > > 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] >> > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > >> > >> > >