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

Allow full-offline startup after resolved libraries once #41

Open
Ghost-chu opened this issue Mar 3, 2024 · 5 comments
Open

Allow full-offline startup after resolved libraries once #41

Ghost-chu opened this issue Mar 3, 2024 · 5 comments
Labels
enhancement New feature or request

Comments

@Ghost-chu
Copy link

Ghost-chu commented Mar 3, 2024

In some cases, the server needs to be started without an (stable) internet connection. SpigotLibraryLoader is able to do this, but libby (gradle) requires an robust internet connection every time it is started in order to read the dependency files (even if cached files already exist).

@frengor
Copy link
Collaborator

frengor commented Mar 3, 2024

Are you using the transitive dependency resolution feature?

@Ghost-chu
Copy link
Author

Ghost-chu commented Mar 3, 2024 via email

@Ghost-chu
Copy link
Author

Are you using the transitive dependency resolution feature?

Yes, is this due to the need to check if its associated dependencies have all finished downloading?
Can this be cached?

As well as I noticed that libby always uses Maven Central when resolving its own dependencies, instead of the mirror specified by Dev, which defeats the purpose of mirroring and ends up causing huge delays for the user (the quality of our country/region's internet connection to Maven Central is pretty bad)...
I'm using my own Fork to circumvent this problem.

Translated with DeepL.com (free version)

@frengor
Copy link
Collaborator

frengor commented Mar 3, 2024

As well as I noticed that libby always uses Maven Central when resolving its own dependencies, instead of the mirror specified by Dev

If you add your mirror before Maven Central the mirror should be queried before it.

@Ghost-chu
Copy link
Author

As well as I noticed that libby always uses Maven Central when resolving its own dependencies, instead of the mirror specified by Dev

If you add your mirror before Maven Central the mirror should be queried before it.

It's load libraries into an standalone classloader and never use user defined mirrors.

@frengor frengor added the enhancement New feature or request label Apr 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants