2.3.2-"3.0.1
gradle version is 4.1com.android.tools.build:gradle:3.0.x
- Android Monitor has been replaced with Android profile;
- The new project needs to be configured Android.enableaapt2=false in gradle.properties to compile the pass;
- Compile is not recommended, Google recommends the use of new implement and APIs;
- API: Exactly the same as the compile directive, no difference, you change all the compile to the API, absolutely nothing wrong.
- Implement: This directive is characterized by the dependency on the project that is dependent on the use of this command, which will not have access to any program in the dependency compiled using the command, that is, to hide the dependency internally, not externally.
- recommendation : In the Google IO related topic mentioned a suggestion, that is, rely on the first should be set to implement, if there is no mistake, then use the implement, if there is a mistake, then using the API instructions, this will make the compilation speed increased.
' Libs ', include: ['*.jar'])
But after 3.0, the notation is
' Libs ', include: ['*.jar''libs', Include: ['*.jar'])
3.0.1-"3.1.2
gradle version is 4.4com.android.tools.build:gradle:3.1.x
- Compile is no longer available;
- Android.enableaapt2=false is not available and needs to be configured to TRUE, the document hint will be completely removed at the end of 2018;
- Do not use the built-in JDK, with your own;
Warning: It is best not to upgrade, do a good backup before upgrading, or you will be the pit dead ... Do a development easy, write code, overtime not to say, but also by a variety of garbage software torture ... Convex (艹 dish 艹)
Differences between Android Studio versions
