Use Netty5 Alpha6-SNAPSHOT in order to avoid slf4j conflicts. #19
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation:
This project is currently depending on Netty 5.0.0-Alpha5.
Let's depend on Netty Alpha6-SNAPSHOT, this seems to avoid dependency conflicts while adapting ReactorNetty to latest Netty Alpha6-SNAPSHOT.
Modification:
Modified the pom.xml in order to depend on 5.0.0.Alpha6-SNAPSHOT instead of 5.0.0.Alpha5
Also moved codec-haproxy/src/main/resources/META-INF/native-image/io.netty.contrib/netty-codec-haproxy/reflect-config.json to codec-haproxy/src/main/resources/META-INF/native-image/io.netty.contrib/netty-codec-haproxy/generated/handlers/reflect-config.json
Result:
This allows to avoid some dependency conflicts while adapting ReactorNetty to the latest Netty Alpha6-SNAPSHOT