File tree Expand file tree Collapse file tree 1 file changed +7
-10
lines changed Expand file tree Collapse file tree 1 file changed +7
-10
lines changed Original file line number Diff line number Diff line change @@ -168,16 +168,13 @@ You can import the Elasticsearch project into IntelliJ IDEA via:
168168
169169#### Checkstyle
170170
171- If you have the [ Checkstyle] plugin installed, you can configure IntelliJ to
172- check the Elasticsearch code. However, the Checkstyle configuration file does
173- not work by default with the IntelliJ plugin, so instead an IDE-specific config
174- file is generated automatically after IntelliJ finishes syncing. You can
175- manually generate the file with ` ./gradlew configureIdeCheckstyle ` in case
176- it is removed due to a ` ./gradlew clean ` or other action.
177-
178- IntelliJ should be automatically configured to use the generated rules after
179- import via the ` .idea/checkstyle-idea.xml ` configuration file. No further
180- action is required.
171+ IntelliJ should automatically configure checkstyle. It does so by running
172+ ` configureIdeCheckstyle ` on import. That makes ` .idea/checkstyle-idea.xml `
173+ configuration file. IntelliJ points checkstyle at that.
174+
175+ Things like ` ./gradlew clean ` or ` git clean -xdf ` can nuke the file. You can
176+ regenerate it by running ` ./gradlew -Didea.active=true configureIdeCheckstyle ` ,
177+ but generally shouldn't have to.
181178
182179#### Formatting
183180
You can’t perform that action at this time.
0 commit comments