Change packaging and Docker deployment strategy #8
Conversation
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
Switch from sbt-assembly + sbt-docker to using sbt-native-packager The former approach builds a fat jar that results in class file deduplication issues described in: sbt/sbt-assembly#391 sbt-native-packager does not rely in building a fat jar
marko-asplund
force-pushed
the
packaging
branch
from
f73ca5c to
6dbf8bb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Switch from
sbt-assembly+sbt-dockerto usingsbt-native-packager.The former approach builds a fat jar that results in class file deduplication issues described in:
sbt/sbt-assembly#391
sbt-native-packageris arguably a better approach among other things since it does not rely in building a fat jar.