-
Notifications
You must be signed in to change notification settings - Fork 320
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
Update to Guava 32.0.1+ #2101
Comments
Blocked by no new guice version |
Meanwhile Guava 32 is released. |
I just received a CVE alert (CVE-2023-2976) related to the use of |
@merks @HannesWell you looked into new guice and guava from maven-orbit pov |
@cherylking btw you use lsp4j. current lsp4j versions no longer have a guava dependency |
There is https://repo1.maven.org/maven2/com/google/guava/guava/32.0.1-jre/ and it’s available in https://download.eclipse.org/oomph/simrel-maven/2023-09/index.html along with any of its dependencies. |
I am asking for the p2 side of things. |
it has Import-Package: com.google.common.base;version="31.0",com.google.commo so i assume it works (did not test with tycho) but i also assume we then need to go the screw you backwards compatibility route cause of javax/jakarta.inject @szarnekow @LorenzoBettini any opinions? |
Ooh...good to know. Which version do I need to update to in order to not have the guava dependency? Is it |
yes 0.21.0 is fine for lsp4j |
more experiments with that on https://github.com/eclipse/xtext/compare/cd_testg32guice7 |
Yes it does as you already ask in their GH issues and they said that they don't plan to upgrade since one can use newer versions by corresponding build-tool configuration (google/guice#1642 (comment)). But luckily Guice only has a lower bound specified for the guava packages, so one can use any version from 31 onwards.
I assume that as well and AFAIK Guice uses Guava only internally so class-space consistency should not be an issue.
At least from a Eclipse-Platforms POV I try to support both javax.inject as well as jakarta.inject when adding support for that. But as said in #2668 personally I have no need for backwards compatibility as long as other SimRel projects like Xcore can follow. |
@merks where can i find the target file for https://download.eclipse.org/oomph/simrel-orbit/2023-09 |
I'm very busy migrating Oomph to GitHub. The new location is here: https://github.com/eclipse-oomph/oomph.incubator/blob/master/maven/tp/Maven.target |
Fixed in 2.32 |
No description provided.
The text was updated successfully, but these errors were encountered: