Is Shipkit+Gradle wanted?

[magneticflux-]

Using the Shipkit Gradle plugin could be pretty useful. It manages the release process by integrating with CI tools such as Travis CI, automatically compiling changelogs, author lists, and incrementing the patch version.

Using Shipkit requires moving to the Gradle build system. That could be a plus or a minus depending on who you talk to, but I feel in general that it is a plus. I believe all of the current Maven plugins used in this build already have Gradle counterparts.

Additionally, the Spotless Gradle plugin could be used to enforce a consistent code style. From a cursory review of the test files, I can already see some odd spacing around generic types and around method arguments, as well as some detected redundant statements/logic.

I'm asking first so I don't go to all the trouble of updating and changing things only to find out you'd rather stick with Maven. It's your call, @magro.

[magro]

I'm open to everything that brings improvements :-) Moving to gradle and automating the release sounds good!