This message was deleted.
# plugin-developments
Slackbot
09/20/2023, 9:52 AMThis message was deleted.
e
ephemient
09/20/2023, 12:17 PMafaik those blocks run outside of buildscript classpath, but if you're making a custom distribution anyway, you could update the core Gradle classes
e
efemoney
09/21/2023, 10:42 AMHow do you mean update the core gradle classes? š¤
t
Thomas Broyer
09/21/2023, 11:50 AMWithout updating the core classes (i.e. actually patching the gradle-core-api.jar/gradle-core.jar), wouldn't it be possible to put the JAR in a place such that it will be added to the classpath without the need for your init script? (and hopefully they'll work for the kotlin dsl plugins/pluginManagement specific compilations)
e
efemoney
09/22/2023, 8:16 PMHmmm, thats an interesting pov. I have no idea actually.
efemoney
09/22/2023, 8:18 PMI can try putting them in
libefemoney
09/24/2023, 7:51 PMDidnt work š
efemoney
09/24/2023, 7:51 PMGradle looks for jars in that folder based on some predefined modules (and their dependencies)
e
ephemient
09/24/2023, 8:16 PMif you're building your own Gradle distribution anyway, it shouldn't be much more work to build your own custom Gradle entirely
ephemient
09/24/2023, 8:17 PMadd your extension to https://github.com/gradle/gradle/blob/master/platforms/core-configuration/kotlin-d[ā¦]ain/kotlin/org/gradle/kotlin/dsl/RepositoryHandlerExtensions.kt and it should be available
e
efemoney
09/24/2023, 9:05 PMIts definietely a lot more work to build custom gradle š
. The custom gradle distro is light work really.
efemoney
09/24/2023, 9:07 PMIām just surprised that even using ā_publicly internalā_ APIs there is no supported āhookā into the system to add custom API.
t
Thomas Broyer
09/24/2023, 9:33 PMHow about adding your classes to, e.g. gradle-kotlin-dsl-XX.jar?
e
ephemient
09/24/2023, 9:34 PMit's a little tricky since you also have to merge the
.kotlin_modulee
efemoney
09/24/2023, 11:15 PMIf I could figure out a way to change the contents of one of the jars then itād be better to just update the /gradle-plugins.properties. Those are auto added to the classpath (looks like its supposed to be built in gradle plugins etc)
e
ephemient
09/24/2023, 11:15 PMyou can do that by modifying the gradle source code and building it
e
efemoney
09/24/2023, 11:16 PMI know but thats not what I want and its a much bigger commitment than just downloading and adding a few files.
e
ephemient
09/24/2023, 11:16 PMdistribution-wise it ends up being the same as a custom distribution, and building gradle is simple and relatively fast (remote caches are set up)
e
efemoney
09/24/2023, 11:17 PMIts just unfortunate that āadding a few filesā is not sufficient to include custom DSL that will target pluginManagement blocks (its more than sufficient for DSL in general, just the plugin management use case thats sad)
e
ephemient
09/24/2023, 11:18 PMspecial blocks are specialā¦ and becoming more so, https://docs.gradle.org/current/userguide/plugins.html#sec:constrained_syntax
e
efemoney
09/24/2023, 11:24 PMYeah I know, hence why I asked here in the first place hoping someone knew āsome type of wayā. Its a niche use case, but since its the recommended way of adding plugins, I still want a way to support it.
e
ephemient
09/24/2023, 11:25 PMyour initial question is fairly similar to the request https://github.com/gradle/gradle/issues/26212
e
efemoney
09/24/2023, 11:25 PMAh yeah, exactly that! It started out trying to add in an init script just like the issue but looking at the source, I see it wont work. Now Iām looking more into how I can include the extensions in the parent/root classpath instead (which I believe is used to actually compile those blocks). Looks like I have one final option š .
I really wish there was an easier, supported, way. tbh,