Open zahariaca opened 6 years ago
This is unexpected, as the same code should be executed in both cases.
However, the classpath setup is subtly different in Eclipse (with M2E) vs command line Maven, as Eclipse allows project dependencies to be resolved directly when the Maven version numbers match, such as develop-SNAPSHOT
, whereas command line Maven requires the dependent project to first execute mvn install
causing the JAR to be published to the local ~/.m2/repository
before it can be resolved by a dependent project.
Let's first see if we have enough information to reproduce the reported issue.
While writting some scripts for a request - response, I noticed that my test would pass in the IDE, but when I would do a Maven build it would fail.
After some careful analysis I noticed that I had used
http.header
for one of the write/read requests, instead ofhttp:header
, this for some reason would make the test pass in the IDE and fail in Maven.This seems like a bug in the k3po logic.
Log: log.txt
Scripts: handshake.response.rpt.txt handshake.request.rpt.txt