Unforking this Gradle plugin back to Palantir #16
Description
I'm from Palantir, the original authors of this plugin, and we would just like to notify you that we are planning to unfork gradle-revapi back to our own Github org. In particular, we need to make a number of changes to the plugin and it will be easier if it is back under our control and standards:
- Gradle 9 support
- Configuration Cache support
- Isolated Projects support
- Bug fixes around the way the plugin finds previous releases
- Running revapi inside a worker daemon with configurable memory to not cause OOMEs in the Gradle daemon
- Improvements to the accepted break file format so it handles PR workflows that do not require up-to-date before merge, and make it more readable
- Working CI for the project
This plugin was moved out of palantir as we were not immediately able to invest in upgrading it to support Gradle 8 due to competing internal priorities and reduced team size. We now have a vastly larger team dedicated to JVM build tooling so this is no longer a concern. We have infra to automatically rewrite Gradle plugin code to use the latest best practices, automatically update dependencies, test automatically against multiple versions of Gradle, as well as dedicated team of experts for Gradle plugins, so believe it's probably going to better maintained living with us.
We'll be doing this soon (early next week) - we'll make sure to bump the major version to try to reduce confusion, but the plugins have different ids and maven coordinates so there shouldn't be an immediate issue.