-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Support for configuration cache #8
Comments
For now this workaround seems to be enough tasks.named('generateMavenPluginHelpMojoSources') {
notCompatibleWithConfigurationCache('https://github.com/britter/maven-plugin-development/issues/8')
} |
Yes, that's true, but it will disable the configuration cache whenever this plugin is part of the build 😕 |
Gradle 7.6.1
|
This is not possible without breaking API, so I'll put this into the 1.0 milestone. |
Just to chime in what I'm running into:
|
yeah, this is still on my backlog. I hope to have some more time to work on this project again in the near future. For now the only workaround is to explicitly disable to configuration cache for the tasks in the plugin. |
Does it make sense to finish and merge #148 until then? |
No, #148 is going to replaced by a different approach. The challenge with the current state of the code is that the tasks unnecessarily reference types that can't be serialized into the configuration cache. My plan is to change that while moving to the org.gradlex namespace because then binary compatibility will be broken anyway. |
Instant execution is one of the upcoming features in Gradle. The plugin should support this.
The text was updated successfully, but these errors were encountered: