This repository has been archived by the owner on Feb 19, 2021. It is now read-only.
Update junixsocket to v2.2.0 to support ARM, Win10 #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updates junixsocket to version 2.2.0, which adds the following to its supported platforms: Linux ARM 32-bit and 64-bit (e.g., Raspberry Pi), and Windows 10 AMD64. This change seeks to resolve issues such as docker-java#1174
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates junixsocket to version 2.2.0, which adds the following to its supported platforms: Linux ARM 32-bit and 64-bit (e.g., Raspberry Pi), and Windows 10 AMD64.
This change seeks to resolve issues such as docker-java#1174
As a quick workaround to the Maven surefire/failsafe plugins throwing "java.lang.noClassDefFoundError: javax/xml/bind/JAXBexception" when trying to perform tests during a simple "mvn clean install," I downgraded those to 2.18.1 as in spring-projects/spring-boot#6254 (comment) and checked that the tests still ran.