Fix startup failures in polaris-service distributions #593
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #542.
The main issue was that the "main"
startScriptstask was configured for the shaded jar, but it shouldn't have: this task produces scripts suitable for the "main" distribution; the shadow jar plugin comes with its own task,startShadowScriptsthat produces scripts for the "shaded" distribution.I manually verified that both distributions contain the required jars, that both contain scripts called
polaris-service, and that the scripts work.This PR also switches the docker layout to "main" (exploded jars) instead of "shadow" (uber-jar). I manually verified that images built with this layout work.
Finally, this PR also fixes the fact that the shadow distribution was missing the LICENSE and NOTICE files.