Calling on EAPers

At JetBrains we’ve always believed in our Early Access Program for our tools, giving developers a chance to use the latest features or fixes as soon as they’re ready. We’ve followed the same philosophy with Kotlin, knowing of course that with a language, some decisions can haunt you for life.

That is why during the pre-release days of Kotlin, we’d have milestone releases with features and important changes for our early adopters (including ourselves at JetBrains), collect feedback on whether things were working as designed. This release-feedback-adjust cycle has proven invaluable in so many occasions and has definitely helped shape Kotlin 1.0.

But it’s not over with the release. We’re still continuing to develop Kotlin with new language features and we need your continued support. As you know, we have two ‘branches’ of EAP’s, the 1.0.X ones which are more about bug fixes and tooling, and the 1.1 EAP which is about language changes. And it’s with these EAP’s, the ones with language changes, where we could really use your help. While we don’t recommend you using these 1.1 EAP’s in production code, we definitely do need you to give us feedback. In return, we promise to listen to everything you have to say!

Using EAP’s

The easiest way to access EAP’s is via the Tools menu. Open Tools | Kotlin | Configure Kotlin Plugin Updates in the main menu, select Early Access Preview channel 1.0.x or 1.1 and press the Check for updates now button.
Screen Shot 2016-08-01 at 17.55.03
To use the new builds from Maven or Gradle: add https://dl.bintray.com/kotlin/kotlin-eap or https://dl.bintray.com/kotlin/kotlin-eap-1.1 as a repository to your project

At the moment the first EAP of Kotlin 1.1 is available (with coroutines, type aliases, bound callable reference, local delegated properties, Java 7/8 support and many more). Also today we just published first EAP build of Kotlin 1.0.4 with lots of bugs fixes in the compiler and IDE, whole bunch of new intentions, inspections and quickfixes, and it’s now fully compatible with Gradle 2.14.1. For more information check out the full Kotlin 1.0.4 changelog

Giving Feedback

Most of the Kotlin team are available on our public (Slack community), and specifically on the #eap channel, where we’re very eager to listen to your feedback and help with any questions or issues you may have. Of course, our issue tracker is always open too

One of our main goals with Kotlin has always been to make it an industrial language that is pragmatic. And it’s by using Kotlin in many types of applications and scenarios that will help us achieve this goal. For this, we continue to need your help!

Thank you and let’s Kotlin!

Comments below can no longer be edited.

8 Responses to Calling on EAPers

  1. Avatar

    A Dev says:

    August 4, 2016

    IntelliJ needs better support for gradle projects

    I still find it to be a pain to manage

    Please add a GUI to manage/add/remove modules, repositories and dependencies, and to run tasks

    Just like how you did with Nuget in Rider, it is perfect

    • Avatar

      Andrew M says:

      August 6, 2016

      If you have an issues with gradle source sets you can downgrade to 2016.1.3 version.
      After this release support of gradle source set is completely mess 🙁
      I think there is the need in IDEA developers 😉

    • Avatar

      Lanka says:

      August 7, 2016

      My top wish is to reduce the CPU usage of Gradle. It’s painful to hear the fan noise of macbook after making any trivial change to Gradle files.

  2. Avatar

    Michael Blume says:

    August 4, 2016

    I think the URL given in the post is wrong — should be


    • Avatar

      Roman Belov says:

      August 4, 2016

      Thanks for pointing it out! Fixed now.

  3. Avatar

    Grdykopląs Namorzyn says:

    August 6, 2016

    If I use 1.1 EAP – are “old” features stable and only “new” features non-production ready or should I expect problems even with just 1.0.x code?

    • Avatar

      Roman Belov says:

      August 9, 2016

      Most probably you’ll have no problems with 1.0.x code and it will works fine. The problem with 1.1 features is not that they are not stable, but some new language constructions can slightly evolve from milestone to milestone.

  4. Avatar

    jk says:

    August 16, 2016

    How do you go back to stable after playing with EAP?

Discover more