JetBrains IntelliJ IDEA Blog

IDEA continues to expand support for J2EE application servers and has recently adopted the integration with OSGI-based Spring dmServer.

The features of the new integration include:

• local and remote run configurations for both 1.0 and 2.0 server families
• automatic management of the libraries and bundles installed at server runtime
• dmServer platform archives (PAR) support
• OSGI-aware intentions for Java and manifest editors
• dmShell access

(more…)

Good news for Amazon Web Services (AWS) users. AWS Manager Plugin provides IntelliJ IDEA integration with Amazon Elastic Compute Cloud (EC2) and Amazon Relational Database Service (RDS).

(more…)

If you’re an IntelliJ IDEA plugin developer, you’re surely going to enjoy IntelliJ IDEA PSI Viewer (Tools -> View PSI Structure), which displays internal structure of various files, as they’re interpreted by IntelliJ IDEA. If you’re implementing a new language support, or trying to add some cool new features to what’s already supported — this viewer is what you’re gonna need a lot.

As you see, PSI Viewer is made up of of tree parts:

• An editor with file content
• PSI structure view with parent-child tree of its elements
• Area that displays references of element selected in PSI structure view.

Note that references marked as red resolve to null.

Available since build 92.35

Maia supports Servlet 3.0 specification (JSR 315). You can now create a Web application without a web.xml descriptor:

Now, configure your servlets and filters with @WebServlet and @WebFilter annotations:

Everything is recognized by IntelliJ IDEA, as well as Web fragment descriptors and static resources packaged in libraries.

You can also use built-in Glassfish v3.0 integration to deploy your applications. Good luck!

In the upcoming Maia EAP you will find a slightly different Commit Changes dialog.

• Automatic use of JobView filter on search results.
• Support for Perforce native search query syntax (in an example below we’re looking for Job in any field)

If you are developing a Java application for Google App Engine, try Google App Engine Integration plugin for IntelliJ IDEA. It will be bundled with the first Maia EAP, but you can download it right now and use with IntelliJ IDEA 8.x

After plugin is installed, start the New Project wizard, select Google App Engine and specify path to the App Engine SDK (you can download it from here, for example). IntelliJ IDEA will add all required descriptors, libraries and create a run configuration for your application, so you can quickly get started with its development.

In IntelliJ IDEA you can quickly configure language injection for XML tags, attributes and Java method parameters and their return values. Just use Inject Language Intention on the code like this:



and it will immediately turn to:




And you get the complete coding assistance, with syntax and error highlighting, completion and navigation.

This functionality is provided by the bundled IntelliLang plugin. The full configuration is available for edit in the Settings dialog (see screenshot below). Default configuration includes various mappings like RegExp language in Pattern.compile(), SQL in JDBC API calls, JPA & Hibernate QL injections and much more.

It is sometimes the case, you can create plugins you want to preserve for internal use only. With
IntelliJ IDEA you can maintain your own enterprise repository to share your plugins with team members solely.

To create a repository, we need a Web server, where our plugins will reside, and a descriptor of available plugins (updatePlugins.xml), so IntelliJ IDEA could find them. This file can be located at the same Web server, for instance. By the time we decide to use plugins from the enterprise repository, we’ll only need to specify where this descriptor resides. To do so, open the Settings dialog (Ctrl + Alt + S) and go to Updates. In the Plugin Hosts section click Add and specify path to the updatePlugins.xml.

When creating updatePlugins.xml file for your repository, follow this DTD:
http://plugins.intellij.net/dtd/idea/updatePlugins1.0.dtd, so IntelliJ IDEA would be able to recognize available plugins.
Each plugin entry in this file should contain plugin identifier and URL of the plugin repository. Additionally, we can specify here plugin version. Though, if it is not pointed out in updatePlugins.xml, IntelliJ IDEA will fish it out from the plugin *.jar.

For example, we upload MyPlugin to the Web server where the repository resides. Then we open the updatePlugins.xml and add new plugin entry, like this one:

<plugins>
  <plugin id="MyPlugin" url="http://unit:8080/myPlugin.jar" version="1.0"/>
</plugins>

And that’s all we need to do to add the plugin to our repository.

If the whole team uses customized IntelliJ IDEA, you can add the whole list of plugin hosts to the bin/idea.properties under IntelliJ IDEA installation folder. Just open this file and add the following line: -D idea.plugin.hosts=[URL1],[URL2],…[URLn] where [URL1],[URL2],…[URLn] is a comma-delimited list of the URLs to the enterprise repositories.

Once hosts are specified, plugins are automatically updated according to the schedule defined in the Check for updates field of the Updates dialog. Yet, you can update them manually any time you need it. Just open the Updates dialog and click Check now. Update Info dialog box opens showing the list of plugins from all the available enterprise repositories. You can unselect those of them you don’t want to update for some reason.
Don’t forget that updates will take effect after IntelliJ IDEA restart.

Yesterday the results of JetBrains’ annual contest for the best plug-in to IntelliJ IDEA were announced. 7 plug-ins were selected by the jury composed of IntelliJ IDEA development team members. Their respective authors will take away great cash and software prizes. The names of the winners are listed on the dedicated Plug-ins Site. There you can even see a small photo-report from the conclusive meeting of the jury

We would like to congratulate the winners, express our appreciation to the co-sponsors for the generous prizes, and encourage new participants to take part in the next year’s contest.

Great challenge and great benefits!

We’re glad to announce that Sixth and Red River Software have just released the GuiceyIDEA plugin for IntelliJ IDEA. This plugin adds support for Guice, the freshly released Google’s lightweight dependency injection framework for Java 5.

It’s really amazing that Sixth and Red River Software guys managed to develop the plugin in only a week after official Guice release. Very nice job!

Plugin extends Guice support to code completion, highlighting and other coding assistance, plus inspections, refactorings, and intelligent quick-fixes, which makes IntelliJ IDEA the perfect tool for using Guice easy and safe.

GuiceyIDEA enables you to:

• Find Guice errors at compile-time, instead of run-time
• Migrate simply between annotation-based binding and explicit binding
• Quickly generate Guice modules, providers, annotations, and interceptors
• Manage Guice scopes cleanly and safely

Check the plugin now and stay tuned with future versions that will include:

• Guice-specific refactorings
• Wizards for creating and managing Guice bindings
• Graphing and display of Guice module configurations
• Automatic download and setup of Guice libraries within IntelliJ IDEA