Your basic gradle build script can look like this: Okay, but how does the “New Build System” prevail in practice? Using the Gradle Android BuildĭISCLAIMER: We are only a few days away from Google IO 2013 so the points raised here might have already changed when you read this.īasic build scripts can be really really small when you rely on the default folder structure for your project. Maven dependencies can be consumed from maven central, while it is also easy to consume “local file” dependencies. The gradle-based build combines some of the strengths of ant and maven (flexible architecture with a lot of custom tweaking opportunities), whilst at the same time providing reasonable default configurations to keep the build scripts small. The new build system is supposed to become the official mechanism for building Android applications. The pom files tend to get verbose and interfering with the designated build process lacks flexibility.Įntering the “ New Build System” based on Gradle. The plugin allows you to infuse maven artifacts and perform the necessary build steps to package your app. Although maven has a great artifact repository, it has a pretty rigid set of configuration settings. Hence, the natural evolution of build process spawned the maven android plugin. It mainly lacks a well-populated dependency infrastructure similar to what maven offers (ivy doesn’t count). The Android SDK ships with a set of helpful ant scripts, but has its shortcomings. Building an Android project can be challenging at times.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |