fix: Vert.x generator and enricher applicable when io.vertx
dependencies present
#329
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
fix: Vert.x generator and enricher to be applicable when
io.vertx
dependencies presentPreviously projects containing a
<dependency><groupId>io.vertx</groupId><!-- .... --></dependency>
were not being picked up by Vert.x generator and enricher since the behavior ofJKubeProjectUtil.hasDependency(getProject(), Constants.VERTX_GROUPID, null)
was not the one expected before Maven decoupling happened.Type of change
test, version modification, documentation, etc.)
Checklist
I have updated the documentation accordingly