Great news for those who wait for new exciting features from IntelliJ IDEA. We are happy to announce that Early Access Program for IntelliJ IDEA 12 has officially started. The code name for new IntelliJ IDEA 12 is Leda. You’re welcome on the cutting edge!
To try new features of IntelliJ IDEA Leda just download EAP build for your platform.
The major features of the release include:
|
 |
Stay tuned for more details on these and other new features soon to appear in our blog.
We believe that making perfect tools for developers is only possible when listening to feedback from the community. That’s why we would be pleased to get feedback from you about IntelliJ IDEA 12.
Please share your impressions on EAP discussion forum and submit bugs to the issue tracker.
Please note that Early Access Program offers features which are still under development. This means that the quality may be far below even beta standards. We strongly recommend to backup your project before the first run.
Develop with pleasure!
IntelliJ IDEA Team
Cool! Thank you. What’s about Play! 2.0 support?
Awesome! Do you an idea (no pun intended) when v12 will be released? We are looking at upgrading from v9, so we don’t wanna be “stuck” with v11 when v12 is around the corner.
How about an updated Ruby plugin that doesn’t have the deadlocks?
WarnerJan,
IntelliJ IDEA 12 will be released before the end of 2012, most likely in late November/early December.
David,
An updated Ruby plugin for Leda will be released at a later time.
What license should I have to use this EAP ? If Idea 11 license will be enough to run it more then 30 days ?
What is the ‘Brand New Compiler Mode’? You can’t just leave it at that!
I get a lot of:
org.jetbrains.android.uipreview.RenderingException: This version of the rendering library is more recent than your version of IntelliJ IDEA. Please update IntelliJ IDEA
at org.jetbrains.android.uipreview.RenderServiceFactory.loadLibrary(RenderServiceFactory.java:158)
at org.jetbrains.android.uipreview.RenderServiceFactory.create(RenderServiceFactory.java:73)
at org.jetbrains.android.sdk.AndroidTargetData.getRenderServiceFactory(AndroidTargetData.java:74)
at org.jetbrains.android.uipreview.RenderUtil.renderLayout(RenderUtil.java:98)
at com.intellij.android.designer.designSurface.AndroidDesignerEditorPanel$8.run(AndroidDesignerEditorPanel.java:258)
at com.intellij.openapi.application.impl.ApplicationImpl$6.run(ApplicationImpl.java:457)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
at com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:148)
But I think it’s because I am using the latest Android SDK
Yole,
Thanks for the info. Looking forward to Idea 12
More details on Brand New Compiler Mode coming soon.
Looking for improved Gradle support. More on par with the current support for Ant and Maven, when editing build.gradle files.
On the EAP page, the new compiler stuff is really cool : Incremental Java Compilation !
Compilation subsystem rewrite: “External make” feature
– The new make is by default off, can be enabled on a per-project basis from “Settings | Compiler | Use out-of-process build for project compilation” checkbox.
– Currently supported: incremental compilation of Java, Groovy, resource copying, UI Designer forms, Artifacts, Android, annotation processing, not-null instrumentation
– Currently NOT SUPPORTED: projects that store data in Eclipse format, Grails-specific instrumentation
Highlights:
– all compilation tasks are performed in a separate process, fully independent from IDE’s VM, no interference with AWT thread, no IDE resources consumption during build
lower memory requirements for the IDE.
– in the make process javac compiler is called in “in-process” mode via java API, hence faster java sources compilation
– java make: completely rewritten java classes dependency management for faster and more accurate search of dependent classes
– ‘automake’ mode: automatic make triggered by events from IDE’s virtual file system. If such make resulted in errors, those are highlighted in Project View and editor tabs
– faster project rebuild
@Andrey: EAP comes with license key built-in. You do not need any keys to use it.
Every EAP build is also time-limited. So, you will need to updated it to a newer one eventually.
Frostman, we are adding support for play 2.0 (IDEA-82967).
finally, we are going to support in Idea12 – drools, clouds, new spring related projects, vaadin, jee7.
Need JavaFX 2 support
Brice, we’ve had incremental java compilation from version 1.0.
By ‘incremental’ I mean “no need to compile whole project every time”.
+1 for an updated ruby plugin. I won’t be able to participate in preview until there is one available.
Brand new compiler mode – that’s sounds like a the final argument against IntelliJ has been met. I recently tried, again, migrating from Eclipse and am really annoyed when I do TDD as IntelliJ is much slower in starting a test suite.
It is so bad it actually lowers productivity as I get distracted when waiting for the “make”, “parse”, “load”, etc.
Don’t use it over current code or yours caches and local history will be lost
Hello,
Either with 4.1 or 4.0.3 Android SDK we have the following exception when trying to edit a simple app main layout:
org.jetbrains.android.uipreview.RenderingException: This version of the rendering library is more recent than your version of IntelliJ IDEA. Please update IntelliJ IDEA
at org.jetbrains.android.uipreview.RenderServiceFactory.loadLibrary(RenderServiceFactory.java:158)
at org.jetbrains.android.uipreview.RenderServiceFactory.create(RenderServiceFactory.java:73)
at org.jetbrains.android.sdk.AndroidTargetData.getRenderServiceFactory(AndroidTargetData.java:74)
at org.jetbrains.android.uipreview.RenderUtil.renderLayout(RenderUtil.java:98)
at com.intellij.android.designer.designSurface.AndroidDesignerEditorPanel$8.run(AndroidDesignerEditorPanel.java:258)
at com.intellij.openapi.application.impl.ApplicationImpl$6.run(ApplicationImpl.java:457)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
at com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:148)
Will you be supporting the Play Framework 2.0 (for both Java and Scala)?
I see a note on purchase on buy&upgrade page
“any IntelliJ IDEA 10 license purchased after November 07, 2011, qualifies for a free upgrade to IntelliJ IDEA 11.”
I wonder if you are going to offer free upgrade of 11 to 12 before the release? I am considering to buy a personel licence
I’m hoping for Play 2 support too. Play 1.2 is in legacy mode now.
@Eugene I have the same feeling as Per Lundholm. However I confer that maven had some role to play there
+1 Play Framework 2.0 support. Whats most needed is the ability to have correct interpretation of scala template files
cannot deploy on startup.i’ve submitted bugs to central youtrack.
this is a huge problem keeps me aways from trying out those great features.
Great list of features.. Taking it for a spin shortly. Play 2 support welcome. Spring Hadoop support would be cool as well.
I’m really hoping for the ability to debug javascript tests especially with JsTestDriver, but nodeunit would be great too. Nothing else matters at the moment
Hey guys,
Been expecting a lot from you since gr8conf. I must admit I am impressed with your vision
TomEE + Groovy 2.0 support ? what do people ask huh ? 
I agree with Jens R – I am seriously looking forward to world-class support for Gradle in IDEA-12 (Leda) – along the lines of Maven. IDEA already has brilliant support for Maven, so please extend this level of support to Gradle too. I’ve had great success with Gradle for building Groovy projects and am looking forward to using it more and more. GMaven is just god-awful for Groovy and doesn’t work at all.
+1 JavaFX 2.0 support. Would be awesome. Eclipse has it and Netbeans too, so why not in Intellij ?
I’d really wish idea 12 will have support for JavaFX too!
It must have JavaFX 2.0.
Please tell me you are not omitting JavaFX2.0 support. If you are, someone has made a big mistake.
Where is awesome goose on the splash screen it was removed from RC, will it be returned in release version? I am waiting for the goose about half year !!!
Return the goose. http://blogs.jetbrains.com/idea/wp-content/uploads/2012/06/splash12_blog.png
Freedom to the geese!!!
Where is the cool goose from Leda preview? Bring the goose back!
Come on guys….why replace the goose with some boring generic splash screen…… I demand the goose!