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.

Sign up for GitHub

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

Jump to bottom

Upgrading Guava project #3

Open
pavelhoral opened this issue Nov 14, 2022 · 0 comments
Open

Upgrading Guava project #3

pavelhoral opened this issue Nov 14, 2022 · 0 comments

Comments

@pavelhoral
Copy link
Member

pavelhoral commented Nov 14, 2022 •
edited
Loading

We should consider the following:

  • upgrading to the current version of Guava (31 JRE version)
  • merging this repository with Wrensec Commons (or even dropping this repo and recreate its module from scratch)
  • have only a single artifact (i.e. do not split single Guava project into artificial JARs)

Not sure what is the motivation of using split package artifacts. It would make sense only in case the original project (Guava) was built like that, but that is not the case. Also by not splitting the original project this will become very trivial shaded package.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pavelhoral