Merge pull request #136 from novoda/release/2.0

release/2.0

CHANGELOG.md

@@ -1,3 +1,27 @@
+# 2.0
+
+_2018-01-30_
+
+### New
+
+- DSL support for main adb wrappers.
+ - Currently supporting `monkey`, `scripts` (#121), `demoMode` (#125), `install` (#127) and `start` (#130) extensions.
+ - More information can be found in https://github.com/novoda/gradle-android-command-plugin#configuration
+
+### Improvements
+
+- Full documentation on public configuration on `command` extension [#129](https://github.com/novoda/gradle-android-command-plugin/pull/129)
+- Clean-up sample project [#126](https://github.com/novoda/gradle-android-command-plugin/pull/126)
+
+### Deprecations
+
+- `task` methods in the extension are deprecated. Instead use the provided and documented DSL's to configure custom tasks. With this change,
+ - Generated tasks are more consistent
+ - usage is nicer-looking thanks to Groovy DSL
+- `sortBySubtasks` is deprecated and not used internally in the plugin.
+ - Tasks are not categorized by variant or simply task names anymore.
+ - Instead, each provided DSL has more meaningful category.
+
 # 1.7.1
 
 _2017-01-31_

README.md

@@ -34,7 +34,7 @@ buildscript {
  jcenter()
  }
  dependencies {
- classpath 'com.novoda:gradle-android-command-plugin:1.7.1'
+ classpath 'com.novoda:gradle-android-command-plugin:2.0'
  }
 }
 ```
@@ -190,7 +190,7 @@ All possible values can be found in [the official Android documentation](https:/
 
 ### Install
 
-`installDevice<Variant>` tasks are available by default just to install the app. The plugin also supports an `install` dsl to define custom installation tasks.
+`installDevice<Variant>` tasks are available by default just to install the app. The plugin also supports an `install` DSL to define custom installation tasks.
 
 **customFlags**
 
@@ -230,7 +230,7 @@ install {
 
 `start<Variant>` and `run<Variant>` tasks are available by default. Start tasks just start an already installed application. Run tasks first install the app before starting.
 
-Just like the `install` dsl, it is possible to specify a device id. Doing this will create corresponding `start` and `run` tasks. 
+Just like the `install` DSL, it is possible to specify a device id. Doing this will create corresponding `start` and `run` tasks. 
 
 ```groovy
 start {

build.gradle

@@ -1,3 +1,4 @@
 task wrapper(type: Wrapper) {
- gradleVersion = '3.2.1'
+ gradleVersion = '4.4.1'
+ distributionUrl = "https://services.gradle.org/distributions/gradle-${gradleVersion}-all.zip"
 }

plugin/build.gradle

@@ -23,13 +23,13 @@ dependencies {
 }
 
 group = 'com.novoda'
-version = '1.7.1'
+version = '2.0'
 
 publish {
  userOrg = 'novoda'
  groupId = 'com.novoda'
  artifactId = 'gradle-android-command-plugin'
- version = project.version
- description = 'Useful tasks for gradle android builds'
+ publishVersion = project.version
+ desc = 'Useful tasks for gradle android builds'
  website = 'https://github.com/novoda/gradle-android-command-plugin'
 }

plugin/src/main/groovy/com/novoda/gradle/command/Install.groovy

@@ -8,14 +8,14 @@ class Install extends AdbTask {
 
  /**
  * Manual creation of Install task is deprecated.
- * Please refer to install dsl documentation for details:
+ * Please refer to install DSL documentation for details:
  * https://github.com/novoda/gradle-android-command-plugin#install
  */
  @Deprecated
  void setCustomFlags(customFlags) {
  logger.warn """\
  Manual creation of Install task is deprecated.
- Please refer to install dsl documentation and modify your task '$name'
+ Please refer to install DSL documentation and modify your task '$name'
  https://github.com/novoda/gradle-android-command-plugin#install
  """.stripIndent()
  installExtension = new InstallExtension()

sample/build.gradle

@@ -17,4 +17,5 @@ subprojects {
 
 task wrapper(type: Wrapper) {
  gradleVersion = '4.4.1'
+ distributionUrl = "https://services.gradle.org/distributions/gradle-${gradleVersion}-all.zip"
 }