-
Notifications
You must be signed in to change notification settings - Fork 31
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
Allow multiple copies of a class on the CP and pick the JAR containing the first. #169
base: main
Are you sure you want to change the base?
Conversation
Last commit published: 5e864b1e2d7c7463e105fb621621c18d1d17b296. PR PublishingThe artifacts published by this PR:
Repository DeclarationIn order to use the artifacts published by the PR, add the following repository to your buildscript: repositories {
maven {
name 'Maven for PR #169' // https://github.com/neoforged/FancyModLoader/pull/169
url 'https://prmaven.neoforged.net/FancyModLoader/pr169'
content {
includeModule('net.neoforged.fancymodloader', 'earlydisplay')
includeModule('net.neoforged.fancymodloader', 'junit-fml')
includeModule('net.neoforged.fancymodloader', 'loader')
}
}
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer the MC jar override to be manual via a system prop. Is that unreasonable? That would better match NG's logic.
As I already told you on Discord, no system properties: It's a pain in the ass to actually set those for JUnit runs |
2c81207
to
5e864b1
Compare
Yes and no. |
@Technici4n What is the state on this? |
In case this got lost: my preference is still to pass the desired MC jar and client-extra as a system prop or something like that. |
This allows unusual setups where through cross-project or cross-source-set dependencies, IDEs put MC on the classpath multiple times.