Validation in 1.0.13 test inconsistency between IntelliJ-IDE and Maven-Surefire

[Sören van Dongen]

Unlike 1.0.12 the new 1.0.13 release fails for my projects when validating during maven-surefire test.

In IntelliJ-IDE the tests are working correctly, during maven-surefire the API path resolution fails though.

e.g.: '/myservice/services/Customer'

com.atlassian.oai.validator.restassured.SwaggerValidationFilter$SwaggerValidationException: Validation failed. [ERROR] No API path found that matches request

[James Navin]

There was a bug in the v1.0.13 release where the API path prefix wasn't used correctly in operation lookup (see #40). I wonder if this could be caused by that? Although it sounds more like a classpath issue (maybe a stale classpath in IntelliJ still using 1.0.12?)

Could you try bumping to v1.0.14 and see if that fixes the problem. If not I'll look deeper.

Cheers.

[James Navin]

@QuasiSodo - is this still a problem? Or did the version bump fix things?

Cheers.

[Sören van Dongen]

Hey,

the problem was resolved with the 1.0.14. release.

You can close if you want!

[James Navin]

Awesome - thanks!