-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
[1.20.x] Fix Reach Issues (and eclipse compilation issues) #346
Conversation
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.
You should use a proper compiler instead of making changes to the NeoForge source code due to its limitations.
Like it or not, we support eclipse, so we have to be compatible with the eclipse compiler. |
96d346d
to
669f13b
Compare
At some point, we ought to add some automated check to compile with the Eclipse compiler. Though that may be somewhat difficult, given how hardcoded Gradle seems to be with using a |
cbec310
to
367b271
Compare
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.
OK this looks good. Just one thing.
This PR addresses #243 and other reach changes that should have been fixed in porting. It also fixes issues with the eclipse compiler that were introduced by #73