From e2400dcd8e21bfd872c866455024b2f4030f31dd Mon Sep 17 00:00:00 2001 From: Qaiser Abbasi Date: Fri, 21 Aug 2020 23:06:12 +0200 Subject: [PATCH] Remove legacy debugger instructions (#60583) In the past, the only way to run a local Elasticsearch build with a remote debugger was by extracting elasticsearch and passing ES_JAVA_OPTS. However, since switching to gradle, a convenience flag was added, `--debug-jvm` (which is documented elsewhere in the testings docs), when running a local elasticsearch build through gradle. This commit removes the old documentation. --- TESTING.asciidoc | 7 ------- 1 file changed, 7 deletions(-) diff --git a/TESTING.asciidoc b/TESTING.asciidoc index e2864291cd9..9267d29561e 100644 --- a/TESTING.asciidoc +++ b/TESTING.asciidoc @@ -657,13 +657,6 @@ as its build system. Since the switch to Gradle though, this is no longer possib the code currently used to build Elasticsearch does not allow JaCoCo to recognize its tests. For more information on this, see the discussion in https://github.com/elastic/elasticsearch/issues/28867[issue #28867]. -== Debugging remotely from an IDE - -If you want to run Elasticsearch and be able to remotely attach the process -for debugging purposes from your IDE, can start Elasticsearch using `ES_JAVA_OPTS`: - ---------------------------------------------------------------------------- -ES_JAVA_OPTS="-Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=4000,suspend=y" ./bin/elasticsearch --------------------------------------------------------------------------- Read your IDE documentation for how to attach a debugger to a JVM process.