New in 10.5: Spring 3.1 bean definition profiles

Posted on by serega.vasiliev

With the upcoming IntelliJ IDEA 10.5 you can try one of the most requested Spring 3.1 feature — environment profiles for application contexts.

1. Active profile names are shown in the top of text editor. Inactive profiles are grayed. Configuration errors and warnings (incorrect classes, properties, etc.) are shown for “active” and “inactive” profiles. “Resolve” problems are highlighted for active profiles only.

2. Active profile can be easily changed by clicking the “Change Profiles” link.

3. Usages search and rename refactoring work in xml configs, @Profile and java code.

Try these new features in the latest IntelliJ IDEA EAP build and let us know how they work for you.

As a side note, we encourage you to help us even more by allowing the IntelliJ IDEA usage statistics to be sent to us. If you had disabled it initially you can change your mind in IDE Settings | Usage Statistics. Thanks for your support!

Comments below can no longer be edited.

5 Responses to New in 10.5: Spring 3.1 bean definition profiles

  1. Igor Kolomiets says:

    April 14, 2011

    Great to see support for the latest Spring features! Will there be more Roo support in 10.5?

    Side note: I noticed annoying IDEA’s spellchecker warning in the example’s Spring *-config.xml – are you planning to make spellchecker more intelligent and ignoring innocent things like “Jdbc” from being highlighted everywhere? For this reason I have to keep it disabled 🙁

  2. anima says:

    April 15, 2011

    A post about Roo console is coming, stay tuned.
    As for spellchecker, you can add any word to your dictionary via a quickfix.

  3. Benoit says:

    July 14, 2011

    Hi,

    I unfortunately click on close instead of ‘change profiles’. Now, I can’t get anymore the dialog box to change the active profile. How can I get again that dialog box ?

    Thks

  4. Dmitry Avdeev says:

    July 18, 2011

    IDE Settings / Editor / Appearance / Show Spring profiles panel

  5. Petter Måhlén says:

    November 9, 2011

    This setting doesn’t seem to take effect when launching, for instance, unit tests – is that intentional?

Subscribe

Subscribe for updates