JetBrains IntelliJ IDEA Blog

In the upcoming Maia EAP you won’t find separate actions for creating classes, interfaces, enums or @interface anymore. Just one action that does not clutter your desktop — New Java Class.
This does not mean you won’t be able to create interfaces, enums and annotation types, though:

The same functionality will be available for Groovy classes.

Developing AIR applications with Maia is easy. Basically all you need is to add an AIR SDK:

Then, select AIR SDK at New Flex Module Wizard step. You can also select an option to automatically create AIR application and descriptor: (more…)

Maia brings you the support of Apache Derby SQL dialect. Just as with all others, you can set it at project, folder and individual file levels either via Project Settings section of Settings dialog:
Or by invoking a quick-fix on any error marker inside of an .sql file with Alt+Enter shortcut:

Maia provides comprehensive support for Apache Tapestry, the Web application framework. The first EAP features the Tapestry support essentials that include:

• Standard way to enable the technology for a module.
  
• Simple facet for quick configuration
  
• Navigation from Tapestry related tag names/attributes to corresponding Tapestry entities.
  
• Navigation between the template and the class of a component, a page or a mixin
• Actions to create components, pages or mixins in proper location.
• Standard Colors&Fonts setting page for Tapestry-related tag names and attributes.

Also, a Tapestry-enabled module is created with all required package structure and web.xml content:

The Type Hierarchy action (Ctrl+H shortcut or View menu, Type Hierarchy) works in IntelliJ IDEA 9 (Maia) for Flex sources (*.mxml and *.as files) showing class, superclass and subclass hierarchy in the same way as for Java sources.

Maia supports Subversion 1.6 using svnkit 1.3.0. Tree conflicts are detected.
You can mark tree conflicts as resolved.

We’ve been blogging about the cool new features implemented in the EAP builds of Maia (IntelliJ IDEA 9) for a while, and now at last you can download and try the new build for yourself.

The new features available in the new build include:

• Backgroundable file indexing, limited navigation / editing / VCS functionality during such process.
• JEE 6 EA support, currently:
  • JPA 2.0 (JSR-317)
  • EJB 3.1 (JSR-318)
  • JSF 2.0 (JSR-314)
  • WebBeans (JSR-299)
  • Bean Validation (JSR-303)
• PHP support
• Tapestry support
• OSGI support
• JavaScript debugger via Firefox plugin
• GWT 1.6 support (see IDEADEV-34713 for details)
• Task context management
• Spell checker
• Grails Project View
• SmartType completion after ‘new’ in Groovy
• Closure and generic parameters foldings
• Easy class exclusion from completion & auto-import
• Highlighting of globally unused symbols

We’re eagerly waiting for your feedback on the new build. Feel free to let us know what you think on the forums, and post bugs and feature requests to our issue tracker.

And may you always develop with pleasure!

Maia is capable of running FlexUnit tests — you can run a single test method, all methods in a certain class, or all classes in a given package and its subpackages. For that, you’re provided with a new FlexUnit Run Configuration, which allows you to specify a module (Flex module or Java module with Flex facet) and configure the test scope:



To run tests you need to set up a dependency on FlexUnit.swc library, but this is something you must have already done to get your tests compiled. Tests are actually executed in debug mode with all the functionality like breakpoints, watches, etc. available.

When a run is finished the results window shows you the tests overview, output and statistics panel:



Mouse click on an item in the tree or statistics panel navigates you to the test source. Same is true for the stack traces of the failed tests.

Also, new context menu actions are provided to run test for a selected method, class, or package. Just right-click them and select Debug Flex, then click FlexUnit.

First Maia EAP brings you the following JavaEE support improvements:

• EJB 3.1 @Singleton Session Bean
  
• JPA 2.0 @ElementCollection attribute type, plus freshly allowed attribute types in embeddable objects (@OneToOne, @Embedded, etc.)
• JPA 1.0/2.0 with Hibernate provider will not throw false-positive warnings about certain JPA specification violations that occur because of differences in JPA and Hibernate.

Maia supports Spring 3.0 Java Configuration via:

• Usage search and Rename refactoring:
  
  
• Code completion:
  
  
• Syntax and error highlighting:
  
  

You can also search java-configured beans using Search by symbol action, view beans on Spring dependency diagram and more.