Correcting some wrong references to dependency versions using fixed vers...#1
Open
gconcon wants to merge 1 commit intompoehler:masterfrom
Open
Correcting some wrong references to dependency versions using fixed vers...#1gconcon wants to merge 1 commit intompoehler:masterfrom
gconcon wants to merge 1 commit intompoehler:masterfrom
Conversation
…ersion number. And there was a wrong tag on xml version tag.
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
2 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.
...ion number. And there was a wrong tag on xml version tag.
When using a version parameter diferent from 1.0, the build fails because admin/pom.xml and frontend/pom.xml reference to core was using fixed 1.0 instead the ${version} snippet.