-
Notifications
You must be signed in to change notification settings - Fork 20
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
Run Setup task issues when using different sourceset #136
Comments
That is correct and sadly working as intended. There are some ideas in the community on how to resolve this (it would involve walking the entire dependency tree of any given configuration, which could be costly), but for right now we have decided not to implement this. You can consider it working as intended for now. |
I think an upcoming version will fix this. |
Added a test to validate that this is actually working now, will be working with newest version. |
Sorry, I couldn't come up with a short better title.
Say you have your mod source in the
main
SourceSet, but you want to run something else in another SourceSet,in this case you can create a run configuration and make it's
xxxImplementation
configuration extendimplementation
See below for an extremely minimalistic example (It crashes after start because there are no compiled classes, but that's not the point)
This will launch (and then crash as mentioned above) without issues.
However, if we move the
configurations
block below the dependencies block it will not launch .Not because the dependencies aren't there, but because the following tasks aren't executed before run (The last one is the main issue)
neoFormJoined_xxx_DownloadAssets
neoFormJoined_xxx_ExtractNatives
writeMinecraftClasspathClient
From a quick look it looks like this is because neoforge detectes when
neoforge
is added as a dep and then does fancy stuff around it. This is of course not triggered if a configuration want to inherit another one after this happened.Side point:
Currently you need to use
to make
modRun
work as a valid launch target, but theoretically you'd want the following to be enough:The text was updated successfully, but these errors were encountered: