Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using compileOnly for dependency still makes it part of launch #1313

Open
CreativeMD opened this issue Aug 9, 2024 · 0 comments
Open

Using compileOnly for dependency still makes it part of launch #1313

CreativeMD opened this issue Aug 9, 2024 · 0 comments

Comments

@CreativeMD
Copy link

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant