-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatible with Gradle Configuration Cache #163
Comments
Thank you for the groundwork done here. I had a brief look at the providers API and found that Therefore, I would like to postpone this feature for some time until Gradle 6.5+ is more commonly used. Let me know if you have a hard reason to use configuration caching and based on the number of votes this comment receives, I'll create and maintain a parallel 3.x branch. |
The main reason is getting rid of recurring waiting times in the development experience that can be avoided. While I understand why it would be to be annoying to maintain two, if this plugin is indeed used by old gradle versions. Other high profile plugins such as shadowjar, kotlin, and jooq have already taken the leap. |
@dsvensson I hear you. I am mostly going to implement this as there is another bug, #156 which needs me to start using the Providers API and lazy configuration in order for the plugin to be compatible with Gradle 7. |
Thanks for the great work you put into this project! Out of curiosity, do you as a gradle plugin developer get metrics on what gradle versions are downloading the plugin from the gradle portal? |
Unfortunately not. The Gradle Plugin Portal is one of the most primitive plugin repositories out there. NPM really puts everyone to shame. Anyway guess what issue number 2 is on Gradle Plugin Portal? 🙂 |
This breaks again in 6.8 it seems:
|
This break in 6.8.2 |
Speaking of configuration cache, it really seems that it was introduced without much of impact analysis and migration guidance for plugin authors. I’m the author of build-time-tracker plugin, and had to work around several nagging issues introduced by configuration cache design, or lack of it. I don’t know if this plugin uses build listeners, probably not, but if you do, you’re in for a lot of trouble. |
Originally posted as comment to #153, but deserves its own issue.
gradle 6.6 released, and with the new
--configuration-cache
feature this plugin causes:Looks like a trivial fix. Have to lookup the overrides specifically via ProviderFactory.systemProperty rather than searching for them like today in getOverrides.
Trying to fix (wild guesses here, never done any plugin development - nor groovy) that part results in the following error on the second execution after establishing the cache:
Crude diff to get rid of the undeclared_sys_prop_read warning:
...and commenting out jacoco, build scans, and the overrides test, and bumping to 6.6
The text was updated successfully, but these errors were encountered: