tests: use latest release for pom_configured test #944
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
algomaster99
changed the title
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.
I removed the version tag from this test to avoid changing it every time I release
sorald. One downside to this change is that we won't be testing this specific test with the latest SNAPSHOT, instead, we would be testing it with the latest release on maven central. I think it is a fine compromise to make because it is very unlikely that other integration tests will pass, but this specific test will fail.Initially, maven had an option
<version>LATEST</version>to fetch the latest SNAPSHOT at build time and use it. However, it has been deprecated in maven3.xin favour of reproducibility.