Feature/upgrade to latest junix socket dependency#1159
Feature/upgrade to latest junix socket dependency#1159KostyaSha merged 7 commits intodocker-java:masterfrom padas2:feature/upgrade-to-latest-junix-socket-dependency
Conversation
|
Is kohlschutter/junixsocket#31 relevant? Perhaps with version 2.1.0 (or maybe 2.1.2 to get the latest), we no longer need to monkey patch junixsocket here and can delete https://github.com/docker-java/docker-java/blob/master/src/main/java/org/newsclub/net/unix/AFUNIXSocketImpl.java ? And if we do, I bet we don't need AFUnixSocketException either. |
Codecov Report
@@ Coverage Diff @@
## master #1159 +/- ##
=========================================
- Coverage 58.64% 58.4% -0.24%
=========================================
Files 451 450 -1
Lines 8893 8715 -178
Branches 545 525 -20
=========================================
- Hits 5215 5090 -125
+ Misses 3382 3349 -33
+ Partials 296 276 -20
Continue to review full report at Codecov.
|
|
|
Removed AFUNIXSocketImpl and AFUNIXSocketException classes. Compilation passed. Waiting for travis build results. |
|
all socket based tests failed... |
CHANGELOG.md
Outdated
| Change Log | ||
| === | ||
|
|
||
| ## 3.1.0-rc-9 |
There was a problem hiding this comment.
3.1.1 even already released....
There was a problem hiding this comment.
Are the socket based test failures because of these changes ?
There was a problem hiding this comment.
no, released version passing unix/tcp tests (beside 2 configurations). This PR fails because amd64 native libs not found something
There was a problem hiding this comment.
I see this error
Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.newsclub.net.unix.NativeUnixSocket
But I believe this class should be available
|
|
pom.xml
Outdated
|
|
||
| <bouncycastle.version>1.60</bouncycastle.version> | ||
| <junixsocket.version>2.0.4</junixsocket.version> | ||
| <junixsocket.version>2.1.0</junixsocket.version> |
There was a problem hiding this comment.
| <junixsocket.version>2.1.0</junixsocket.version> | |
| <junixsocket.version>2.1.2</junixsocket.version> |
Does this by chance make the failure go away?
There was a problem hiding this comment.
Please update to 2.2.0 (the latest version)
|
|
||
| <bouncycastle.version>1.60</bouncycastle.version> | ||
| <junixsocket.version>2.0.4</junixsocket.version> | ||
| <junixsocket.version>2.1.2</junixsocket.version> |
There was a problem hiding this comment.
| <junixsocket.version>2.1.2</junixsocket.version> | |
| <junixsocket.version>2.2.0</junixsocket.version> |
There was a problem hiding this comment.
Let's see if this gets us farther. Also see kohlschutter/junixsocket#31 (comment) for more suggestions.
There was a problem hiding this comment.
Yes, please directly update to 2.2.0. There's no point in moving anymore.
Upgrading the version of junixsocket dependencies
This change is