Regarding the last commit, its fixed... I forgot to update the cache
@@ -175,17 +175,6 @@ public class Input {
return super.map(internalName);
}
}));
- // TODO: Why does this not catch certain classes that hold
- // references to the renamed class? I don't see any reason why it
- // would fail. The remapper above will add the iterated node to the
- // referenced set if it references the renamed class's original
- // name.
- //
- // Yet in one of my test cases, the node is updated but still
- // retains references to the original class.
- //
- // If this check is removed ALL nodes are regenerated. That is
- // WILDLY inefficient but resolves the issue.
if (referenced.contains(cn.name)) {
updatedMap.put(cn.name, updated);
}
@@ -201,6 +190,7 @@ public class Input {
// Update the class that contains references to the renamed
// class
proxyClasses.put(updated.name, updated);
+ proxyClasses.removeCache(updated.name);
}
}
// Check if node was updated
