JetBrains elected to the JCP Executive Committee

Trisha Gee

Recently the Java Community Process had a Special Election to fill the two vacant ratified seats on the Executive Committee (EC).  JetBrains was honoured to be elected, and will serve on the Executive Committee until 2018.

The Java Community Process is the mechanism for developing specifications for Java. Java Specification Requests (which may cover Java EE specs, for example, or define what’s going to be in the next version of Java) describe the standards for new (or sometimes existing) functionality, and the JSRs have to pass through a series of gateways before they are finally approved and become an official part of the Java landscape. At each of these gateways, the Executive Committee members vote on whether they should progress, and may give feedback on changes that need to be made to the spec.  This is a really important part of making sure that official parts of the language have been looked at by the wider community (EC members represent vendors, user groups and individuals) before being dropped onto developers.

The process of the Executive Committee approving Java Specification Requests (JSRs) has recently been in the news after the unusual “no” vote on Jigsaw’s  public review. JetBrains joined the EC too late to vote on that first round, but this interesting situation has brought a lot of visibility to the whole process, and we’re excited to be part of it.

We believe it’s important for JetBrains to be on the JCP EC.  We can pass on feedback from users like you to those who create the specifications for the language.  Where you have frustrations or questions, we can use those to push the Java platform in a direction that makes your life easier.  It also means we have a clear view of upcoming changes in the language and the common frameworks we use, and we’ll do what we always do – evolve our tools inline with these changes.

The JetBrains representatives on the Executive Committee are Anna Kozlova and me, Trisha Gee. I’ve a bit of experience with the EC from when I was in the JCP working group for the London Java Community, and I’m looking forward to being involved again.  We’re not the only JetBrains people who get to have a say, we’ve formed a working group of people inside JetBrains who share an interest in the specifications that are coming and in the future of Java, so our votes will represent diverse opinions and voices.  Most importantly, we hope to represent you, the users, on the JCP EC.

Comments below can no longer be edited.

14 Responses to JetBrains elected to the JCP Executive Committee

  1. Armando Picon says:

    July 5, 2017

    A really good news for Java… Could be a second chance to build a better Java?

    • Trisha Gee says:

      July 5, 2017

      Thanks! We hope that we can help evolve Java in a way that’s useful for developers.

  2. Paul Vinogradoff says:

    July 5, 2017

    Congratulations to all at JetBrains on this appointment. It is recognition of the quality and integrity of your drive to develop.

    • Trisha Gee says:

      July 6, 2017

      Thank you!

  3. kebernet says:

    July 6, 2017


  4. vitalij says:

    July 6, 2017

    Should we expect to have official Kotlin support?

    • Trisha Gee says:

      July 6, 2017

      From Oracle? No, the JCP is just about the standards for Java/Java EE.

  5. Sebastian says:

    July 6, 2017

    I got a few wishes, which you might want to consider to bring up:

    – faster releases like a Java language update each year (with fixed release timings like you got it for the JetBrains products); TypeScript development can be looked at
    – support for pattern matching
    – support for case classes

    For the latter two, there is already a good proposal at

    In addition, I like to see more natural support for JSON (and XML and YAML). Basically, I want to do something like:

    JsonObject obj = { “values”: [ “foo”: “bar” ] }
    JsonArray arr = obj[“values”]

    Even with JSON-P a lot of code is required to create a simple JSON object.

    • Trisha Gee says:

      July 6, 2017

      1) Faster releases have already been hinted at by the JDK developers. This should hopefully be made possible by Jigsaw.
      2) The JCP is responsible for approving standards, not implementations. New standards can be suggested my any JCP member (not just EC members like JetBrains) here: Standards are generally more likely to be approved if there is at least one reference implementation. For core language features, this is usually found in the OpenJDK. Additions to the OpenJDK are managed through JEPs (Java Enhancement Proposals) – note that there is a JEP for a Lightweight JSON API and that there’s a lot of interest from the community to get this into a version of Java very soon. Other standards like JPA came about through libraries like Hibernate.

      It’s sometimes frustrating that the process is so heavy and slow, but it is improving! And the good news is that really great ideas for features or standards do often come from the community, via open source libraries that are developed and used by “real life” developers, not just the Oracle JDK developers. We’d be really happy to support any proposal that the community finds useful because it makes developers lives easier.

      Thanks for your comment, I agree that these are all areas that need work.

  6. Sebastian says:

    July 6, 2017

    The different processes are very confusing if you don’t work with them on a daily basis 🙂

    I did some search and it seems my wishes are documented / on their way to some degree:

    – pattern matching – JEP 305
    – easier JSON handling – JEP 198
    – cases classes – implemented by popular Lombok library

    Let’s hope for the best 🙂

    • Trisha Gee says:

      July 7, 2017

      I agree, the processes are confusing. JetBrains would like to improve this in two ways – one, by letting developers know what the current processes are and how to work with them, and two by helping to improve them.

      One area I’m personally interested in being involved is clarifying what goes into the OpenJDK as a JEP and then is “standardised” with a JSR, and what should perhaps start in the JCP process as a JSR and then be implemented (perhaps via the OpenJDK).

  7. Peter Schäfer says:

    July 10, 2017

    Good to hear that you are taking part in the community process.
    I want to put one issue on the wishlist: Swing.
    It’s pretty sad (I hope you agree) that Swing development has stalled,
    and maybe JetBrains could revive interest in Swing.
    So is my faint hope…

    • Trisha Gee says:

      July 12, 2017

      Well… we can do our best. But I’m pretty sure Oracle is not excited about investing in Java front-end technologies 🙁

      Plus at the moment JavaScript and web technologies are racing ahead and grabbing mind-share, so I think we might have to ride that wave before looking at other UI technologies.

      • Peter Schäfer says:

        July 13, 2017

        I think Java’s strength is diversity.
        Though desktop technology is not fashionable anymore, it’s still useful and worth supporting.