imacatlolol Posted April 13, 2020 Posted April 13, 2020 This has been a thorn in my side for a while, and I've never been able to find a good solution. Whenever I update Forge, the newly mapped sources get applied just fine. However, the previous version still ends up lingering around in my environment, resulting in my searches getting cluttered and generally being a nuisance. The solution that I've been using up until now is to just delete my Gradle cache by hand. In some cases, I have to delete the entire cache for it to be resolved, which forces me to sit around waiting to Forge to patch and re-map the game's sources for my desired version. This gets out of hand pretty fast if I'm swapping versions a lot, and can be troublesome if I'm developing for multiple versions in the same project. Chances are that I'm doing something wrong here. Probably an IDEA configuration or Gradle task that I don't know about. Any ideas? Quote I'm eager to learn and am prone to mistakes. Don't hesitate to tell me how I can improve.
TheGreyGhost Posted April 13, 2020 Posted April 13, 2020 Hi I have exactly the same problem (in IntelliJ), I haven't spent the time to figure out exactly what the root cause is, but there is a workaround that you don't have to delete the cache for. If you go to Project Structure, Libraries, and select the mapped snapshot, you can manually unlink the older sources which are mapped to the class file. Eg see screenshot (after removing the extra/older source). It's not perfect because when you refresh the gradle task it puts the old ones back in again, but it's not a big hassle. -TGG 1 Quote
imacatlolol Posted April 14, 2020 Author Posted April 14, 2020 On 4/13/2020 at 11:38 PM, TheGreyGhost said: Hi I have exactly the same problem (in IntelliJ), I haven't spent the time to figure out exactly what the root cause is, but there is a workaround that you don't have to delete the cache for. If you go to Project Structure, Libraries, and select the mapped snapshot, you can manually unlink the older sources which are mapped to the class file. Eg see screenshot (after removing the extra/older source). It's not perfect because when you refresh the gradle task it puts the old ones back in again, but it's not a big hassle. -TGG Expand Ah! That's a great workaround, thank you! Quote I'm eager to learn and am prone to mistakes. Don't hesitate to tell me how I can improve.
imacatlolol Posted April 14, 2020 Author Posted April 14, 2020 On 4/14/2020 at 7:41 AM, diesieben07 said: This appears to be fixed with version 2020.1. Expand Ha! That's what I get for putting off the update, I guess. Quote I'm eager to learn and am prone to mistakes. Don't hesitate to tell me how I can improve.
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.