Skip to content

Commit c1319d0

Browse files
avneesh91martijnvg
authored andcommitted
[Issue-27716]: CONTRIBUTING.md IntelliJ configurations settings are confusing. (#27717)
* Improved paragraph describing how to run unit tests from Intellij. * Added information about how to run a local copy of elasticsearch from the source.
1 parent 648f8d2 commit c1319d0

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

CONTRIBUTING.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -115,11 +115,13 @@ Alternatively, `idea.no.launcher=true` can be set in the
115115
[`idea.properties`](https://www.jetbrains.com/help/idea/file-idea-properties.html)
116116
file which can be accessed under Help > Edit Custom Properties (this will require a
117117
restart of IDEA). For IDEA 2017.3 and above, in addition to the JVM option, you will need to go to
118-
`Run->Edit Configurations...` and change the value for the `Shorten command line` setting from
118+
`Run->Edit Configurations->...->Defaults->JUnit` and change the value for the `Shorten command line` setting from
119119
`user-local default: none` to `classpath file`. You may also need to [remove `ant-javafx.jar` from your
120120
classpath](https://github.com/elastic/elasticsearch/issues/14348) if that is
121121
reported as a source of jar hell.
122122

123+
To run an instance of elasticsearch from the source code run `gradle run`
124+
123125
The Elasticsearch codebase makes heavy use of Java `assert`s and the
124126
test runner requires that assertions be enabled within the JVM. This
125127
can be accomplished by passing the flag `-ea` to the JVM on startup.

0 commit comments

Comments
 (0)