This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 . It is not the current version, and thus it cannot be edited.

Back to current version Restore this version

This is a blog like article with a FAQ for d3web developers transitioning from Eclipse to IntelliJ IDEA:

Import current code styles#

Download the attached code_styles.jar and import them with File -> Import settings.

Add copyright header#

Download the attached copyright.txt and add it the following way:

The provided copyright.txt is for the denkbares GmbH, but can easily be changed to other firms or e.g. the university.

Adding new files and classes to version control automatically:#

Go to File -> Settings -> Version control -> Confirmation -> When files are created. You're probably looking for "Add silently".

Save actions like in eclipse#

Edit -> Macros -> Start macro recording

Now we record the actual macro simulating our Save actions:

1. Code -> Reformat Code (formats the code according to the code style/template, also allows to optimize inputs)
2. File -> Save all
3. Build -> Compile (compiles the changes which also causes them to be hot swapped when in debug)

Edit -> Marcros -> Stop macro recording

After that, I bound the macro to "Cmd + Alt + S". This way I still have the normal save, but also the macro which does more...

Show Javadoc#

Use View -> Quick Documentation or the corresponding keyboard shortcut (depends on OS and Keymap).
On Mac OSX with Eclipse keymap, F2 Works.

It's also possible to enable automatic JavaDoc popup on code completion in Preferences -> Editor -> Code completion (Autopopup documentation).
At the beginning this worked for me (somewhat clitching), but now it no longer works :(

Running Headless-App-Tests in JUnit#

To run the Headless-App-Tests in JUnit (e.g. for debugging), create/add a new JUnit Configuration. In the configuration, it is important to select "class" at the dropdown for the "Form mode" (upper right). I also recommend to use "Single instance only".

If "Fork mode: class" is not selected, JUnit seems to use different JVMs to execute test and parameter method, which causes the ArticleManager in the test method to be empty.

Sorting of import statements#

By default IntelliJ has different order of import statements as Eclipse. To avoid having these change every time a class is edited in the different IDEs, we should adjust the order in IntelliJ. This can be done under Code Style -> Java - > Imports. The order should be:

1. import java.*
2. <blank line>
3. import javax.*
4. <blank line>
5. import all other imports
6. <blank line>
7. import cc.denkbar.*
8. import com.denkbares.*
9. import de.*
10. <blank line>
11. import static all other imports

The above order will not quite avoid all changes, since Eclipse seems to additionally add blank lines between all imports with different first path elements, but this seems close enough for now. I think since it is a code style, this should also be part of the code style settings, which are also attached to this site.