-
Notifications
You must be signed in to change notification settings - Fork 67
Adapt LSP4E to LSP4J vers. 1.0.0 #1421
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -28,8 +28,8 @@ Require-Bundle: org.eclipse.core.runtime;bundle-version="3.12.0", | |
| org.eclipse.tm4e.ui;resolution:=optional, | ||
| org.eclipse.ui.editors, | ||
| org.eclipse.ui.navigator;bundle-version="3.6.100", | ||
| org.eclipse.lsp4j;bundle-version="[0.24.0,0.25.0)", | ||
| org.eclipse.lsp4j.jsonrpc;bundle-version="[0.24.0,0.25.0)", | ||
| org.eclipse.lsp4j;bundle-version="[1.0.0,2.0.0)", | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. same |
||
| org.eclipse.lsp4j.jsonrpc;bundle-version="[1.0.0,2.0.0)", | ||
| org.eclipse.ui.console, | ||
| org.eclipse.ltk.core.refactoring, | ||
| org.eclipse.core.expressions;bundle-version="3.5.0", | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should all these not use
1.1.0instead of2.0.0?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it is intentionally set to 1.0.0. There was no LSP4E release yet based on the latest LSP4J release vers. 1.0.0 and LSP4J vers. 1.1.0 is still under development. see #1421 (comment)
Should LSP4E not always depend on a released LSP4J version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did not mean to change
1.0.0, I meant change2.0.0to1.1.0, which would be the next minor version bump, equivalent to what we have been doing.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I should have read your comment more properly. Sorry for that.
But I'm still not sure if an upper range limit of
1.1.0instead of2.0.0is what we want. Starting with LSP4J 1.0.0, semantic versioning is used. Doesn't that mean that increasing the minor version of LSP4J would not introduce any breaking change and we can leave the upper range limit being 2.0.0?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see your point. Let's go for this. I have rerun one failing build and if it passes, I will merge it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@travkin79 , actually I cannot merge. Can you do the rebase?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its already merged, but here is a +1 review as requested.
I hope so! Assuming LSP4J doesn't screw up.
It may not mean any less updates needed to version ranges, but at least those updates will be semantic version compliant. i.e the next version LSP4J releases may well be 2.0.0, it is still TBD depending on what patches/improvements the project gets.