Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't call System.exit on exit, might cause workspace corruption #199

Merged
merged 1 commit into from
Mar 28, 2017

Conversation

fbricon
Copy link
Contributor

@fbricon fbricon commented Mar 27, 2017

Signed-off-by: Fred Bricon fbricon@gmail.com

@fbricon fbricon requested review from gorkem and tsmaeder March 27, 2017 17:48
@fbricon fbricon added this to the Late March 2017 milestone Mar 27, 2017
@gorkem
Copy link
Contributor

gorkem commented Mar 28, 2017

rerun tests

System.exit(0);
Executors.newSingleThreadScheduledExecutor().schedule(() -> {
logInfo("Forcing exit after 1 min.");
System.exit(0);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wonder if we should return a value other than 0 in this case. It is not actually a clear exit.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agreed. exit code 1?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, Let's define it as a constant though.

Signed-off-by: Fred Bricon <fbricon@gmail.com>
@fbricon fbricon merged commit f58ad76 into eclipse-jdtls:master Mar 28, 2017
@fbricon fbricon deleted the bad-system-exit branch March 28, 2017 03:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants