IntelliJ IDEA 7.0.3: Maven Integration Improvements

Each new IntelliJ IDEA version brings lots of different enhancements. Maven integration is not exception to the rule, and I’d like to draw your attention to some Maven integration improvements in IntelliJ IDEA version 7.0.3, that I personally consider worth mentioning.

  • Automatic synchronization with Maven structure on startup. Now, when importing Maven projects to IntelliJ IDEA, you can specify, whether you want IntelliJ IDEA to sync with the projects on startup or not (unlike it was done in IntelliJ IDEA 7.0.2 that used temporary modules for this purpose).

    AutoSync
  • Automatic detection of facets. While importing your Maven project to IntelliJ IDEA 7.0.3, the following facets are detected automatically: Java EE, EJB, GWT, and Web. All dependencies and deployment settings are recognized and stored. If you change some facet’s build setting, or add own deployment descriptors, IntelliJ IDEA will preserve them, so they won’t be lost when synchronizing with Maven projects.
  • Selecting build profiles. If you import a Maven project to IntelliJ IDEA 7.0.3, you can specify profiles to be taken into account, thus selecting module structure and dependencies.
  • Detecting errors. If you try to import Maven project from a pom.xml file, that is somehow corrupted, IntelliJ IDEA will warn you about erroneous descriptor file.

    Building Model Error


See the release notes for other improvements and fixes, and download the free 30-day trial version.

Technorati tags: , ,
This entry was posted in New Features and tagged . Bookmark the permalink.

2 Responses to IntelliJ IDEA 7.0.3: Maven Integration Improvements

  1. Geoffrey says:

    I like the whole automatic syncing thing, but my project has a directory /data/xml/ with huge xml files (several megs per file and at least 20 of those files). That directory needs to be excluded, because it takes to long for IntelliJ to sync that directory and it also makes a refactor rename hang (if search for text occurances).

    However , as far as I know, there’s no way to tell a pom.xml file that the ide should exclude directory’s. So every time it IntelliJ syncs with the pom.xml file, it looses those excludes and a refactor rename takes ages again.
    Those xml files don’t belong in /target because they need to be under source control (svn). They could very well be under /src/test/resources too (but not all test/resources should be excluded for refactor renames). How can I fix this?

  2. Anton Makeev says:

    Unfortunatelly, you can not specify additional excluded directories at the moment. You may create a jira issue for that feature (http://www.jetbrains.net/jira/).

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>