gradle-git has been around since 2012 and has evolved quite a bit from the original release. In order to continue to evolve these features, this project is being broken up into multiple repositories. As such:
- gradle-git will no longer be enhanced
- gradle-git may make some fix releases, as issues are identified, presuming they don't break compatibility
||grgit||stable||Grgit has been an independent project since 2013 and has been stable for quite a while. Version 2.0 removed some deprecated features, but otherwise is fully compatible with existing usage. It also integrates the
||reckon||development||Reckon focuses solely on determining your project version (and assisting with tagging and pushing that tag). It provides an opinionated model of how to apply semantic versioning, with more finite configuration options.|
Why do you care?
Git is immensely popular and being able to interact with it as part of a build process can be very valuable to provide a more powerful and consistent result.
What is it?
gradle-git is a set of Gradle plugins:
org.ajoberstar.grgit- provides a
Grgitinstance, allowing interaction with the Git repository the Gradle project is contained in
org.ajoberstar.github-pages- publishes files to the
gh-pagesbranch of a Github repository
org.ajoberstar.release-base- general structure for inferring a project version and releasing it
org.ajoberstar.release-opinion- opinionated defaults for
See Grgit for details on the Git library used underneath, including configuration for authentication.
NOTE: gradle-git modules require Java 7 (or higher).
Questions, Bugs, and Features
Please use the repo's issues for all questions and bug reports.
Non-breaking bug fixes are welcome via pull requests.
I am no longer accepting feature contributions. See the Project Status section above for details.
Thanks to all of the contributors.
Credit goes to Peter Ledbrook for the initial
idea for the