-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36362/
-----------------------------------------------------------

(Updated July 9, 2015, 7:03 p.m.)


Review request for Aurora and Zameer Manji.


Repository: aurora


Description (updated)
-------

Upgrade to gradle 2.5.  Release notes here: 
https://docs.gradle.org/current/release-notes
In particular, this feature might be intersting to try out:
```
The new “Continuous build” support brings capability to have Gradle 
automatically initiate a build in response to file system changes. This works 
with any build and has many applications. For example, it can be used to get 
continuous compile and test, giving more immediate feedback. As it works with 
any Gradle task, it is equally applicable to documentation generation tasks and 
more. Upcoming versions of Gradle will build on this capability to facilitate 
reloading applications and the like under development in response to changes, 
providing a fast feedback local development loop.
```
Note: i had to resort to `git clean -fdx` to fully wipe out my intellij 
project, as i encountered a problem running unit tests due to a reported module 
cycle (somehow related to annotation processing).  Gradle 2.5 does indeed have 
changes in this area, but clearing out the old project corrected the issue i 
encountered.


Diffs
-----

  buildSrc/gradle.properties 3231a7add9e0503f0ee6779ae3c4000143b174ab 
  gradle/wrapper/gradle-wrapper.properties 
e713793f7d63e65ea68e091b959ba6a68352b48f 

Diff: https://reviews.apache.org/r/36362/diff/


Testing
-------

./gradlew build -Pq
./gradlew idea, ran unit tests
Played with continuous build: ./gradlew -t build


Thanks,

Bill Farner

Reply via email to