IntelliJ IDEA 12 EAP 122.813 with Vaadin and Drools Support

Today we have released IntelliJ IDEA 12 EAP 122.813, the next preview build of upcoming IntelliJ IDEA 12 with a bunch of new features.

The major changes in the release include:

  • Support for JDK 8′s new extension methods syntax.
  • Code assistance for Drools Expert, a rule-based language from JBoss.
  • Basic Vaadin support.
  • ColdFusion debugger.

The full list of changes can be found in Release Notes.
Important note: You’ve got to perform full rebuild once if your project is compiled with new compiler. Also due to ongoing work to support JDK7 it is no longer possible to update this IntelliJ IDEA build using incremental update on Mac.

Please feel free to share your feedback and report bugs in our issue tracker.
Stay tuned for more details on these new features coming soon in our blog.
Develop with Pleasure!

About Andrey Cheptsov

Andrey Cheptsov is IntelliJ IDEA product marketing manager at JetBrains. He's passionate about productivity, programming languages and tools.
This entry was posted in EAP Releases and tagged . Bookmark the permalink.

19 Responses to IntelliJ IDEA 12 EAP 122.813 with Vaadin and Drools Support

  1. David says:

    Should PHP support be working yet? It isn’t for me and wondering if it is something wrong with my setup.

    NoClassDefFoundError: update failed for AnAction with ID=PhpListenDebugAction: Could not initialize class com.jetbrains.php.PhpIcons

  2. tomph says:

    The latest build is making the application crash when I try and boot it up. I’m running Mac OSX Mountain Lion. Was fine before. Am I able to roll back?

  3. Michael says:

    Same here … PHP isn’t working :(

  4. Jonathan Hardie says:

    Broken for me too on Mountain Lion, freezes on start-up.

  5. Michael Scholz says:

    EXTERNAL BUILD: Error: Argument 0 for @NotNull parameter of com/intellij/openapi/util/io/FileUtil.isAbsolute must not be null
    java.lang.IllegalArgumentException: Argument 0 for @NotNull parameter of com/intellij/openapi/util/io/FileUtil.isAbsolute must not be null
    at com.intellij.openapi.util.io.FileUtil.isAbsolute(FileUtil.java)
    at com.intellij.flex.model.bc.InfoFromConfigFile.getInfoFromConfigFile(InfoFromConfigFile.java:140)
    at com.intellij.flex.model.bc.impl.JpsFlexBuildConfigurationImpl.getActualOutputFilePath(JpsFlexBuildConfigurationImpl.java:273)
    at com.intellij.flex.build.FlexResourceBuildTarget.writeConfiguration(FlexResourceBuildTarget.java:122)
    at org.jetbrains.jps.incremental.storage.BuildTargetConfiguration.saveToString(BuildTargetConfiguration.java:86)
    at org.jetbrains.jps.incremental.storage.BuildTargetConfiguration.getCurrentState(BuildTargetConfiguration.java:78)
    at org.jetbrains.jps.incremental.storage.BuildTargetConfiguration.isTargetDirty(BuildTargetConfiguration.java:39)
    at org.jetbrains.jps.incremental.BuildOperations.ensureFSStateInitialized(BuildOperations.java:48)
    at org.jetbrains.jps.incremental.BuildOperations.ensureFSStateInitialized(BuildOperations.java:35)
    at org.jetbrains.jps.incremental.IncProjectBuilder.buildTargetsChunk(IncProjectBuilder.java:599)
    at org.jetbrains.jps.incremental.IncProjectBuilder.buildChunkIfAffected(IncProjectBuilder.java:540)
    at org.jetbrains.jps.incremental.IncProjectBuilder.access$200(IncProjectBuilder.java:58)
    at org.jetbrains.jps.incremental.IncProjectBuilder$3.run(IncProjectBuilder.java:477)
    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 com.intellij.util.concurrency.BoundedTaskExecutor$1.run(BoundedTaskExecutor.java:35)
    at org.jetbrains.jps.service.impl.SharedThreadPoolImpl$1.run(SharedThreadPoolImpl.java:26)
    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:662)

  6. javierg says:

    Same thing’s happening to me (also running Mountain Lion) The IDE just won’t finish loading (I’m also running the Scala plugin, FWIW)
    I was able to get a direct link to the previous installer
    http://download.jetbrains.com/idea/ideaIC-122.746.dmg
    It should help until this gets fixed

  7. Joseph says:

    Same here on Mountain Lion, the IDE gets stuck on “Scanning Files”.

  8. Sorin Jucovschi says:

    Same thing here. Mountain Lion and the IDE just crashes.

  9. Maxim Mossienko says:

    @All Mountain Lion users, for workaround, please use complete install, sorry for inconvenience

  10. Alexander Doroshko says:

    @Michael Scholz The issue is already fixed but unfortunately a bit later than this EAP was released. Temporary workaround is to disable ‘Use external build’ at Settings/Preferences | Compiler.

  11. Maxim Mossienko says:

    @David,Michael we will release PHP plugin for IntelliJ IDEA 12 shortly, once PhpStorm 6 EAP will start

  12. K.B. says:

    Hi,

    when using IDEA 12 EAP (122.813 + the one before) I noticed that only java classes in the /target/ directorys get updated when doing a change to the file. If you do same to an resource lying inside the class strcutre (e.g: foo.html for foo.class with wicket) then the file foo.class will change when compiled manually (CMD+S on OS X) but the html file will stay old. On IDEA 11 this updated both files.

    Any Idea how to solve this issue? Tried old compiler mode but it also didnt work – so far this forces me back to IDEA 11.1 as I can’t really work with it ignoring changes to html files (else full redeploy necessary, taking some minutes each);

  13. Worajedt S. says:

    Ohhhhh ColdFusion Debugger support! OMG!

    I’m trill to test the debugger with Railo & OpenBlueDragon CFML Engines also!

  14. Alexander Doroshko says:

    @K.B. Please make sure that resource patterns (Project Structure/Preferences | Compiler) include ?*.html and other resource patterns that you need.

  15. Eugene Zhuravlev says:

    @K.B. Or, if it is maven-based project and the module has been constructed from a pom.xml, all resource patters will be taken from the pom.xml only (standard resource patterns in compiler settings will be ignored for this particular module).

  16. relgames says:

    I’m disappointed with the new Welcome screen implemented by Maxim Shafirov. You have so many things to do and yet spend your time on unusable “features”. New screen is buggy – no menus, checkout doesn’t work, no way to update, can’t open global and default project settings. And developers are just closing issues reported as “won’t fix”.

    This is first time I have actually spent my time to checkout the source code and find who is responsible for this; all other versions used to just work. This one prevents me from working with pleasure.

  17. max says:

    I’m so glad my work didn’t go unnoticed! Seriously speaking, we didn’t stop there and put a quite a work into new welcome screen and open for the feedback given you’ll take a look at next EAP build.

  18. Igal says:

    any updates on the ColdFusion debugger?

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>