Gradle Memory Manager enters a loop after first execution on using 'swagger-request-validator', version: '1.0.17' with pact 3.4.0

Issue #47 closed
Richa Agarwal created an issue

I am testing Swagger validator with pact using sample 'petstore' swagger file. As soon I upgraded by build.gradle to use the combination of 'swagger-request-validator', version: '1.0.17' with pact 3.4.0, Gradle Memory Manager entered a loop upon execution.

Before this when I was using pact 3.3.x with swagger-request-validator 1.0.17 the execution was working fine (atleast memory manager not entering a loop).

Build file snippet below. Also attaching the stacktrace on running 'gradle build' from intelliJIdea terminal.

dependencies { compile 'org.codehaus.groovy:groovy-all:2.3.11' testCompile group: 'junit', name: 'junit', version: '4.11' testCompile group: 'junit', name: 'junit', version: '4.12' compile group: 'com.atlassian.oai', name: 'swagger-request-validator-pact', version: '1.0.17' compile group: 'au.com.dius', name: 'pact-jvm-provider-junit_2.11', version: '3.4.0' compile group: 'au.com.dius', name: 'pact-jvm-consumer-junit_2.11', version: '3.4.0' compile 'org.apache.httpcomponents:fluent-hc:4.5.3' compile group:'com.github.rest-driver',name:'rest-client-driver',version:'1.1.45' compile group:'org.slf4j',name:'slf4j-api',version:'1.7.23' compile group:'org.slf4j',name:'slf4j-simple',version:'1.7.23' compile group:'commons-collections',name:'commons-collections',version:'3.2.1' compile group: 'io.rest-assured', name: 'rest-assured', version: '3.0.0' compile group: 'com.atlassian.oai', name: 'swagger-request-validator', version: '1.0.17' }

Comments (1)

  1. Log in to comment