Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
mezz opened this issue Dec 19, 2015 · 8 comments
Closed

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

mezz opened this issue Dec 19, 2015 · 8 comments
Labels
Bug

Comments

@mezz
Copy link
Member

@mezz mezz commented Dec 19, 2015

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.

@AbrarSyed AbrarSyed added the Bug label Jan 5, 2016
@Darkhax
Copy link

@Darkhax Darkhax commented Feb 28, 2016

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
Copy link

@maruohon maruohon commented Mar 3, 2016

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

@AbrarSyed AbrarSyed closed this in cf21a49 Mar 9, 2016
@tterrag1098
Copy link
Member

@tterrag1098 tterrag1098 commented Mar 20, 2016

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

That is even with --refresh-dependencies

@Darkhax
Copy link

@Darkhax Darkhax commented May 1, 2016

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

@AbrarSyed
Copy link
Member

@AbrarSyed AbrarSyed commented May 1, 2016

ugh

@UntouchedWagons
Copy link

@UntouchedWagons UntouchedWagons commented Jun 7, 2016

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

@Darkhax
Copy link

@Darkhax Darkhax commented Oct 7, 2016

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

mccreery added a commit to mccreery/hotswap that referenced this issue Feb 9, 2019
Had to add some extra processing for InvTweaks'
non-standard AT handling, which Forge misses
with its normal extractDependencyATs task.
Also added information about fixing a ForgeGradle bug
(MinecraftForge/ForgeGradle#312)
@DaemonUmbra
Copy link
Contributor

@DaemonUmbra DaemonUmbra commented May 28, 2020

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants