JSF 2.0 Managed Beans in Maia
July 3rd, 2009 by serega.vasilievMaia lets you reference JSF 2.0 managed beans directly from Java code and provides completion, usage search and core refactorings for them.

Maia lets you reference JSF 2.0 managed beans directly from Java code and provides completion, usage search and core refactorings for them.

IntelliJ IDEA 9M1 supports debugging of JavaScript code in Mozilla Firefox. Just create a JavaScript Debug configuration, select Firefox from the Browser list and click OK:
IntelliJ IDEA automatically installs plugin for Mozilla Firefox and executes the configuration.
Note that you need to clear Make option under Before launch group before starting debugger to work around a bug that will be fixed in next Maia EAP.
Maia supports preview of icons you are using in Java code directly from the editor. For each of the icon definitions (javax.swing.Icon), Maia tries to locate a file from which it is loaded and then shows a preview in the gutter bar. You can click it to open the image for editing, of course.![]()
We’re happy to announce the first Milestone release of upcoming IntelliJ IDEA 9, nicknamed Maia.
This release delivers a fresh preview of features and improvements we’ve implemented so far for IntelliJ IDEA 9:
You’re welcome to download IntelliJ IDEA 9M1, traditionally available for Windows, Mac OS X and Unix systems.
With Maia it’s easy to target a specific version of Flash player for your Flex/AIR applications. All you need is to specify it on the Flex Compiler Settings tab of a Flex module or facet:
With Flex SDK 3.2.0 or later you can target players of either version 9 or 10. Remember that version of playerglobal.swc library attached to module or facet SDK must match your target selection. Maia takes care of it by automatically changing SDK to an one that contains required library. If there is no such SDK, it will be created for you. By the way, a default Flex SDK name contains major version of target player:
AIR SDK name does not contain target player information because it does not include playerglobal.swc library, and airglobal.swc library does not vary from version.
Note: Changing a target player version for Flex module or facet may lead to changes it its SDK configuration and vice versa — if you change module or facet Flex SDK, it may affect the target player version settings.
In IntelliJ IDEA 8.x there is no special configuration setting for target player version, so to target a custom player version you need to change playerglobal.swc library attached to the used SDK manually (either <Flex SDK>/frameworks/libs/player/9/playerglobal.swc or <Flex SDK>/frameworks/libs/player/10/playerglobal.swc) and also to write Additional compiler option like -target-player=10
Maia brings you an improved Show Usages popup (Ctrl+Alt+F7):

Maia includes support for running FlexUnit 4 tests. All you need is to a add dependency to FlexUnit4.swc library and your FlexUnit4-style tests will be recognized and run. FlexUnit4 runner supports legacy tests (FlexUnit 0.9 and Flunit), so you don’t have to worry about existing code. Maia also includes some nifty testing support features:

Test with pleasure!
IntelliJ IDEA 8.1.3 update is available. Download the fresh build that includes:
For more information about fixes and improvements see Release Notes.
Today we’ve released an updated version of the Python plugin, with support for both IntelliJ IDEA 8 and “Maia” EAP. New features of the plugin include:
You can find detailed release notes and screenshots of the new plugin on our Confluence space.
Groovy language support becomes a little bit better in Maia with the support for named parameters completion. Maia is now capable of displaying all named parameters ever used in method bodies.
