[NG7] Minecraft setup multiple times when including multiple NG projects

neoforged / NeoGradle

Gradle plugin for NeoForge development

GNU Lesser General Public License v2.1

43 stars 25 forks source link

[NG7] Minecraft setup multiple times when including multiple NG projects #186

Closed ApexModder closed 3 months ago

ApexModder commented 3 months ago

Gradle setups Minecraft for each included NG project, making imports slow and workspaces tedious to use as there are duplicate Minecraft source entries.

Would be nice if we could mark a single project to be used for all Minecraft source related tasks, and have all NG projects use the Minecraft sources from that project.

original discussion in NeoCord

thedarkcolour commented 3 months ago

I can also vouch for this. The workspace I use for Kotlin for Forge takes 10+ minutes to import on my laptop, and anytime I accidentally mess up the cache I have to wait another 10 minutes for Neo to do the same work three times. I know factors like AccessTransformers, Parchment mappings, and NeoGradle version could mess things up but when they're all the same I think it would make sense to reuse the dependencies across projects like ForgeGradle used to.

Not to mention the multiple Minecraft sources are a big resource hog.

tmvkrpxl0 commented 3 months ago

I heard Orion was working on better caching system, maybe it's relevant?

thedarkcolour commented 2 months ago

This is still not working properly...

thedarkcolour commented 2 months ago

https://github.com/thedarkcolour/KotlinForForge/tree/4.x