Skipping packaging for war projects in boost-gradle #7
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
* bumping up spring 1.5 plugin version * using gradle 4.10 wrapper for spring 1.5 tests and updating project wrapper to 5.1.1 * documenting spring boot 1.5 gradle plugin issues with gradle 5.0 and up * adding include and exclude property for test task * setting up travis to run 2 separate gradle builds * moving gradle test commands into separate script
…-host-config Correct case of useDefaultHost
…-windows Fix security util cmd windows
Pull dependencies from compileClasspath
scottkurz
force-pushed
the
172-no-package-for-war-packaging
branch
from
259a6ad
to
c29826c
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.
No description provided.