Replaced the old JVM Argument -Xdebug (which does nothing according to documentation) with newer ones as described in #39388.
Comment From: wanger26
Should we update the test for parseDebugFlags as well as the running-your-application doc to reflect this change?
Comment From: lukasdo
I added another commit for the running-your-application documentation.
An updated parseDebugsFlags test could look like this:
@Test
void parseDebugFlag() {
String[] args = parseArgs("-agentlib:jdwp=server=y,transport=dt_socket,address=8000,suspend=n");
assertThat(args).hasSize(1);
assertThat(args[0]).isEqualTo("-agentlib:jdwp=server=y,transport=dt_socket,address=8000,suspend=n");
}
I am not really sure if that would make sense as it would be just testing if one argument is parsed correctly which is also tested in e.g. parseWithExtraSpaces. If desired I could update this test or delete it completely.
Comment From: wanger26
Excellent, thank you 💯 It might be worth updating the test to ensure that the parsing works as expected in cases changes are made in the parser in the future.
Comment From: mhalbritter
Thank you very much and congratulations on your first contribution :tada:!