useDepAts seems to look for old ATs before actually updating the dependency

[mezz]

build.gradle

Here is console output from a recent jenkins build:
https://gist.github.com/mezz/6308e4bb684acf7818e6

I am building my mod against JEI 1.10.0.102, which has an AT file, but it is looking for an AT from an older version, JEI 1.8.3.99.

Found AccessTransformer: jei_at.cfg_jei_1.8-1.8.3.99_at.cfg
...
:deobfMcMCPjava.io.FileNotFoundException: /var/lib/jenkins/workspace/JEI_Addons-MC1.8/build/depAts/jei_at.cfg_jei_1.8-1.8.3.99_at.cfg (No such file or directory)

This means I usually have to build twice in a row, half the time it seems to work fine.

[Darkhax]

I am experiencing the same issue on one of my projects. Glad to know I am not alone here lol I go into my issue a bit deeper here.

[maruohon]

I have also noticed the same issue. The recent builds of my mod on a jenkins box have tried to use the AT file from the version of JEI that was as a dependency in the previous build (ie. whenever I update the JEI dependency, the build fails on the first try). (Although atm I have only seen this twice because of lack of activity on my mod lately, but anyway, both of my most recent builds have this issue, since both of those updated the JEI dependency.)

Edit: build log: https://gist.github.com/maruohon/dbdca15ac2a1b27e7b20

[tterrag1098]

Still occuring for me http://ci.tterrag.com/job/Chisel/branch/1.9%252Fdev/5/console

That is even with --refresh-dependencies

[Darkhax]

I can confirm What tterrag is saying, an issue still exists.

[AbrarSyed]

ugh

[UntouchedWagons]

Mezz recommended I leave a polite comment in the event I find this issue annoying. Pls fix thanks.

[Darkhax]

Just wanted to leave another reminder that this is still an issue. Would really appreciate a fix.

[DaemonUmbra]

Closing this issue as it does not appear to be applicable to the currently supported ForgeGradle branch (FG_3.0).

If I am incorrect in this regard, please create a new issue prefixed with [FG_3.0] and containing:

• A summary of the issue (in case the issue has mutated slightly or the original report was poorly described)
• Steps to recreate the issue
• Console output or logs (if possible)

Note that an ongoing effort to update legacy MinecraftForge branches to utilize FG_3.0 is ongoing and accepting informed contributions. (For more information join the Discord and read through the #mcpconfig channel)