Hi,

 

I've got a little problem.

 

runDir = "../run/assets"

deobfCompile "mezz.jei:jei_${config.minecraft_version}:${config.jei_version}:api"
runtime "mezz.jei:jei_${config.minecraft_version}:${config.jei_version}"

 

So I got those dependencies and updated them today. My problem is, gradle didn't deleted the old dependencies it seems and so I can't start Minecraft as I've got now twice the runtime dependencie.

Does anyone know where Gradle saves these dependencies so I can delete the old version manually?

I've already looked into the mods folder at "../run/assets/" but this folder is empty.

 

Besides, to update the dependencies I've run this command: gradlew cleanCache setupDecompWorkspace --refresh-dependencies eclipse

And is there any way to let gradle automatically delete those old dependencies?

 

Thx in advance.

Bektor

 

Edited April 21, 20178 yr by Bektor

For me (on Linux) gradle stores JEI in /home/user/.gradle/caches/modules-2/files-2.1/mezz.jei.

Edited April 21, 20178 yr by Matryoshika

1 minute ago, Matryoshika said:

For me (on Linux) gradle stores JEI in /home/user/.gradle/caches/modules-2/files-2.1/mess.jei.

Ah, ok, thx. Makes %homepath%\.gradle\caches\modules-2\files-2.1\mess.je

But interesting, the whole .gradle folder there is over 1GB large with about 6-8 different Gradle versions. ^^

 

So, is there a way to delete those old dependencies automatically when a new dependencie has to be downloaded. I basically mean, when you update depencie A, the old one get's deleted and the new one downloaded but depencie B stays the same as it is not required to download any new version there.

52 minutes ago, Bektor said:

So, is there a way to delete those old dependencies automatically when a new dependencie has to be downloaded. I basically mean, when you update depencie A, the old one get's deleted and the new one downloaded but depencie B stays the same as it is not required to download any new version there.

As far as I am aware, gradle should do this when you run the eclipse task. At least I'm sure I've had it do that before. If it doesn't delete the old versions, try running this command:

gradlew cleanEclipse eclipse

That'll clean all the Eclipse specific gradle stuff and set it up again, which should fix your issue. 

4 minutes ago, Leviathan143 said:

As far as I am aware, gradle should do this when you run the eclipse task. At least I'm sure I've had it do that before. If it doesn't delete the old versions, try running this command:

Well, it doesn't delete the old versions when I'm running the eclipse task and it doesn't delete the old versions when I run the cleanEclipse command.

You will need to refresh the project. Also, delete from where?

5 minutes ago, Leviathan143 said:

You will need to refresh the project. Also, delete from where?

Well, from the .gradle folder:  %homepath%\.gradle\caches\modules-2\files-2.1\

I don't wanna have there over 1GB of cached stuff just because this folder exists for some years now.