https://gradle.com/ logo
Join Slack
Powered by
This message was deleted.
# community-support
s
This message was deleted.
f
where are they generated? I seem only having those under 
build-logic/xxx-plugins/build/generated-sources.../../xxx.kt
so I never noticed it without searching this type of import.
Otherwise try use the latest IntelliJ? 🙂
👌 1
v
You are using my hack-around for using version catalog accessors within precompiled Kotlin DSL build scripts, aren't you?
u
The location of accessors is in the build directory.
It’s not a critical issue because it happens intermittently, but it’s inconvenient because you have to repeat clean & build or intellij restart. I was curious if there was any prevention method or fundamental solution.
@Vampire I’m not sure if I understood correctly, This occurs even if version catalog is not used. The above case occurred in a simple convention plugin that simply runs maven-publish.
v
The question was whether you generally use my hack-around in that project, not specifically in that script.
Because afair this occasional "mis-behavior" of the IDE is a side-effect of my hack-around.
a
I notice the same problem when I copy-paste code from one convention plugin / buildscript into another. Usually when you copy paste code IntelliJ tries to be helpful and automatically add the dependencies, but in this case it doesn't realise it shouldn't copy the generated accessor imports! https://youtrack.jetbrains.com/issue/KTIJ-27871/Gradle-Add-unambiguous-import-on-the-fly-adds-wrong-import#focus=Comments-27-8500085.0-0 If you're noticing IJ adding the imports in other situations, then I suggest you add a comment or make a new issue.
👌 2
thank you 1
u
@Vampire Is the ‘my hack-around’ you mentioned https://github.com/gradle/gradle/issues/17963 referring to this? Then yes.
v
3 Views
Open in Slack
PreviousNext
Powered by