I m trying to port this to kotlin and merge it with my build

Question

I m trying to port this to kotlin and merge it with my buildscript for last 3 4 hours and I m completely stuck <https github com PaleoCrafter Dependency Extraction Example blob coremod separation build gradle>

jlleitschuh · Answer

Hi Bartosz Do you have an example of your attempted port that isn t working Be aware that ``` task coreJar type Jar ``` Is creating a task called `coreJar` not pulling it from some task created by a plugin The syntax to convert that to kotlin would be ``` task lt Jar gt coreJar Your logic here ```

barteks2x · Answer

I tried exactly that syntax and the ForgeGradle plugin game me that error I also tried ``` tasks coreJar Jar class logic here ``` with the same result

jlleitschuh · Answer

What error

barteks2x · Answer

``` What went wrong A problem occurred configuring root project 1 12 gt coreJar is not a jar task Can only reobf jars ```

barteks2x · Answer

this is part of ForgeGradle trying to tell me something

jlleitschuh · Answer

Can you link to your current code

barteks2x · Answer

it comes from the equivalent of this ``` reobf coreJar mappingType = SEARGE ``` which is ``` configure lt NamedDomainObjectContainer lt ReobfTaskFactory ReobfTaskWrapper gt gt create coreJar apply mappingType = ReobfMappingType SEARGE ``` my current code <https hastebin com sicemaruna scala> this is with addition to my project

jlleitschuh · Answer

You re sure that ``` configure lt NamedDomainObjectContainer lt ReobfTaskFactory ReobfTaskWrapper gt gt ``` is equivalent

barteks2x · Answer

yes I m sure

jlleitschuh · Answer

So in full you have something like this ``` task coreJar type Jar configure lt NamedDomainObjectContainer lt ReobfTaskFactory ReobfTaskWrapper gt gt create coreJar apply mappingType = ReobfMappingType SEARGE ```

barteks2x · Answer

well I have ``` tasks coreJar Jar class logic here ``` which I saw in samples

barteks2x · Answer

but basically yes

jlleitschuh · Answer

Try putting ``` configure lt NamedDomainObjectContainer lt ReobfTaskFactory ReobfTaskWrapper gt gt create coreJar apply mappingType = ReobfMappingType SEARGE ``` Into an `afterEvaluate` block and see what happens

barteks2x · Answer

well I actually have 2 of create something apply blocks I just realized that it could be bug in that plugin that makes it break when 2+ are there

barteks2x · Answer

it seems to work with afterEvaluate

barteks2x · Answer

but Ihave no idea why it s needed when it works without kotlin dsl

jlleitschuh · Answer

I agree that it s strange I m going to guess that there s an execution ordering problem

barteks2x · Answer

Considering the strange things the FG plugin does it s not that unlikely

barteks2x · Answer

well now I actually get this ``` What went wrong Execution failed for task reobfCoreJar gt org gradle jvm tasks Jar Decorated cannot be cast to org gradle api tasks bundling Jar ```

barteks2x · Answer

and the previous error is straneg too because that part that does `throw new GradleConfigurationException jarName + is not a jar task Can only reobf jars ` is in afterEvaluate in that plugin s code

jlleitschuh · Answer

So Gradle weirdness there are actually two `Jar` tasks One is just an interface for the other one

barteks2x · Answer

is it just a change in gradle internals in some version that broke the plugin

barteks2x · Answer

OH

barteks2x · Answer

default imports broke it

jlleitschuh · Answer

Yea that

jlleitschuh · Answer

Because the default `Jar` is probably different than the one the plugin expects

barteks2x · Answer

Should I report it as an issue that the `org gradle api tasks bundling Jar` needs fully qualified name to be used

barteks2x · Answer

it s impossible to use without using fully qualified name

jlleitschuh · Answer

Yea I think the forge gradle plugin needs to be updated

barteks2x · Answer

to use the other jar task

jlleitschuh · Answer

Yea

barteks2x · Answer

Good luck with getting ANY change into ForgeGradle

barteks2x · Answer

also to me it looks like `org gradle api tasks bundling Jar` is actually in the API Shouldn t that one be actually imported by default

jlleitschuh · Answer

< bamboo> or < eskatos> Can you explain the weird `Jar` api why there are two of them ect to me again because I still don t really understand I know it has something to do with not breaking the API

barteks2x · Answer

and yet it turned out to be a breaking change

jlleitschuh · Answer

True it probably changed during a major version bump ツ

barteks2x · Answer

wekk breaking change when used together with kotlin s default imports

jlleitschuh · Answer

I mean these are the same default imports used by Groovy too

barteks2x · Answer

I would be able to debug it if I could add breakpoints in gradle code

jlleitschuh · Answer

Supposedly you can but I haven t ever been able to get it to work

barteks2x · Answer

You can add them but they don t work

barteks2x · Answer

It s also unlikely it can be fixed in FG because it probably still builds against gradle 2 x

jlleitschuh · Answer

Well that s their problem That s really old they should update their build

barteks2x · Answer

its not their problem if they don t claim compatibility with gradle 4 x

jlleitschuh · Answer

ツ

barteks2x · Answer

anyway now I can try to make publishing to maven work

eskatos · Answer

Like Jonathan said Kotlin DSL default imports are the very same as the ones you get in the Groovy DSL But thanks to the Groovy magic it may work anyway but Kotlin doing strict type checking forces you to use a fqcn here Agreed that FG should update their build or you have to live with the fqcn

eskatos · Answer

After taking a closer look that s on Gradle amp Kotlin DSL The Groovy DSL actually imports the old `Jar` task by default This will be fixed in the upcoming Gradle 4 3