So a tip I figured out by trial and error: My recommendation is to always add -"core" to to artifact ids like 'androidx.compose.ui:ui' that have a package name that will be part of other imports. That way auto complete plays nicely and it actually improves the wizard tooltip accuracy when you do that by allowing you to click "androidx.compose.ui.core" in your gradle files and it properly auto click through to the correct dependency. This works so nicely since Import Names and even Version Names don't have to 1:1 match the artifact IDs, and you can use "-base", or any other suffix you like to make it that auto-complete works nicely all the time, etc.
@johngray28757 ай бұрын
You can also have a bundles section, where you set up way add multiple dependencies will a single line. It's very handy for things you always use together. Like all the compose dependencies.
@Narazgul7 ай бұрын
In addition to your content I'm also making use of "bundles" there. For example all the compose dependencies could be bundle together and instead of 4 implementation you only got 1 left in your gradle file. But that's of course an indivuall preference 🙂
@PhilippLackner7 ай бұрын
Haven't found much use for that yet, since in a single module app, you'll have to add them all to your Gradle file anyways and in a multi-module project, I got used to work with convention plugins which also didn't make me feel like that was necessary. Still thanks for adding though!
@mytubekt7 ай бұрын
Bundles are very nice approach, we are also using to group dependencies and use them as single line in gradle file.
@rishabh-more7 ай бұрын
@@PhilippLackner I can't believe it. Bundles make my life soo much easier, even if I'm also using Convention Plugins. Just wrap all the multiple dependencies for one library such as Koin or Retrofit and then just call your bundle in one line. It's soo good!!
@romanosp93496 ай бұрын
Will you make a video combining versionCatalog with buildSrc ?
@嘿嘿嘿-z1v27 күн бұрын
Now I'm using Android Studio Koala and it already appled the version catalogs for the library dependencies. Thanks for your information 6 months ago :)
@abada-s7 ай бұрын
I hope to see a new video about buildSrc module that supports this toml file
@vighnesh1537 ай бұрын
This is nice and definitely makes it easier to manage dependencies for large projects. When I look at build scripts that use version catalogs, I just find it a bit hard to build a mental model of dependencies. Before version catalogs, it was easier on the eyes to figure out what "groups" we are using in our application.
@itssinghankit7 ай бұрын
They are just increasing complexity, adding dependency is much easier in other frameworks, this is the thing which i don't like about android.
@gabrielabanica6153 ай бұрын
Something is not clear for me. For example, if we use timber library we can use : timber="5.0.1" timber = { group = "com.jakewharton.timber", name="timber",version.ref="timber"} timber = { module = "com.jakewharton.timber:timber",version.ref="timber"} ? It is the same thing if we use group or module? I don't understand the difference between them.
@vitalijuskolinko90117 ай бұрын
Thank you for great video! :) I'm trying to migrate from buildSrc Deps object in KMM to that catalogs ;) P.S.: Don't forget to update KMM Translator ;) P.S.S.: The name of lib in 21 line should be androidx-compose-ui-test-manifest ;)
@barfyman3Six27 ай бұрын
I'm been using this for 2 years now. It's a big improvement but I still don't like the TOML file format.
@RahulKumar-et4pmАй бұрын
how can we add classpaths and how to find the proper versions of the plugin
@aditya_rajive7 ай бұрын
Would be great if you could make a video on automating Gradle dependency updates through Github Actions.
@hassanjamil8416 ай бұрын
Great video to know about the version catalog ❤
@eliasshemsu58536 ай бұрын
This is awesome, man!
@niharranjan35566 ай бұрын
Thanks Philipp for your great work ! I have seen gradle team has inculded this video link in their latest newsletter published for march, 2024. I have a question related to it though, appreciate if you can point me to something. With version catalog added to my project, I am not able to generate a gradle.lock file, and it always fails to identify the dependencies. There are multiple open bugs pending with gradle for the same and gradle team not showing the appetite to fix those as well.
@excalibur81475 ай бұрын
Came here to solve the same problem at 12:56 (material reference error) and you cut how you solved it :/ update: New projects don't include old material dependency, only material3
@SiamakAshrafi7 ай бұрын
Version Catalogs are the default in Android Studio Jellyfish | 2023.3.1 Canary 11
@emreyigit76715 ай бұрын
Thank you philipp :)
@DanielLuche7 ай бұрын
I'm using version catalog for a while but I didn't know that was possible uses the shortcuts to move build.gralde depencies into toml file.
@utubenada7 ай бұрын
Very cool. BTW. Should androidx-compose-tooling-ui-manifest be named androidx-copmose-ui-test-manifest?
@Rishisingh-s9h7 ай бұрын
i am learning android using your old projects but i am facing issue in your news app. I am stuck at a point from 3 days but i don't get any solution.i am using new version of android that is hedgehog. Please tell me what should i do?
@briantaylor_7 ай бұрын
would you say this is more ideal than using a buildSrc in a multi-module app?
@PhilippLackner7 ай бұрын
Yes
@briantaylor_7 ай бұрын
thanks @@PhilippLackner would love to see a video comparing buildSrc vs Version Catalogs with some pros and cons of each
@MarkOverton-fn4gm7 ай бұрын
Hi @PhilippLackner, I am busy doing your Multi-Module Architecture paid course and I just finished the Module Setup video. Am I correct in assuming that the Version Catalogue can completely replace the buildSrc method of managing dependencies? And will you update your course with the Version Catalogue method?
@PhilippLackner7 ай бұрын
@@MarkOverton-fn4gm yes you are
@Nonsense6754 ай бұрын
Hi Philip I am not able to add the Hilt dependency using this approach, as it gives this error: Duplicate class org.intellij.lang.annotations.Identifier found in modules annotations-12.0.jar -> annotations-12.0 (com.intellij:annotations:12.0) and annotations-23.0.0.jar -> annotations-23.0.0 (org.jetbrains:annotations:23.0.0) I have this in toml [versions] hiltCompiler = "1.2.0" [libraries] androidx-hilt-compiler = { group = "androidx.hilt", name = "hilt-compiler", version.ref = "hiltCompiler" } in build.gradle(apps) implementation(libs.androidx.hilt.compiler) see if if you could help here
@jacqueswho7 ай бұрын
I prefer your approach to using kotlin build src folder with variables and so forth. Its easier to manage and clean. Or am i missing something?
@gamermom19457 ай бұрын
You don't get the hint that there are newer versions if you use that approach
@Feints4Days-dx5gd7 ай бұрын
This feels so unnecessarily over-engineered
@jackeblan7 ай бұрын
You don't have to do this in a monolithic project. This is the best and recommended way in a multi-module project.
@RahulRamakrishnan-si4tb7 ай бұрын
What is the advantage of using this over the regular build.gradle?
@PhilippLackner7 ай бұрын
One source of dependencies for multi module projects
@RahulRamakrishnan-si4tb7 ай бұрын
@@PhilippLackner makes sense. did not think in that way. Good to know. Thanks for the video
@entorterradofotossintetizante7 ай бұрын
I’m waiting for the day when they’ll create a dependency manager like Rust’s Cargo or JavaScript’s npm.
@vighnesh1537 ай бұрын
I have worked in Javascript land for over 3 years of my life and felt like nothing is better. But after working with Gradle for a year, I have realized why it is superior than NPM. I am not saying it is the best, but it is definitely better than NPM.
@androidkotlin-62347 ай бұрын
how to create hilt plugin with version catalog? I didn't find instruction at docs. I was find it for dagger, not for hilt
@martinseal19877 ай бұрын
This is so bad, as if it wasn't complicated enough already they decided to add a new language file 😢, why can't we take an idea out of flutters playbook? Their pubspec file makes all of this so easy
@martinseal19877 ай бұрын
I wrote this early in the video after seeing all the generated info this is so stupid
@tygourm7 ай бұрын
This feature has been out there for a while and is actually one of the best ways to handle dependancies in Gradle projects. All your dependencies for your modules are centralized, you get autocomplete for plugins and dependencies in your Gradle scripts, you can use bundles to make your dependencies sections even smaller ... I think that it should be the standard for that propose, give it a try and you'll see how good it is 😉
@martinseal19877 ай бұрын
@@tygourm you're right I should but did we really need a new file type to learn
@martinseal19877 ай бұрын
@@tygourm also I didn't realise how long this has been around I thought it was new
@martinseal19877 ай бұрын
@@tygourm I hear you when you say it's the best way because the old way sucked I'm asking if this is a good
@oleg123957 ай бұрын
👍
@Otabek001uz7 ай бұрын
You're the best, Native developer!!!
@swaminathbera64077 ай бұрын
True
@friday75104 ай бұрын
yes, it's true!
@argahutama7 ай бұрын
How about Version Catalogue vs Gradle Kotlin DSL comparation?
@mohancena89706 ай бұрын
will you update multi-module course with version catalogs instead buildSrc ??
@readysetgo44685 ай бұрын
this was helpful i was watching an old tutorial on app development that was released on 2021 and i was confused as to why my dependency lines were red while his was fine XD
@SurjanHevin6 ай бұрын
How to add kotlin-kapt
@EsloqueesАй бұрын
Invalid catalog definition: - Problem: In version catalog libs, you can only call the 'from' method a single time. (i called just one time, what is wrong?) dependencyResolutionManagement { versionCatalogs { create("libs") { from(files("gradle/libs.versions.toml")) } } }
@WeCrackAllGames2 ай бұрын
So the only thing this does is adding an extra file to your project. I don't like that approach.
@Pulkit__72 ай бұрын
Great Video Philipp. Rant:- IDE support for this is worse, why don't Android Studio, just create a simple GUI interface, which makes it easier. Upgrading is mess, unused libraries in version catalogue is a mess. I don't like the new way of doing things, it's like we are intentionally making it difficult to import libraries, but as long as we get paid, eh.
@AllpcgeekАй бұрын
Thank so much, understood thanks
@koncinar7 ай бұрын
"Finally, developers can now use one language, Kotlin, for the logic, UI and also build config" "Unacceptable, let's bring in a completely new language without logic, code completion or even type safety. We'll build an extra tool to handle that." "Emmm, ok. We could then group the libraries together. For example with a dot like in the rest of the code?" "Boooooring, let's use dash on one side and dot on the other. So that they can't do a litelar search. Wink wink"
@riezkymaisyar40387 ай бұрын
thanks philips, this is great 🤙
@jamunaperumal3592Ай бұрын
How to add maven with pom , instead of using Gradle in android studio koala version
@GeertBerkers6 ай бұрын
Can you also do this with hilt dependency injection? I cant make ik work.
@tarsilacostalonga6 ай бұрын
Great video, Philipp! Is it possible to use the versions catalog and group dependencies like you did in the video "Perfect Dependency Management"? I mean, call room() and add all the dependendencies related to it.
@germenwong4 ай бұрын
of course,You can use a bundle
@that1angrykraken5 ай бұрын
how do we defind a dependency to a module when using version catalog?
@ahmadzafar57865 ай бұрын
Why not they introduce yaml file like Flutter
@moldovanpeter51237 ай бұрын
We have the same + build conventions
@martinseal19877 ай бұрын
Can we have more of your opinions? If you dont want to put then on the main channel i understand
@PhilippLackner7 ай бұрын
Opinions about what specifically? 😄
@Adorabledaivikshorts7 ай бұрын
Hi Philip Kindly Make an App Demo for a Live Streaming app For HLS or KZbin Using Jetpack Compose and Kotlin.
@МухаммадаминСалохиддинов7 ай бұрын
Hello world !
@annaberkovitch854 ай бұрын
Ah! This is great. Been working on the same big project for a while, so when i created a new project in Jellyfish for a small app this morning and went to add dependencies, the first reaction seeing the libs system was "WTF!?". Was tempted to revert back, but the OCD had won 😂 After it had taken me the best part of the morning to figure out the version catalog system on my own and add all my drpendencies manually, decided to migrate my big project... for which this video was, as usual, A GODSEND! Seriously, you're a lifesaver ❤
@robertfontaine36506 ай бұрын
Updated to the nosebleed version of android studio, ksp, jdk 21 etc. Dependency management is nice. They have done something new with resources as well. factoring and refactoring and rere.... I swear building the framework for an application takes longer than writing the logic. For MVVM I should just be able to configure the entities and click generate. stub the business logic and save a bunch of time. by the time you write 3 mvvm applications it's going to get pretty dull
@dhimanpaul37722 ай бұрын
this is very helpful for me . for this i can use string dependencies to library dependencies. thank you .
@dahlola7 ай бұрын
Another nice feature is that you can create "bundles". So say that you have related dependencies like compose for instance, then you can create a bundle of these. You can then in you app gradle file just refer to "implementation(libs.bundles.compose)" for instance.
@McMouse886 ай бұрын
It would be nice to mention about bundle in version catalog. And it would be pretty convenient if version catalog has opportunity to define groups like versions )))
@Yannis1968-96 ай бұрын
I tried recreating your room beginner project with this version catalog android studio and I keep getting an error with classes conflicts
@v4lde3c06 ай бұрын
your videos are very top! Thank you so much for sharing your knowledge. 😍🤩🥳❤🙏
@kalios017 ай бұрын
My college faculty be like this could be done by creating val for version 😂
@jackc-gw76307 ай бұрын
Hey your location tracking app doesnt seem to auto update anymore, do you know why?
@robertfontaine36507 ай бұрын
Nice to see this is being done. Sad that I did this all manually and now I have to unwind it. :)
@tasnimulhasan73297 ай бұрын
thanks for this video. this tutorial helped me a lot upgrading my gradle from to old and I now understand toml very well. thanks again bro
@4ytonly4 ай бұрын
Can someone explain why use this!? It look like few steps more then before, and I don't see any extra benefits from doing stuff this way
@vengateshm21227 ай бұрын
Bundles is missing here.
@ngenge_senior7 ай бұрын
Thanks for this Philipp
@leunamvon25655 ай бұрын
King of Android.
@mustafaammar5517 ай бұрын
Thank you BRO
@Diego-hn6oh7 ай бұрын
Hi, I'm new to android developmet, is it better to get started with view xml or jetpack compose?
@pgnrr7 ай бұрын
Compose all the way
@shashanksp91687 ай бұрын
compose , don't waste time learning xml !!
@CodeRedDevelopment7 ай бұрын
Do they also support notices about new versions of the dependencies?
@robchr7 ай бұрын
Yes, there will be a yellow squiggly in the version catalog when there is a new version, just like in the build.gradle file.
@CodeRedDevelopment7 ай бұрын
@@robchr Great 🤩 This was always a problem some years ago back when I tried out own version catalogs by gradle ext.
@byaruhaf7 ай бұрын
Wouldn't using Version Catalogs be more relevant for Multi-Module Apps?
@PhilippLackner7 ай бұрын
Yes, but it also becomes the standard for single module apps