Remove the explicit build dependency #64
Merged
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
Having `build` as a required step puts all the jars in the lib folder and makes this artifact 40mb+. This isn't required as these should be managed at the parent when packaging.
|
|
|
@tednaleid Any bandwidth to get this merged and released? |
|
This is causing application.yml to be bundled which wouldn't normally happen. Causes default pool to be setup and logs warn for missing property. |
|
Sorry, missed the email for this PR when you submitted it. |
tednaleid
added a commit
that referenced
this pull request
Feb 3, 2016
Remove the explicit build dependency
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.
Having
buildas a required step puts all the jars in the lib folder and makes this artifact 40mb+. This isn't required as these should be managed at the parent when packaging.