Netty implementation of DockerCmdExecFactory#397
Conversation
Conflicts: src/main/java/com/github/dockerjava/api/command/ExecStartCmd.java src/main/java/com/github/dockerjava/api/command/InspectContainerResponse.java src/main/java/com/github/dockerjava/core/command/ExecStartCmdImpl.java
|
Resorted imports 😱 After this PR i will try reflect in http://checkstyle.sourceforge.net/config_imports.html#ImportOrder |
There was a problem hiding this comment.
Latest netty stable release 4.0.33.FINAL is missing some features that are needed here. It might be possible to backport it from 4.1.0.Beta7 but as it is an experimental implementation of DockerCmdExecFactory I think its OK for now.
|
Oh, crazy PR :) |
There was a problem hiding this comment.
reformat styling? case intend.
|
Too big for understanding, i propose merge it and test from master. I can try to use new implementation in my reference jenkins plugin. |
|
@KostyaSha This PR duplicates mostly the Internally I tried to imitate the JAX-RS API for two reasons:
|
|
I asked from support perspective :) Feel free to merge as soon as you think that it's enough. |
|
I'm not sure if I should merge as some important features are still missing. See initial comment please. WDYT? |
|
If missing features not breaking existed connection factory, then merge of course. |
|
Either i will be unable rework tests/poms. |
|
Also please put |
Netty implementation of DockerCmdExecFactory
This contains an additional (experimental) implementation of
DockerCmdExecFactory. It supports http connection hijacking that is needed for passing STDIN to the container which is a long awaited feature (#253).Currently there are three missing features compared to the current Apache HttpClient based impl:
Any feedback is really appreciated!