This message was deleted.
# community-support
s
This message was deleted.
k
It depends on the context - in the past I’ve bundled all the code and artifacts in one jar and selected which one to use at runtime. I believe this is the same approach netty uses.
It’s often used when making bindings to C libraries as well
a
I'd create one task for each platform. Each platform-specific task should have an
onlyIf {}
predicate that enables the task per platform. And finally a lifecycle task (or use a Base Plugin lifecycle task, like assemble) that depends on both.