hibiscus-client/fabric-loom
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Improve some bad stack traces.

Browse source 
Idk why this happens.
This commit is contained in:
modmuss50 2021-07-13 00:05:24 +01:00
parent f13dc4eea7
commit ad5ac78e06
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
src/main/java/net/fabricmc/loom/task/LoomTasks.java
View file

@ -114,6 +114,13 @@ public final class LoomTasks {
project.afterEvaluate(p -> { project.afterEvaluate(p -> {
MappingsProviderImpl mappingsProvider = extension.getMappingsProvider(); MappingsProviderImpl mappingsProvider = extension.getMappingsProvider();
if (mappingsProvider.mappedProvider == null) {
// If this is ever null something has gone badly wrong,
// for some reason for another this afterEvaluate still gets called when something has gone badly
// wrong, returning here seems to produce nicer errors.
return;
}
File inputJar = mappingsProvider.mappedProvider.getMappedJar(); File inputJar = mappingsProvider.mappedProvider.getMappedJar();
if (mappingsProvider.hasUnpickDefinitions()) { if (mappingsProvider.hasUnpickDefinitions()) {