Feedback for refreshVersionsMigrate #396
Replies: 9 comments 14 replies
-
|
First impressions:
(notice the extra space on okio) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Colton! |
Beta Was this translation helpful? Give feedback.
-
Super long stacktrace (Click to expand)not sure if it internet connection or the robolectric plugin problems, but failed to compile after successfully executed the
|
Beta Was this translation helpful? Give feedback.
-
|
Looks like the |
Beta Was this translation helpful? Give feedback.
-
|
will try to remove it first |
Beta Was this translation helpful? Give feedback.
-
|
solved, by removing the |
Beta Was this translation helpful? Give feedback.
-
|
issue found, regarding the firebase crashlytics plugin unresolved 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
Looks like this is not related to task |
Beta Was this translation helpful? Give feedback.
-
|
Will further investigate if our project config requires extra workaround |
Beta Was this translation helpful? Give feedback.
-
|
In the meantime, we remove the |
Beta Was this translation helpful? Give feedback.
-
|
related: #405 |
Beta Was this translation helpful? Give feedback.
-
|
Hello! I just tried to migrate a project that I freshly created from Android Studio BumbleBee Canary 9, selecting "Empty Compose Activity", and there was 2 problems:
@jmfayard Can you try to do it on your end after you commit the initial project in git to be able to easily revert as you walk down the why? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
This is a great new feature, I also like |
Beta Was this translation helpful? Give feedback.
-
|
Android Studio Arctic Fox | 2020.3.1 Patch 3 After a few basic tests of refreshVersionsMigrate, I am pleasantly surprised at how well it works. I did find one situation that could be improved but could also be expected behavior. If you use .+ for versioning in a dependency, it just leaves it as it is. For example:
My test build.gradle.kts also has a few lines that reference versions, for example: The migration updates the compose dependencies like so: Is there any current feature that would allow reference to the compose version? Maybe this is more of a feature request and should be a separate post. My initial thought was it could be something like: |
Beta Was this translation helpful? Give feedback.
-
|
@codeversed thank you for your feedback. Regarding your last paragraph, yes, you can reference the compose version See |
Beta Was this translation helpful? Give feedback.
-
|
@codeversed Since version 0.51.0, we have a nice way to handle compose compiler version: https://twitter.com/Louis_CAD/status/1585016939289903105?t=Qd0lXsdME6yG7aNmMTk9CQ&s=19 |
Beta Was this translation helpful? Give feedback.
-
|
I get this error when running
It only happens when there is no |
Beta Was this translation helpful? Give feedback.
-
|
@natanfudge |
Beta Was this translation helpful? Give feedback.
-
|
Gradle 7.5.1 and refreshVersions 0.50.0 |
Beta Was this translation helpful? Give feedback.
-
|
I think we fixed the issue since then, sorry for not circling back. Can you confirm it doesn't fail like that now with latest version @natanfudge? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @natanfudge! Thanks for the plugin, I just had this problem, has anything similar happened? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I have just noticed something If you run: and then It fails with a message about not being able to find `gradle/libs.versions.toml'. If I have done mode=VersionsPropertiesOnly then it doesn't generate libs.versions.toml, so why fail then on refreshVersion? Creating an empty file fixes it but just wondering if this is the correct behaviour. Thanks |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Update: for feedback on Gradle Versions Catalog, lease use discussion
Feedback on Gradle Versions Catalog support? #592
Migrating an existing project to refreshVersions used to be cumbersome.
Existing dependencies were ignored because they didn't use the version placeholder
_.Replacing the harcoded version with the version placeholder was not enough, because it had the major side effect to upgrade all your dependencies to whatever was the latest version available.
refreshVersionsMigrate new in refreshVersions 0.11.0
If you are using refreshVersions 0.11.0 or later...
plugins { // See https://jmfayard.github.io/refreshVersions id("de.fayard.refreshVersions") version "0.11.0" }there is a new task called refreshVersionsMigrate that takes care of this automatically:
versions.propertieswith the current version of all dependenciesbuild.gradle(.kts)and other known files likelibraries.gradleso that the version placeholder_is used everywhere.$ ./gradlew refreshVersionsMigrate > Task :refreshVersionsMigrate modified: versions.properties modified: build.gradle.kts modified: gradle/libraries.gradle To find available updates, run this: ./gradlew refreshVersionsAt that point you probably want to have a look at the
git diffto see what was changed.Did it work for you?
Please try it out in one of your projects and gives us feedback of what worked and what didn't worked.
Beta Was this translation helpful? Give feedback.
All reactions