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

Move stream initialization to application #2504

Merged
merged 1 commit into from
Mar 2, 2023

Conversation

mickaelistria
Copy link
Contributor

So the plugin can be installed in other environments without messing streams

@rgrunber
Copy link
Contributor

rgrunber commented Mar 1, 2023

re-test this please.

Copy link
Contributor

@rgrunber rgrunber left a comment

Choose a reason for hiding this comment

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

The streams only need to be redirected (so we can use them for client/server communication) prior to starting the application, and that's exactly where they're being moved.

If some plugin were to grab a reference to stdout and write on it, that might be an issue, but that's still the case without this patch, given how many plugins would need to be activated before jdt.ls.core. If this were really an issue, then we can always starting using our own stream/socket for communication.

I think we can merge after #2503 .

Stream initialization is needed prior to starting the application, so it
can be moved out of plugin startup
@rgrunber rgrunber merged commit e275556 into eclipse-jdtls:master Mar 2, 2023
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