fix the reversed version problem for maven-enforcer-plugin rule config #18040
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
fix the reversed version problem for maven-enforcer-plugin rule config when generating jhipster with a low version of java Fix #18038
|
|
mshima
requested changes
Mar 3, 2022
ko5tik
pushed a commit
to ko5tik/generator-jhipster
that referenced
this pull request
May 21, 2022
jhipster#18040) * fix the reversed version problem for maven-enforcer-plugin rule config fix the reversed version problem for maven-enforcer-plugin rule config when generating jhipster with a low version of java Co-authored-by: Marcelo Shima <marceloshima@gmail.com>
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.
fix the reversed version problem for maven-enforcer-plugin rule config
when generating jhipster with a low version of java
Fix #18038
Please make sure the below checklist is followed for Pull Requests.
When you are still working on the PR, consider converting it to Draft (below reviewers) and adding
skip-cilabel, you can still see CI build result at your branch.