I'm using compileOnly to declare a dependency. I do not want it to be part of my launch configuration, but only have it available when compiling. I'm using modding for minecraft. Using Buildship 3.1.9.v20240115-1636. Apparently this is an issue of how eclipse is structured (at least other people said so), that there are no dependency a project can have which are only available when compiling and are ignore when running the project.
Is this a known issue? Is there any way to get around this?
My setup
I make use of NeoGradle a plugin for developing with Minecraft and NeoForge. I have a root project (link) and a subproject called CreativeCore, which declares the compileOnly dependency (here).
I'm using
compileOnlyto declare a dependency. I do not want it to be part of my launch configuration, but only have it available when compiling. I'm using modding for minecraft. Using Buildship 3.1.9.v20240115-1636. Apparently this is an issue of how eclipse is structured (at least other people said so), that there are no dependency a project can have which are only available when compiling and are ignore when running the project.Is this a known issue? Is there any way to get around this?
My setup
I make use of NeoGradle a plugin for developing with Minecraft and NeoForge. I have a root project (link) and a subproject called CreativeCore, which declares the compileOnly dependency (here).