Unclear, we’ll see how things go but inertia alone will probably make Gradle/Kotlin the new standard

Over the past few days, I had come to the realization that I was probably ready to call Kobalt 1.0

it has all the features I set to implement six months ago and even more (IDEA plug-in awesome improvements thanks to @dmitry.zhuravlev )

Yes, so many awesome stuff, and this gets announced, kinda makes me sad

maybe Gradle is silently preparing an acquiring proposal to Kobalt 😉 ?

Kradle 😛

You know, when I started TestNG, my goal was only to play with some new stuff and show what was possible (annotations, groups, etc…). My goal was nothing more than hoping the JUnit team would pick up on that and implement these features in JUnit. It’s no different with Kobalt: experimenting with new ideas, showing what’s possible, trying to advance the state of the art

Which things of Kobalt would you like to view in Gradle?

I think the DSL is better than Gradle's and the plugin system is elegant

Yes I like these two aspects too. The fact the plug-in system is fully statically typed and 100% “Hollywood principle” makes the delineation between plug-in and core crystal clear. It’s much less clean in Gradle in my opinion, where plug-ins routinely modify internal Gradle state to get things done

@cedric: I still prefer Kobalt as it has variants built-in

Glad to hear it. Interestingly, I’ve never needed it so far (besides on Android) but I put it in the core because it’s obvious to me that this is where it belongs, not in a plug-in.

Hi everyone. I just joined the channel and I’ve read the posts since early April. Just as I get excited about trying Kobalt and moving my Gradle plugins over I see posts that questions the long term for Kobalt. My input - Gradle (and I’ve wrestled with it since the early days) is really hard to stabilize. I looked at SBT for a long time but finally decided I didn’t like Scala. I strongly prefer strong-type checking environments. So… Kobalt caught my attention. I’m not sure what the plans are for this build system, and I’m still an outsider who wants to dive in … but I hope this project continues forward. And then a question - if I want to start looking at moving over plugins, should I just grab the latest and work with that or is there an older release that everyone considers “stable” and representative of the final form?

Hi @randolph.kahle, and welcome!

Picking the latest is good, you can go with that.

Note that there are two different versions: the kobalt “app”, which is what you use to build things with, and which I iterate on pretty often (several times a day) and the

kobalt-plugin-api

, which is what you should use for plug-ins and which I don’t update as often (only when I make significant changes to the plug-in API)

Also, note that just today, JetBrains and Gradle announced a partnership which will make Kotlin a first class language to write Gradle build files. You should keep an eye on that

I saw that announcement. That’s what caused me to post now about the future of Kobalt. Forgive me for sounding skeptical but it’s the inner logic of Gradle that used to drive me crazy. Maybe it is better now.

Thanks for the tips, I’ll start to dig in.

Don’t hesitate to ask if you have questions!

I installed the plugin into IntelliJ and the IDE started to report errors. Should I drive things from outside of the IDE or push on forward with the IDE plugin?

First make sure everything builds from the shell, then please file bugs if anything goes wrong in the IDE

What are you seeing?

25437 PM StringIndexOutOfBoundsException: String index out of range: 0 25442 PM StringIndexOutOfBoundsException: String index out of range: 0 25704 PM Unable to save settings: Failed to save settings. Please restart IntelliJ IDEA

Let me rework all of this and then I’ll let you know if I have problems.

mmh odd, maybe a Kotlin version clash? Is that from the Kobalt IDEA plug-in?

I need to create a clean project

oh! Maybe

Ok file a bug once you think you have something reproducible

@cedric: i think Kobalt is a great tool. First build tool i've ever enjoyed using. There have been bumps in the road but it's a fine tool.