Remove workaround to force guava version once ELK 0.8.0 is released #265
Assignees
Labels
Comments
tortmayr
added a commit
to eclipse-glsp/glsp-server
that referenced
this issue
Jan 19, 2023
- Update target platform
- Eclipse 21.03-> 22.12
- Jetty 9.x -> Jetty 10.0.12
- LSP4J -> 0.8.0 -> 0.19.0
- ELK 0.7.0 -> 0.8.1
- Add slf4j to enable logging in Jetty 10
- Keep "old" 2021-03 targetplatform and use it as minimal baseline target.
- Consume log4j,slf4j and javax.servlet via maven
- Jetty websockt requires slf4j 2.0 which ist not available via orbit and not compatible with the orbit log4j version.
So we instead use the new target platform features and consume it directly from a maven location
- Update server.websocket plugin to conform to Jetty API breaks
- Update to ELK 0.8.1 and remove workaround (Fixes eclipse-glsp/glsp#265)
- Clean up pom files and consistently use properties for all versions
- Remove xtext nature from parent project. Otherwise we get false positives in the Eclipse Problem view.
- Ensure that both the p2 and m2 build use the same version ranges for their dependencies (if possible)
Part of eclipse-glsp/glsp#764
tortmayr
added a commit
to eclipse-glsp/glsp-server
that referenced
this issue
Jan 20, 2023
- Update default target platform
- Eclipse 21.03-> 22.12
- Jetty 9.x -> Jetty 11.0.12
- LSP4J -> 0.8.0 -> 0.19.0
- ELK 0.7.0 -> 0.8.1
- Add slf4j to enable logging in Jetty 10
- Consume log4j,slf4j and javax.servlet via maven
- Jetty websockt requires slf4j 2.0 which is not available via orbit and not compatible with the orbit log4j version.
So we instead use the new target platform features and consume it directly from a maven location
- Update server.websocket plugin to conform to Jetty API breaks
- Update to ELK 0.8.1 and remove workaround (Fixes eclipse-glsp/glsp#265)
- Clean up pom files and consistently use properties for all versions
- Remove xtext nature from parent project. Otherwise we get false positives in the Eclipse Problem view.
- Ensure that both the p2 and m2 build use the same version ranges for their dependencies (if possible)
- Provide a second target for 2021-09 to use it as minimal baseline.
Part of eclipse-glsp/glsp#764
tortmayr
added a commit
to eclipse-glsp/glsp-server
that referenced
this issue
Jan 20, 2023
- Update default target platform
- Eclipse 21.03-> 22.12
- Jetty 9.x -> Jetty 11.0.12
- LSP4J -> 0.8.0 -> 0.19.0
- ELK 0.7.0 -> 0.8.1
- Add slf4j to enable logging in Jetty 10
- Consume log4j,slf4j and javax.servlet via maven
- Jetty websockt requires slf4j 2.0 which is not available via orbit and not compatible with the orbit log4j version.
So we instead use the new target platform features and consume it directly from a maven location
- Update server.websocket plugin to conform to Jetty API breaks
- Update to ELK 0.8.1 and remove workaround (Fixes eclipse-glsp/glsp#265)
- Clean up pom files and consistently use properties for all versions
- Remove xtext nature from parent project. Otherwise we get false positives in the Eclipse Problem view.
- Ensure that both the p2 and m2 build use the same version ranges for their dependencies (if possible)
- Provide a second target for 2021-09 to use it as minimal baseline.
Part of eclipse-glsp/glsp#764
tortmayr
added a commit
to eclipse-glsp/glsp-server
that referenced
this issue
Jan 20, 2023
- Update default target platform
- Eclipse 21.03-> 22.12
- Jetty 9.x -> Jetty 11.0.12
- LSP4J -> 0.8.0 -> 0.19.0
- ELK 0.7.0 -> 0.8.1
- Add slf4j to enable logging in Jetty 10
- Consume log4j,slf4j and javax.servlet via maven
- Jetty websockt requires slf4j 2.0 which is not available via orbit and not compatible with the orbit log4j version.
So we instead use the new target platform features and consume it directly from a maven location
- Update server.websocket plugin to conform to Jetty API breaks
- Update to ELK 0.8.1 and remove workaround (Fixes eclipse-glsp/glsp#265)
- Clean up pom files and consistently use properties for all versions
- Remove xtext nature from parent project. Otherwise we get false positives in the Eclipse Problem view.
- Ensure that both the p2 and m2 build use the same version ranges for their dependencies (if possible)
- Provide a second target for 2021-09 to use it as minimal baseline.
Part of eclipse-glsp/glsp#764
tortmayr
added a commit
to eclipse-glsp/glsp-server
that referenced
this issue
Jan 20, 2023
- Update default target platform
- Eclipse 21.03-> 22.12
- Jetty 9.x -> Jetty 11.0.12
- LSP4J -> 0.8.0 -> 0.19.0
- ELK 0.7.0 -> 0.8.1
- Add slf4j to enable logging in Jetty 10
- Consume log4j,slf4j and javax.servlet via maven
- Jetty websockt requires slf4j 2.0 which is not available via orbit and not compatible with the orbit log4j version.
So we instead use the new target platform features and consume it directly from a maven location
- Update server.websocket plugin to conform to Jetty API breaks
- Update to ELK 0.8.1 and remove workaround (Fixes eclipse-glsp/glsp#265)
- Clean up pom files and consistently use properties for all versions
- Remove xtext nature from parent project. Otherwise we get false positives in the Eclipse Problem view.
- Ensure that both the p2 and m2 build use the same version ranges for their dependencies (if possible)
- Provide a second target for 2021-09 to use it as minimal baseline.
Part of eclipse-glsp/glsp#764
Contributed on behalf of STMicroelectronics
tortmayr
added a commit
to eclipse-glsp/glsp-server
that referenced
this issue
Jan 20, 2023
- Update default target platform
- Eclipse 21.03-> 22.12
- Jetty 9.x -> Jetty 11.0.12
- LSP4J -> 0.8.0 -> 0.19.0
- ELK 0.7.0 -> 0.8.1
- Add slf4j to enable logging in Jetty 10
- Consume log4j,slf4j and javax.servlet via maven
- Jetty websockt requires slf4j 2.0 which is not available via orbit and not compatible with the orbit log4j version.
So we instead use the new target platform features and consume it directly from a maven location
- Update server.websocket plugin to conform to Jetty API breaks
- Update to ELK 0.8.1 and remove workaround (Fixes eclipse-glsp/glsp#265)
- Clean up pom files and consistently use properties for all versions
- Remove xtext nature from parent project. Otherwise we get false positives in the Eclipse Problem view.
- Ensure that both the p2 and m2 build use the same version ranges for their dependencies (if possible)
- Provide a second target for 2021-09 to use it as minimal baseline.
Part of eclipse-glsp/glsp#764
Contributed on behalf of STMicroelectronics
tortmayr
added a commit
to eclipse-glsp/glsp-server
that referenced
this issue
Jan 20, 2023
- Update default target platform
- Eclipse 21.03-> 22.12
- Jetty 9.x -> Jetty 11.0.12
- LSP4J -> 0.8.0 -> 0.19.0
- ELK 0.7.0 -> 0.8.1
- Add slf4j to enable logging in Jetty 10
- Consume log4j,slf4j and javax.servlet via maven
- Jetty websockt requires slf4j 2.0 which is not available via orbit and not compatible with the orbit log4j version.
So we instead use the new target platform features and consume it directly from a maven location
- Update server.websocket plugin to conform to Jetty API breaks
- Update to ELK 0.8.1 and remove workaround (Fixes eclipse-glsp/glsp#265)
- Clean up pom files and consistently use properties for all versions
- Remove xtext nature from parent project. Otherwise we get false positives in the Eclipse Problem view.
- Ensure that both the p2 and m2 build use the same version ranges for their dependencies (if possible)
- Provide a second target for 2021-09 to use it as minimal baseline.
Part of eclipse-glsp/glsp#764
Contributed on behalf of STMicroelectronics
tortmayr
added a commit
to eclipse-glsp/glsp-server
that referenced
this issue
Jan 20, 2023
- Update default target platform
- Eclipse 21.03-> 22.12
- Jetty 9.x -> Jetty 11.0.12
- LSP4J -> 0.8.0 -> 0.19.0
- ELK 0.7.0 -> 0.8.1
- Add slf4j to enable logging in Jetty 10
- Consume log4j,slf4j and javax.servlet via maven
- Jetty websockt requires slf4j 2.0 which is not available via orbit and not compatible with the orbit log4j version.
So we instead use the new target platform features and consume it directly from a maven location
- Update server.websocket plugin to conform to Jetty API breaks
- Update to ELK 0.8.1 and remove workaround (Fixes eclipse-glsp/glsp#265)
- Clean up pom files and consistently use properties for all versions
- Remove xtext nature from parent project. Otherwise we get false positives in the Eclipse Problem view.
- Ensure that both the p2 and m2 build use the same version ranges for their dependencies (if possible)
- Provide a second target for 2021-09 to use it as minimal baseline.
Part of eclipse-glsp/glsp#764
Contributed on behalf of STMicroelectronics
tortmayr
added a commit
to eclipse-glsp/glsp-server
that referenced
this issue
Jan 22, 2023
- Update default target platform
- Eclipse 21.03-> 22.12
- Jetty 9.x -> Jetty 11.0.12
- LSP4J -> 0.8.0 -> 0.19.0
- ELK 0.7.0 -> 0.8.1
- Add slf4j to enable logging in Jetty 10
- Consume log4j,slf4j and javax.servlet via maven
- Jetty websockt requires slf4j 2.0 which is not available via orbit and not compatible with the orbit log4j version.
So we instead use the new target platform features and consume it directly from a maven location
- Update server.websocket plugin to conform to Jetty API breaks
- Update to ELK 0.8.1 and remove workaround (Fixes eclipse-glsp/glsp#265)
- Clean up pom files and consistently use properties for all versions
- Remove xtext nature from parent project. Otherwise we get false positives in the Eclipse Problem view.
- Ensure that both the p2 and m2 build use the same version ranges for their dependencies (if possible)
- Provide a second target for 2021-09 to use it as minimal baseline.
Part of eclipse-glsp/glsp#764
Contributed on behalf of STMicroelectronics
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the ELK maven artifacts limit the Guava version to 19.xx. This blocks the upgrade of the Guice version (#260) because newer Guice versions use API that is not available in Guava 19.xx.
As a workaround guava has been excluded from all elk maven dependencies so that a newer version (27.1) will be used instead.
Once ELK 0.8.0 will be released we can remove this workaround.
The text was updated successfully, but these errors were encountered: