I’m not sure about the total number of consumers of the gradle-rpm-plugin, but the below was posted by at least one user within the last 24 hours to the gradle-rpm-plugin github site.
We’re having quite a lot of issues using the plugin across different environments >
1.3 works with Gradle 1.6, but not Gradle 1.7 + > 1.4 works only with Gradle 1.7, but not 1.8 > Nothing works with Gradle 1.8 >
It would be great if plugin was backwards compatible across all versions of Gradle, so that we could always point to the latest one and > have it work across multipel boxes with Gradle 1.6, 1.7 and 1.8
Because of this exact same issue, Gradle 1.7 is the latest version in use by us in some instances, as robust rpm generation has been deemed more important at present than other core features. There is a non-released version of the gradle-rpm-plugin being tested that works with Gradle 1.8, but key functionality appears to be broken again in the latest 1.9 release candidates.
It would be good to have some idea of how many people are relying on the gradle-rpm-plugin or would consider utilizing it, if it weren’t so brittle recently.