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

Possibility of dropping Forgerock/Guava in favor of Google/Guava #24

Open
krystofNovotny opened this issue Jan 29, 2021 · 1 comment
Open

Comments

@krystofNovotny
Copy link

The current version of Forgerock/Guava is old and no longer developed.

This issue is about exploring the possibility of replacing Forgerock/Guava with the latest version of Google/Guava and specifying problems it would create.

I'm looking for answers to those questions:

  • Is it feasible?
  • What changes would have to be done?
@pavelhoral
Copy link
Member

I think we know answer to those questions thanks to our latest tinkering with Wren:IDM dependencies... It is better to have shaded Guava because a lot of other libraries depend on a different version which makes it jar hell situation. Feels safer to have our own version locked in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants