thanks to intellij I m almost completely stuck now

Question

Soren Valle · Answer

I m not entirely sure because I m new to gradle myself but you might try File gt Invalidate Caches Restart Also you could try deleting your generated gradle files

barteks2x · Answer

This is a nuclear option that will take almost as long as my fumbling around solution

Soren Valle · Answer

Is this a recurring thing then

barteks2x · Answer

yes It s an issue every single time I change something in buildSrc

Soren Valle · Answer

Oh gotcha

barteks2x · Answer

intellij just doesn t catch on and thinks everything is stll as it was when editing build gradle kts

barteks2x · Answer

it clearly has the option to refresh it but I have no idea how to reliably trigger it

Soren Valle · Answer

That might be the option

barteks2x · Answer

the issue is that intellij isn t even detecting that anything has changed So autorefreesh won t help

barteks2x · Answer

it will just make the issue way more annoying because it will be all hidden behind magic autorefresh that doesn t work

Soren Valle · Answer

That is annoying what version are you on 2019 2

barteks2x · Answer

yes

barteks2x · Answer

but again gradle 4 8 and I know kotlin dsl support has been improved significantly in 5 x

barteks2x · Answer

but I can t upgrade

Soren Valle · Answer

That might be it but it doesn t seem like it I wish I knew more One that I do know from messing around with getting a scss to compile on change I had to trigger the project sync I can t remember why but what I remember is that for some reason I had to manually do it That was different but you might consider looking into that

Soren Valle · Answer

Meaning manually tell the ide that something has changed

barteks2x · Answer

I do refresh gradle project quite regularly when editing gradle plugin and have autorefresh disabled because it takes forever But this doesn t appear to have any way to force manually

barteks2x · Answer

at least not that I can find The only option I see is when intellij decides it knows that something in buildscript dependencies has changed and offers me the option

Soren Valle · Answer

You can make a macro and then bind it to a keyboard shortcut

barteks2x · Answer

buildSrc is buildscript dependency not project dependency And if the option to force applying buildscript dependencies exists it s really well hidden

Soren Valle · Answer

Wait I think I miss understood In the picture you linked in main channel you didn t select the auto reload you want the first option Apply Dependencies to be a manual thing is that correct

barteks2x · Answer

yes

barteks2x · Answer

I want to be able to do it whenever I want not when intellij thinks something changed and shows me this option

barteks2x · Answer

it looks like adding a dummy classpath entry to buildscript dependencies that it has never seen before works quite reliably but it s still just a weird workaround

Soren Valle · Answer

That s a manual trigger there would that do it for you

barteks2x · Answer

reimport gradle project is not it

Soren Valle · Answer

That resyncs the deps for me

Soren Valle · Answer

Different thing

Soren Valle · Answer

Man I m sorry I m out of thoughts Maybe a feature request Sorry I couldn t be of more help

barteks2x · Answer

I honeslty hate dealing with any issue trackers other than github so I will probably just keep doing what I have been doing until a few days later where I no longer need to touch my buildscript for the next few months

Soren Valle · Answer

Fair enough hope you figure something If you do let me know

Soren Valle · Answer

I hate problems I can t solve

barteks2x · Answer

The only workaround I have is as I said to add a dummy classpath entry in buildscript dependencies

barteks2x · Answer

discovered it just a few minutes ago

Soren Valle · Answer

Oh yeah good to know