Since our platform-specific code is so small, it may be worth it to provide a "merged jar".
I think this only makes sense when all builds remap to the same mappings. If one platform uses notch at runtime and the other uses searge, there's no point merging the jars.
However, if both platforms use notch*, we may as well bundle both sets of metadata & platform-specific classes in one jar to simplify installation for end-users.
* I believe this is the case for modern versions.
One way to do this is with plugins like Forgix. We could probably also do it manually using shadow or a custom gradle task that combines each jar's ZipTree.
On the other hand, we could keep things simple and mark this issue as "not planned" :smiley:
Since our platform-specific code is so small, it may be worth it to provide a "merged jar".
I think this only makes sense when all builds remap to the same mappings. If one platform uses
notch
at runtime and the other usessearge
, there's no point merging the jars.However, if both platforms use
notch
*, we may as well bundle both sets of metadata & platform-specific classes in one jar to simplify installation for end-users.* I believe this is the case for modern versions.
One way to do this is with plugins like Forgix. We could probably also do it manually using shadow or a custom gradle task that combines each jar's
ZipTree
.On the other hand, we could keep things simple and mark this issue as "not planned" :smiley: