Adjusting Intellij settings in ide-settings

[CREITZ25]

As an Intellij user, I want to use Intellij with defaults that make sense to us. To do this, the required settings should be stored in the ide-settings repository.

• Settings - Editor - Code Style - Java - Tab "Imports":
• Class count to use import with '*' : 999
• Names count to use static import with '*': 999
• Set line length to at least 160 characters (I cannot imagine that as of today any developer does not get this number of characters on his screen without the need to scroll - the restrictions limiting to 80 or later 120 characters per line come from an ancient time and the reformatting line wraps added by intellij contribute to our diff-war)
• Ensure we get a Warning if JavaDoc is missing or incomplete for public and protected elements (Types, Fields, Constructors, Methods including parameters).
• Activate "save actions" in Intellij (like in Eclipse to ensure the code-style is always applied and cannot be forgot on commit)
• Eclipse reformat plugin should not be used anymore - we want to configure IntelliJ natively (otherwise you get errors if you never installed and configured Eclipse and our team is not using eclipse) See here
  https://github.com/devonfw/ide-settings/blob/d1a7dd1f1ae817b3fb659f92a8fb54eb567b3b74/intellij/plugins/EclipseCodeFormatter.properties#L2
• Optional: FolderCompact plugin could be pre-installed too (I initially liked this plugin but it has some severe downsides - if it is installed, you do not see folders like src anymore and if you have src/main/assembly or anything not common you get unable to see this in IntelliJ. This renders the plugin useless even though it would otherwise be great. See my rating comment here)
• Maven Builder settings need to be pre-configured
• Encoding for resource bundle properties to UTF-8
• more?

[jan-vcapgemini]

For Adapter for Eclipse Code Formatter we need to use these settings:

[jan-vcapgemini]

For Save Actions I prefer to use these settings:

[jan-vcapgemini]

For the Maven Runner I'd suggest these settings:

[jan-vcapgemini]

For Maven Running Tests I'm using:

[jan-vcapgemini]

I've added a new branch to ide-settings now: https://github.com/devonfw/ide-settings/tree/dev-ide-settings

[hohwille]

Just had a long confusion with @moritzLanger because assertions are failing in his JUnit test.
I was assuming that assertions are enabled via our settings and therefore did not get that the assert statements in the code were totally wrong (inverted) but never executed when I run the CLI.
What we need to change is to enable assertions in our IDEs (ideally both Eclipse and Intellij and IMHO on all branches).
This is done with the JVM option -ea for "enable assertions".

[jan-vcapgemini]

I've realized that "Save Actions Tool" is deprecated. It won't work in the latest version of intellij anymore.
Looks like we have to remove it from our settings. :(
With some luck, we might get its features integrated into intellij later: https://youtrack.jetbrains.com/issue/IDEA-326980

[jan-vcapgemini]

It looks like some more steps are required so that our settings work properly.
F.e. eclipse needs to be pre-installed automatically, otherwise our Adapter for Eclipse Code Reformatter Plug-In won't work at all.

We also need to make sure that our IDEasy project gets cloned and imported into intellij properly.

Current workflow looks like the following:

• run devon eclipse
• manually clone IDEasy into workspaces/main
• run devon intellij
• open/import the workspaces/main folder
• browse to the IDEasy module
• rightclick on the pom.xml in the root and choose Add as Maven project

All of these steps should be run automatically.

[jan-vcapgemini]

Another issue I've found is the initial clone of the settings when providing the dev-ide-settings git repository URL.
It seems like the initial installation of devonfw-ide changed some files in the settings directory and fails to pull the latest version of our dev-ide-settings.