kotlinlang #kobalt

║  semver-example-kotlin         ║ SUCCESS     ║ 9.83     ║
          ║  java                          ║ FAILED      ║ 4.02     ║
          ╚═════════════════════════════════════════════════════════╝

cedric

04/24/2017, 5:43 PM

Wait a minute, you have two projects sharing the same directory

ethauvin

04/24/2017, 5:44 PM

Copy code

╔═════════════════════════════════════════════════════════╗
          ║  Project                       ║ Build status║ Time     ║
          ╠═════════════════════════════════════════════════════════╣
          ║  semver-example-kotlin         ║ SUCCESS     ║ 20.32    ║
          ║  java                          ║ FAILED      ║ 8.07     ║
          ╚═════════════════════════════════════════════════════════╝

cedric

04/24/2017, 5:44 PM

Are you launching with

clean

ethauvin

04/24/2017, 5:44 PM

$ ./kobaltw clean java:run

cedric

04/24/2017, 5:45 PM

Try this:

./kobaltw clean && ./kobaltw assemble

ethauvin

04/24/2017, 5:46 PM

It works in 1.0.72, btw. 😉

cedric

04/24/2017, 5:46 PM

No it doesn’t

cedric

04/24/2017, 5:46 PM

Result of cleaning separately?

ethauvin

04/24/2017, 5:47 PM

Copy code

╔═════════════════════════════════════════════════════════╗
          ║  Project                       ║ Build status║ Time     ║
          ╠═════════════════════════════════════════════════════════╣
          ║  semver-example-kotlin         ║ SUCCESS     ║ 22.42    ║
          ║  java                          ║ SUCCESS     ║ 17.93    ║
          ╚═════════════════════════════════════════════════════════╝

cedric

04/24/2017, 5:47 PM

yup

cedric

04/24/2017, 5:47 PM

Here’s what’s happening:

cedric

04/24/2017, 5:48 PM

1. Clean first project 2. Run and build project, apt works 3. Clean second project 4. Oops you just deleted the generated files from the first project (since they are in the same directory)

cedric

04/24/2017, 5:50 PM

Why do you have two projects in the first place?

ethauvin

04/24/2017, 5:51 PM

one execute from kotlin, one from java.

cedric

04/24/2017, 5:51 PM

So just to have two different

mainClass

ethauvin

04/24/2017, 5:51 PM

Yeah.

ethauvin

04/24/2017, 5:52 PM

a koltin one, and a java one.

cedric

04/24/2017, 5:52 PM

Mmmh interesting scenario

cedric

04/24/2017, 5:52 PM

So first of all, does the failure I explained make sense?

ethauvin

04/24/2017, 5:52 PM

It used to work though. Yes, it does.

cedric

04/24/2017, 5:53 PM

I don’t think it used to work, it can’t. I’m guessing you used different command lines for 72 and 74 and that gave you the impression it used to work

cedric

04/24/2017, 5:53 PM

Ok so now let’s talk about multiple main classes, wondering what would be a better way to handle that

ethauvin

04/24/2017, 5:53 PM

The command line that I used are the top of the build file.

cedric

04/24/2017, 5:54 PM

Is it possible in Gradle?

ethauvin

04/24/2017, 5:54 PM

Yeah, look at the build.gradle.

ethauvin

04/24/2017, 5:54 PM

It works.

cedric

04/24/2017, 5:54 PM

We could have multiple “run configurations” and you could have

k run:fromJava

and

k run:fromKotlin

, where you associate these strings to a main class

cedric

04/24/2017, 5:55 PM

So Gradle seems to be doing something like that:

Copy code

task(runJava, type: JavaExec) {
    main 'com.example.Example'
    classpath sourceSets.main.runtimeClasspath
}