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

Updated Guava and javax.servlet dependencies #417

Closed
wants to merge 1 commit into from

Conversation

keinhaar
Copy link
Contributor

@keinhaar keinhaar commented Dec 9, 2022

  • Removed the included 2 guava libraries and replaced them by an dependency to the bundle com.google.guava which is included in eclipse anyway.
  • replaced the javax.servlet dependency by jakarta.servlet-api, which is included since 2021-06.

- Removed the included 2 guava libraries and replaced them by an
dependency to the bundle com.google.guava which is included in eclipse
anyway.
- replaced the javax.servlet dependency by jakarta.servlet-api, which is
included since 2021-06.
@protoism
Copy link
Contributor

Hi @keinhaar,
this PR seems interesting, but I wonder how safe is using Eclipse's guava.
I wonder if we introduce a dependency between the version we need, and the version eclipse distributes.
Moreover, we're "exporting" guava. What does it mean?

About servlet APIs... the proposed fix is already in main, isn't it?

So... at the very least the PR must be re-done (best thing to do in my opinion is back merging main branch to your branch and make a manual merge)

Let me know!

@protoism
Copy link
Contributor

Hi Keinhaar.

There are just a handful binary libraries (except monster GWT dev)

  • guava JDK 5 is probably gone, see Remove apiclientlib #486
  • gson is not used
  • Servlet APIs change is already in main (and probably can go away as well :)
  • JSR 305 usage is too low to justify embedding the library

What's missing is Guava dependency.
As far as I now Guava people do care a lot about binary compatibility, so let's assume that all versions will do.
But nonetheless, can you point me to where Eclipse people declare that guava is part of all distributions, and safe to use?
At the very least, we must pay attention to how to declare guava dependency.
I don't even understand, for example (I beg pardon for my ignorance), where we would declare "we want guava from that Eclipse version"

@protoism
Copy link
Contributor

Closing this PR.
I think we can simply remove all dependencies except GWT / Guava.
About Guava, I'm a bit reluctant to use the Eclipse provided version to reduce the risk of breaking the plugin with newer Eclipse releases

@protoism protoism closed this Jul 26, 2024
@keinhaar keinhaar deleted the libupdates branch September 22, 2024 13:49
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.

2 participants