HDDS-6304. Add enforcer to make sure ozone.version equals project.version #3075
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.
What changes were proposed in this pull request?
When updating Ozone's version with "mvn versions:set", the content of "ozone.version" is not updated.
This ticket is to add a maven-enforcer to make sure the ozone.version equals project.version. So that it can notice the inequality for the builder of the project.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-6304
How was this patch tested?
Test by changing the ozone.version in pom.xml. The following error would happen if the ozone.version doesn't equal to project.version.