This session was given at Paris Android Makers 2018 by Bradley Smith and Lucas Smaira, Google.
More info: http://androidmakers.fr/schedule/#ses...
Android Studio is a build system-centric IDE, where Gradle is the source of truth. This decision was made when we started Android Studio back in 2013, with the following benefits in mind:
• 1. IDE configuration files (IML files) are generated when syncing a project with Gradle. Developers no longer have to manually edit IML files.
• 2. By delegating builds to Gradle, build output will be the same regardless of where the build is executed: IDE, command line or CI server.
Even though we delivered on these promises, there is still friction between the IDE and Gradle, making the user experience not awesome:
• 1. Syncing a project (with Gradle) is slow
• 2. Project synchronization has to be manually started.
• 3. Editing build.gradle files is not trivial
• 4. There is no way to visualize the structure of a project: a full dependency graph, how build variants are composed, etc.
• 5. Importing big projects (100+ modules) makes the IDE crawl
I'll cover each problem and what my team is doing to solve these issues. I'd love to gather feedback from the audience, to have a better understanding of their pain points and how our strategy aligns with their priorities.
Alex Karp Production
Смотрите видео Gradle in Android Studio 3.2 and beyond by Bradley Smith and Lucas Smaira, Google EN онлайн без регистрации, длительностью часов минут секунд в хорошем качестве. Это видео добавил пользователь Android Makers 15 Июнь 2018, не забудьте поделиться им ссылкой с друзьями и знакомыми, на нашем сайте его посмотрели 453 раз и оно понравилось 3 людям.