Skip to content

Conversation

@gabizou
Copy link
Member

@gabizou gabizou commented Oct 9, 2020

Pretty basic premise, we've got issues with relying on guava, and as Configurate is migrating away from Guava altogether, so shall we (on the basis that we don't really use too much of guava, this is a good chance for cleanup as well).

@zml2008 has got more to do with migrating our usage of TypeTokens.

@Lignium
Copy link
Contributor

Lignium commented Oct 10, 2020

What about plugins? If each plugin will add Guava to JAR manually, there will be version conflicts.

@gabizou
Copy link
Member Author

gabizou commented Oct 10, 2020

What about plugins? If each plugin will add Guava to JAR manually, there will be version conflicts.

We're not removing guava as part of the API set of libraries, we're just removing our usage of them in the API. There's also an overall issue of "we're stuck with the versions of guava based on the MC implementation" but other implementations (like lantern) are irrespective of Minecraft's version dependencies.

@kashike kashike added the api: 8 (u) version: 1.16 (unsupported since Oct 17th 2023) label Oct 10, 2020
Signed-off-by: Gabriel Harris-Rouquette <gabizou@me.com>
Signed-off-by: Gabriel Harris-Rouquette <gabizou@me.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: 8 (u) version: 1.16 (unsupported since Oct 17th 2023)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants