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

LiteLoader plugin unusable with subprojects #347

Closed
mattmess1221 opened this issue Mar 10, 2016 · 8 comments
Closed

LiteLoader plugin unusable with subprojects #347

mattmess1221 opened this issue Mar 10, 2016 · 8 comments

Comments

@mattmess1221
Copy link
Contributor

I have a couple projects with the liteloader plugin applied. When the root project has it, it crashes. I'm suspecting a configuration is somehow null.

Log: http://pastebin.com/QthGEk4t
Repo: https://github.com/killjoy1221/TabbyChat-2/tree/1.8.9

@AbrarSyed
Copy link
Member

@Mumfrey !!!

Mumfrey added a commit to Mumfrey/ForgeGradle that referenced this issue Mar 10, 2016
@Mumfrey
Copy link

Mumfrey commented Mar 10, 2016

Fix should be something like this

@Mumfrey
Copy link

Mumfrey commented Mar 10, 2016

I'm on an event from tomorrow for the following week so if that doesn't fix it then I'll look into it when I get back.

@mattmess1221
Copy link
Contributor Author

On this note, what's the reason you decided to add liteloader to every project instead of just the one it was applied on? I think that removing the allprojects entirely would resolve it.

Mumfrey added a commit to Mumfrey/ForgeGradle that referenced this issue Mar 11, 2016
@Mumfrey
Copy link

Mumfrey commented Mar 11, 2016

@killjoy1221 oh I see you're right. I was in a hurry yesterday so didn't actually look at it that closely. I think what happened is that the allprojects closure is supposed to add the repo the same way it's done here, here and here but the second part of the logic should not be in the allprojects closure.

This makes the fix look more like this where the logic for that method is moved out of the allprojects closure.

Mumfrey added a commit to Mumfrey/ForgeGradle that referenced this issue Mar 11, 2016
@Mumfrey
Copy link

Mumfrey commented Mar 21, 2016

Hey @killjoy1221 I'm back now, if you can confirm that the changes in the commit I mentioned above fix the issue then I'll open a PR.

@mattmess1221
Copy link
Contributor Author

👍

@AbrarSyed
Copy link
Member

PR please?

mattmess1221 pushed a commit to mattmess1221/ForgeGradle that referenced this issue Mar 31, 2016
mattmess1221 pushed a commit to mattmess1221/ForgeGradle that referenced this issue Mar 31, 2016
Mumfrey added a commit to Mumfrey/ForgeGradle that referenced this issue Apr 21, 2016
mattmess1221 pushed a commit to mattmess1221/ForgeGradle that referenced this issue May 4, 2016
LexManos added a commit that referenced this issue Dec 27, 2016
Fix for #347 and add support for description keys in litemod.json
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants