[Issue-538] Dependency notations for Ktor 2.0.0 #542
Closed
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
[Summary] Ktor 2.0.0 renames a significant number of dependencies, adds new ones, and moves some previously available ones from 1 module into another. It makes sense to make a separate repo for Ktor 2. The full list of artifact changes between 1.6.x and 2.0.0 can be found here: https://ktor.io/docs/migrating-2.html [Fix] Create a Ktor2 dependency group, and include all dependencies listed in the docs: Ktor 2.0.0: https://api.ktor.io/index.html Ktor 1.6.8: https://api.ktor.io/older/1.6.8/index.html [Testing] - Run project tests - publish to maven local, and consume locally
|
Example usage:
|
|
@LouisCAD pinging to see your thoughts |
|
Thanks @brady-aiello I have merged your changes via #559 |
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.
What?
Resolves #538
Adding dependency notations for Ktor 2.0.0
Why?
Ktor 2.0.0 renames a significant number of dependencies, adds new ones, and moves some previously available ones from 1 module into another. It makes sense to make a separate repo for Ktor 2. The full list of artifact changes between 1.6.x and 2.0.0 can be found here:
https://ktor.io/docs/migrating-2.html
How?
Create a Ktor2 dependency group, and include all dependencies listed in the docs:
Ktor 2.0.0: https://api.ktor.io/index.html
Ktor 1.6.8: https://api.ktor.io/older/1.6.8/index.html
Testing?