PaperMC/paperweight

Support for separate API and server upstream data

mastercoms opened this issue · 0 comments

Currently, upstream data is prepared for both API and server, which causes an upstream to prepare unnecessary outputs in its prepare for downstream task, if the downstream only uses the API (like Glowstone's Glowkit).

Downstream should be able to specify that it does not need certain outputs from upstream.