-
-
Notifications
You must be signed in to change notification settings - Fork 213
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Package services, lang and mod into a single jar
- Loading branch information
Showing
6 changed files
with
175 additions
and
161 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
103 changes: 0 additions & 103 deletions
103
...applaunch/java/org/spongepowered/forge/applaunch/loading/moddiscovery/ForgeBootstrap.java
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
894ba0f
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.
Would it be better to re-do (perhaps not the best word but) the overall gradle config for the Sponge implementation to do jar in jar? Almost all deps (if not all) come from common and the accesswidener relocate would be in common's services jar. Its a small example but is what immediately came to my mind after reading this config.
This would also let us take a step back and look at our source sets. AppLaunch and Launch in common/vanilla are...weird and I wonder if we've over-engineered this somewhat. It may be I'm overthinking but I always want to slim down and make sure we're doing only what we need to and nothing more.
Thoughts?
894ba0f
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.
The accesswidener relocate is temporary. We are now using access transformers (converted from access wideners by arch loom) in SF production so we will no longer need to shade the accesswidener lib at all in SF jar. Only SV will.
Overall there are tons of cleanup I would like to do in SC and SV but for now I'm focusing on having a runnable SF jar.
The next step (in a separate PR) will be to update SC, SV and modlauncher-transformers to match SF's ModLauncher version. I think this will be the appropriate time to refactor the remaining Gradle stuff because I don't know yet what SV will look like when ModLauncher will be updated.