Thanks, that worked! I think it's looking in ~/.m2 because we've added mavenLocal as a maven repository in our gradle build. I must have at some point sucked down jetty into my local maven repo.
It seems like it still should have worked, but maybe there is a gradle bug here with a local maven repository and a classifier on the artifact. -Dan On Mon, Feb 8, 2016 at 2:29 PM, Jens Deppe <jde...@pivotal.io> wrote: > I wonder why it's trying to resolve from your maven repo and not ~/.gradle? > Can you try after deleting > /home/dsmith/.m2/repository/org/eclipse/jetty/jetty-http/9.3.6.v20151106? > > --Jens > > On Mon, Feb 8, 2016 at 2:23 PM, Dan Smith <dsm...@pivotal.io> wrote: > > > Anyone else hitting this after the merge of the modules? It looks like > it's > > trying to find a jetty-http-tests.jar and failing for some reason. > > > > This is with c8c26e6. > > > > -Dan > > > > > > >open> ./gradlew clean build > > ... > > > > What went wrong: > > Could not resolve all dependencies for configuration > > ':extensions/gemfire-modules-session:testCompile'. > > > Could not find jetty-http-tests.jar > > (org.eclipse.jetty:jetty-http:9.3.6.v20151106). > > Searched in the following locations: > > > > > > > file:/home/dsmith/.m2/repository/org/eclipse/jetty/jetty-http/9.3.6.v20151106/jetty-http-9.3.6.v20151106-tests.jar > > >
