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.

Sign up for GitHub

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

Jump to bottom

Implement User Preferences for jdt.ls #6733

Closed
tsmaeder opened this issue Oct 13, 2017 · 3 comments
Closed

Implement User Preferences for jdt.ls #6733

tsmaeder opened this issue Oct 13, 2017 · 3 comments
Assignees
@tolusha
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. target/branch Indicates that a PR will be merged into a branch other than master.

Comments

@tsmaeder
Copy link
Contributor

tsmaeder commented Oct 13, 2017 •
edited
Loading

We need to analyse what configuration we need to do for jdt.ls. This analysis will result in outcomes:

  • Settings that exist, but will not be shown to the user
  • Settings that exist and need to be exposed in user preferences
  • Settings that don't exist yet. We need to implement those in jdt.ls.
    At this point, we should implement the minimum settings we need for Java support to function. More settings can be added later.
@tsmaeder tsmaeder mentioned this issue Oct 13, 2017
Closed
45 tasks
@gazarenkov
Copy link
Contributor

@tsmaeder labels?
https://github.com/eclipse/che/wiki/Labels

@tsmaeder tsmaeder added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Oct 20, 2017
@tolusha tolusha added team/enterprise status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach labels Dec 26, 2017
@tolusha tolusha self-assigned this Dec 26, 2017
@tolusha tolusha assigned tolusha and unassigned tolusha Dec 28, 2017
@tolusha tolusha added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. team/enterprise sprint/current and removed status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach labels Dec 28, 2017
@tolusha
Copy link
Contributor

tolusha commented Jan 9, 2018

@tsmaeder Could you clarify pls.
What exactly do we have to analyse?

@tolusha tolusha added status/in-progress This issue has been taken by an engineer and is under active development. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Jan 10, 2018
@tolusha
Copy link
Contributor

tolusha commented Jan 10, 2018

  • Xmx
  • debug mode

@tolusha tolusha added the target/branch Indicates that a PR will be merged into a branch other than master. label Jan 10, 2018
This was referenced Jan 16, 2018
Merged
Merged
@tolusha tolusha added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. sprint/current and removed sprint/current target/branch Indicates that a PR will be merged into a branch other than master. labels Jan 22, 2018
@tolusha tolusha closed this as completed Jan 24, 2018
@tolusha tolusha added target/branch Indicates that a PR will be merged into a branch other than master. and removed sprint/current status/in-progress This issue has been taken by an engineer and is under active development. status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. labels Jan 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tolusha tolusha

Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. target/branch Indicates that a PR will be merged into a branch other than master.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gazarenkov @tolusha @tsmaeder