Jonathan Coates a17b001950 Move the core API into a separate module ... It should be possible to consume the ComputerCraft's core (i.e. non-Minecraft code) in other projects, such as emulators. While this has been possible for years, it's somewhat tricky from a maintenance perspective - it's very easy to accidentally add an MC dependency somewhere! By publishing a separate "core" jar, we can better distinguish the boundaries between our Lua runtime and the Minecraft-specific code. Ideally we could have one core project (rather than separate core and core-api modules), and publish a separate "api" jar, like we do for the main mod. However, this isn't really possible to express using Maven dependencies, and so we must resort to this system. Of course, this is kinda what the Java module system is meant to solve, but unfortunately getting that working with Minecraft is infeasible.		2022-11-04 21:41:59 +00:00
..
src/main/java/net/minecraft/resources	Move the core API into a separate module	2022-11-04 21:41:59 +00:00
build.gradle.kts	Move the core API into a separate module	2022-11-04 21:41:59 +00:00