Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency notations updates #559

Merged
merged 17 commits into from
Aug 2, 2022
Merged

Dependency notations updates #559

merged 17 commits into from
Aug 2, 2022

Conversation

jmfayard
Copy link
Member

@jmfayard jmfayard commented Jul 2, 2022

Hello/bonjour,

What?

Merge changes from PR about dependencies

  • Jetbrains.exposed.*
  • Ktor2.*
  • KotlinX.lincheck.*
  • KotlinX.multik.*
  • KotlinX.dataframe.*
  • KotlinX.deeplearning.*
  • Koin.navigation

Also

  • fix typo Spring.boms.springCloud
  • remove rule androidx.avigation.compose

From other PRs:

  • Kotlinx.dataframe
  • Testing.cucumber
  • Testing.assertj
  • Testing.jsonAssert
  • Testing.powermock
  • Testing.restAssured

@jmfayard jmfayard force-pushed the jetbrains-exposed branch 2 times, most recently from db48688 to f9d0640 Compare July 2, 2022 11:57
@jmfayard jmfayard changed the title ➕ Jetbrains.exposed Merge PR with dependencies Jul 2, 2022
jmfayard and others added 5 commits July 2, 2022 14:33
[Issue-538] Dependency notations for Ktor 2.0.0

[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

Co-authored-by: Brady Aiello <[email protected]>
This was referenced Jul 2, 2022
@jmfayard jmfayard requested a review from LouisCAD July 2, 2022 12:59
@jmfayard jmfayard changed the title Merge PR with dependencies Merge PRs with dependency notations Jul 2, 2022
@jmfayard jmfayard changed the title Merge PRs with dependency notations Dependency notations updates Jul 2, 2022
org.jetbrains.kotlinx..dataframe-core=version.kotlinxdataframe
org.jetbrains.kotlinx..dataframe-excel=version.kotlinxdataframe
org.jetbrains.kotlinx..dataframe=version.kotlinxdataframe
org.jetbrains.kotlinx..dataframe-arrow=version.kotlinx.dataframe
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this has never been released so the change in version name is OK

Copy link

@ConstantinCezarBegu ConstantinCezarBegu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@jmfayard jmfayard force-pushed the jetbrains-exposed branch 2 times, most recently from b4e8edc to bc52c85 Compare July 10, 2022 19:35
@jmfayard
Copy link
Member Author

Todo before merging: move the data frame Gradle Plugin to the Kotlinx namespace

Kotlin/dataframe#128 (comment)

@LouisCAD
Copy link
Member

Also, renaming the branch before merging to avoid a misleading history.

# Conflicts:
#	plugins/dependencies/src/test/kotlin/de/fayard/refreshVersions/BundledDependenciesTest.kt
@jmfayard
Copy link
Member Author

Also, renaming the branch before merging to avoid a misleading history.

The name of the branch is not part of the git history and git can't rename a branch so I skip this part

@jmfayard
Copy link
Member Author

I fixed dataframe to its new kotlinx plugin id.
@LouisCAD any questions before I merge the PR?

@LouisCAD
Copy link
Member

The merge commit includes the name of the branch, and you can rename a branch in git . You'll only need to submit a superseding PR pointing to the newly pushed branch.

@jmfayard
Copy link
Member Author

And then I loose the discussion.

But more importantly that git gymnastic provides no value to the world so I would rather focus on things that do, like reviewing, merging and releasing.

@brady-aiello
Copy link
Contributor

@LouisCAD what do you think? Does branch renaming offer more benefit than that of merging sooner and having less PR indirection?

@jmfayard
Copy link
Member Author

jmfayard commented Aug 2, 2022

In the future we want to do small and fast PRs.
Currently there are two huge stale PRs that gets in the way.
I'm merging this one so that there is only one left :)
Instead I created this issue for dependency notations that needs to be reviewed one last time before release

#568

@jmfayard jmfayard merged commit a6e58b1 into main Aug 2, 2022
@jmfayard jmfayard deleted the jetbrains-exposed branch August 2, 2022 07:42
Comment on lines -13 to +14
io.kotest.extensions:kotest-extensions-*
^^^^^^.^^^^^^^^^^.^
io.kotest.extensions:*
^^^^^^.^^^^^^^^^^
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@LouisCAD I think so, all dependencies inside io.kotest.extension that are maintained have the same version, 1.2.5
Other kotest dependencies are in another namespace

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's ask @sksamuel if he agrees with the fact that everything non version 1.2.5 (so everything but the arrow extension) has been discontinued.

Screenshot 2022-08-17 at 18 56 08

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi,

The 1.0.1 konform is current. The arbs is current. The pitest is current.

Basically, some external modules moved to io.kotest.extensions instead of io.kotest and had their versions reset, around 18 months ago.

If you have a central list I can check them over.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants