Terasology is an open source project started by Benjamin "begla" Glatzel to research procedural terrain generation and efficient rendering techniques in Java using the LWJGL. The engine uses a block-based voxel-like approach as seen in Minecraft. After proving itself as a solid tech demo begla was joined at first by Anton "small-jeeper" Kireev and Rasmus "Cervator" Praestholm and a full-fledged game concept was born. Our goal is a game that pays ample tribute to Minecraft in initial look and origin, but stakes out its own niche by adopting the NPC-helper and caretaker feel from such games as Dwarf Fortress and Dungeon Keeper, while striving for added depth and sophistication in the foundation systems akin to DF.
With a module A set up locally that has a dependency on module B the following execution of Gradle will amusingly first fetch the binary version of B for the command that fetches the source version of B
gradlew fetchModuleB
Nothing actually breaks, but it seems goofy. Example may be off if alpha-sorting matters, actual example was having Portals locally but not LightAndShadowResources
On a slightly related note I've encountered a time or two when dependency resolution for newly fetched modules can cause failures, probably when there's more than one dependency (I believe Cities can encounter the problem). Running "gradlew" again gets past the issue and everything works.
Cervator
commented
10 years ago
With a module A set up locally that has a dependency on module B the following execution of Gradle will amusingly first fetch the binary version of B for the command that fetches the source version of B
gradlew fetchModuleB
Nothing actually breaks, but it seems goofy. Example may be off if alpha-sorting matters, actual example was having Portals locally but not LightAndShadowResources