We are trying to blog about new features http://blogs.jetbrains.com/idea/tag/maia/

The preliminary roadmap looks like following:

Core Functionality

• Performance improvements
  • Faster startup
  • Better IDE responsiveness (reducing lags during typing)
  • Faster background code analysis
• Background building of indexes
• Floating editor tabs
• Packaging configurations
  • More flexible way to specify how a desktop or Web app is packaged into .jar/.war/.ear etc.
  • Multiple packaging configurations per project
  • Visual UI for specifying layout
  • Possibility to run IDEA build and packaging process from command line or Ant task
• OSGi support
  • Running apps under OSGi container
  • Support for OSGi bundle dependencies and exported/imported packages in code insight features
• Task-based UI
  • Associating additional context with a task (tests, breakpoints, favorites etc.)
  • Sharing a changelist between multiple developers without committing it to VCS
• Offline modules
  • Possibility to choose whether a part of a project is loaded as a source module or as a library
• "Code Cleanup" (batch execution of formatter + optimize imports + inspection quickfixes)
• Concurrency-oriented refactorings
• Spell checker

#Frameworks and Technologies

• JavaEE 6 support
  • JaxWS 2.2
  • Jaxb 2.2
  • WebBeans
  • JSF 2.0
  • JPA 2.0
  • EJB 3.1
  • Servlets 3.0
  • JSP 2.1
  • Beans validation
• Spring 3 support
• Tapestry support
• Adobe AIR support
• JavaScript / ActionScript refactorings
• Android support
• Initial JavaFX support (syntax highlighting, compiler, run configuration)
• Improved JavaScript debugger (Firefox plugin)

Well, I'd say Wicket and Google App Engine.

Perhabs, it is time to start EAP for Google App Engine Integration plugin http://plugins.intellij.net/plugin/?id=4254

If you are working on Tabs, maybe you could consider the idea of Tab Groups, for those of use that work with hordes of files.

I have a feeling that Spring support was not a priority after the initial release of 8.0. Even though Spring integration was improved in many areas in 8.x, there are still quite a few bugs and regressions there. I can only hope that support of all fancy new technologies and frameworks does not completely divert Jetbrains resources from support the core thing that Spring is.

Dmitry,

To support my statement, below is a list of issues that I raised over the last year or so. Some of them are assigned to you, some to the other team members. There is about a dozen of other annoying issues that I know about, but did not yet have time to write proper test scenarios and file jira tickets. You know that I always try to help you by providing as detailed description of a problem as possible. Please also note that most of the issues below are related to plain core Spring, applicable to any version of Spring starting from 1.5.

I am not often whingeing on these forums, but looking at the release notes of 8.1.1, it is not difficult to see that a very large share of addressed issues was related to Oracle SQL support, another major share was related to Flex support. All other addressed issues were various bits and bobs, and only a handful of fixed issues is related to Spring.

Bugs:

http://www.jetbrains.net/jira/browse/IDEA-22574 "Spring Constructor/Setter Dependency" is not injected into all bean definitions

http://www.jetbrains.net/jira/browse/IDEA-22515 "Move" refactoring does not work for Spring beans from the Structure pane

http://www.jetbrains.net/jira/browse/IDEADEV-35313 Spring dependencies diagram: lines for "depends-on" declarations are not drawn

http://www.jetbrains.net/jira/browse/IDEADEV-34012 Spring gutter icons not shown for 'anonymous' beans

http://www.jetbrains.net/jira/browse/IDEA-21462 Spring: "inline bean" refactoring changes order in lists

http://www.jetbrains.net/jira/browse/IDEA-21289 No intention to add missing <constructor-arg> tags, if bean declaration does not match actual constructor arguments

Feature requests:

http://www.jetbrains.net/jira/browse/IDEA-22514 Introduce "Safe delete" refactoring for Spring beans

http://www.jetbrains.net/jira/browse/IDEA-22138 Spring: navigation/completion support for PropertyPathFactoryBean and <util:property-path>

http://www.jetbrains.net/jira/browse/IDEADEV-30456 Spring: flag use of deprecated class in beans configuration file

http://www.jetbrains.net/jira/browse/IDEA-21311 Spring: navigation/completion support for MethodInvokingFactoryBean

http://www.jetbrains.net/jira/browse/IDEA-21309 Spring: "Replace <value> element with 'value' attribute" intention should be available when inspection is turned off

http://www.jetbrains.net/jira/browse/IDEA-21290 No gutter icon for a class constructor, referenced in the Spring bean declaration

http://www.jetbrains.net/jira/browse/IDEA-21273 Intention "add constructor parameter" should also update Spring bean definitions

Usability problems:

http://www.jetbrains.net/jira/browse/IDEA-22423 When a Spring file has errors, the editor tab is not highlighted

http://www.jetbrains.net/jira/browse/IDEA-21307 Ctrl+Shift+Space does not work in Spring XML files 

http://www.jetbrains.net/jira/browse/IDEA-21044 Find usages: references to a spring bean are shown as 'write access'

To be positive, I must say that the existing Spring support in IDEA8 is fabulous, but there is still a room for improvement.

Kind regards and thanks for all your efforts to date,

Sergei

I'd like to have support for Google App Engine and more of the STS (Spring Tools Suite) features including integration with recently announced Spring Roo. Considering the momentum SpringSource is getting these days I would seriously think about getting more support for their technologies rather than concentrating efforts on full range of Java EE 6 stuff and especially on yet unproven JavaFX.

I totally second the request for rock-solid Spring support in Maia. Hopefully, JetBrains will fix all the Spring usability issues outlined above. I feel that Maia should have brilliant Spring integration. Diana works very nicely with Spring, but the holes outlined above by Sergei should be plugged.  The direction that JetBrains has taken in IntelliJ 8.1 is good and I appreciate the attention paid to startup time, better responsiveness, better usability, etc.

One thing I would personally like to see is automated QA done by JetBrains against all external (non-JetBrains) plugins. When these plugins are found to be defective, users should not be allowed to install them instead of disabling them from the IDE or manually removing them in some cases.

One question though ....... will we have to wait for Maia for Spring 3.0 support or will this be also available in Diana at some point?

I should mention that professionally (and for my organization) Spring and Groovy/Grails support is the most important.  I just do Android on the side.  But you will pull over a lot 'Droid Developers by adding Android support.