Specify content filters for each maven repo #574
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PLEASE READ THE GUIDELINES BEFORE MAKING A CONTRIBUTION
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, ...)
Bug fix.
What is the current behaviour? (You can also link to an open issue here)
A Gradle build with a clean cache can take a long time, as Gradle attempts to fetch every dependency from every Maven server. Yesterday I was having some connectivity issues to mvn.intelligence-modding.de, which caused just downloading Forge to take 10 minutes (let alone any of the mod dependencies)!
What is the new behaviour (if this is a feature change)?
This now adds content filters to all of the additional repos, meaning Gradle will now only try to download from:
We could prevent searching Maven Central and NeoForge by using
exclusiveContent
(example in Mekanism), but that's a bit of a bigger change