Manifest doesn't provide AT to dependant mods

Question

Manifest doesn't provide AT to dependant mods

yrsegal opened this issue 7 years ago · 5 comments

yrsegal commented 7 years ago

https://github.com/yrsegal/NaturalPledge/tree/1.12

When I setup using Botania (as of latest maven build), despite using dep ATs, the botania_at.cfg isn't copied into my build/depAts folder, causing all builds and runs to fail with a security exception.

This can be solved by copying botania_at.cfg into the build/depAts manually, so it's not a problem with the AT, but in how it's set up in the manifest.

quat1024 commented 6 years ago

🤔

williewillus · Answer 1 · 2018-02-01T15:36:24.000Z

so what am I supposed to do to fix this :thonk: idk how the manifests work

yrsegal · Answer 2 · 2018-02-02T01:20:19.000Z

i don't either maybe don't have it in a META-INF folder in src/main/resources? i'm spitballing though

williewillus · Answer 3 · 2018-06-29T01:56:50.000Z

idk gradle someone just fix it pls 😢

Hubry · Answer 4 · 2018-10-15T12:12:09.000Z

Seems like there are two Botania jars deployed on Maven - one of them is the universal jar, which is the proper one that has the AT defined in the manifest, and the other one has no classifier and no FMLAT in manifest (and also has all the files it is supposed to exclude?). Sadly idk gradle either that well and I have no idea which step does this, I couldn't get it to create the universal jar or the incorrect one with no classifier even once.

Share to