exclude spring dependencies from print plugin#3587
Merged
mbarto merged 1 commit intogeosolutions-it:masterfrom Feb 28, 2019
randomorder:spring-version
Merged
exclude spring dependencies from print plugin#3587mbarto merged 1 commit intogeosolutions-it:masterfrom randomorder:spring-version
mbarto merged 1 commit intogeosolutions-it:masterfrom
randomorder:spring-version
Conversation
mbarto
approved these changes
Feb 28, 2019
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Description
Print plugin update caused a Spring dependencies clash between GeoStore and Print plugin. This will exclude print plugin conflicting jars form the final WAR.
What is the current behavior? (You can also link to an open issue here)
Final MapStore WAR not working
What is the new behavior?
Final MapStore WAR is working
Does this PR introduce a breaking change? (check one with "x", remove the other)
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: