search

autaut03 / kottle

Kotlin language provider for Forge 1.13.2+
GNU Lesser General Public License v3.0
30 stars 13 forks source link

Gradle dependency no longer recognizes kottle #10

Closed AlexCouch closed 5 years ago

AlexCouch commented 5 years ago

I am just wondering if you changed the way you use kottle as a dependency. Your readme hasn't been updated since 1.0.6 so did you get a maven or something?

autaut03 commented 5 years ago

Hey. No, I did not change anything, though readme is a bit outdated.

JPitman97 commented 5 years ago

Hi!, having the same issue as above, When compiling I get Execution failed for task ':compileKotlin'.

Could not resolve all files for configuration ':compileClasspath'. Could not find kottle:Kottle:1.1.1. (I am using 1.1.1 as on Curse it shows as the compatible version with 1.14, however I also tried other versions with the same result)

autaut03 commented 5 years ago

@Trxnce Hi. I'll look into it later today.

JPitman97 commented 5 years ago

Hi, any updates on this?

autaut03 commented 5 years ago

@AlexCouch, @Trxnce,

So I just tried it with this gradle config and it worked perfectly.

Could you show me your config you're having problems with?

JPitman97 commented 5 years ago

Hi, using the gradle config you posted seems to of fixed the issue and Minecraft now compiles and launches, appreciate the help

autaut03 commented 5 years ago

@Trxnce Please, provide your gradle config so I can reproduce it. Thanks in advance.

JPitman97 commented 5 years ago

Hi, sorry mate but I deleted the old file when I got the new one working, one thing I noted I was missing from the one you posted was

repositories { maven { url 'https://minecraft.curseforge.com/api/maven/' } mavenCentral() }

Once I added that it seems to work, the gradle config I used before was extremely similar to the one on the readme, just with the group and archive name specified

autaut03 commented 5 years ago

@Trxnce No problem. @AlexCouch Has this resolved your issue too?

AlexCouch commented 5 years ago

Yes, it was just a simple maven script issue thank you.