This message was deleted.
# community-support
s
This message was deleted.
v
No. Unless the plugin is designed to do it itself for example by using worker api with classpath isolation or process isolation.
Or by shading the dependency into its own jar with relocation which makes it independent of other dependencies, but is a bit bad practice imho. Using worker api is imho preferable there.
a
Thanks. In this instance I might be able to wrap the third party lib into a custom plugin and provide classpath isolation. The Gradle docs mention that a future version will introduce proper isolation for plugins. Is this planned into v9 by any chance? https://docs.gradle.org/current/userguide/designing_gradle_plugins.html
v
I don't think that this will come any time soon or ever at all. I would actually assume this is just wrong and should be removed.
It should probably have been removed together with this commit: https://github.com/gradle/gradle/commit/d71c6c43725d4d31e9de2237ba524f2942d9bd9f that removed "Allow different plugins to use different versions of dependencies." in the description of
plugins { ... }
DSL in PR https://github.com/gradle/gradle/pull/21448 to fix this issue: https://github.com/gradle/gradle/issues/21293. What do you think @Paul Merlin?
p
Agree this should be removed. Promises in documentation 🤦 🙄
v
Is this enough for you to do it right away, or do you need an issue opened? :-)
p
a
Not the result I was hoping for but thanks for the quick turnaround time 🙂
👌 1