Multiple port support added!

Now is possible to mock several services in only one YAML differing on port address.

Check the multiple port documentation on our README

It is now possible to mock TCP clients as well! Check the Readme for details.

Additionally, is now also possible to provide an SSLContext instance to VirtualTcpService which allows to programmatically change what protocolos, cyphers, trusted certificates, etc, will the virtual service use for SSL connections.

Now is possible to load wireshark dumps with server and client applications using same IPs (by specifying in sever addres the port), thanks to the contribution of @mdanetzky.

Update dependencies and minor fix to debugging message when connection is closed and no client packets have been received.

Change logging when client closes connection to avoid misinterpretation of the message as an error when in fact is an expected behavior.

Fix standalone help message example which had incorrect flag for specifying the server address used in dumps.

Add support for loading .pcap files and changed -w option to -a in standalone artifact since the address no longer applies to Wireshark only dumps, but also to .pcap files.

Add debugging log when connection is closed by client to ease tracing potential reasons for the client to close the connection (i.e.: waiting for the server to answer, but server not answering due to unexpected client input).

This version fixes bug reported in #1 due to read buffer size being set after flow validation (and not before), and if a flow contained a request bigger than default read buffer, wiresham would fail as detailed in reported issue.

Fix standalone artifact to be able to run it with java -jar command

Additionally:

• Add missing initialization logic in VirtualTcpServiceMain
• Add option -vv to be able to view received bytes to trace potential issues with configured flow.