Refact sempv2 codegen on build #10
Merged
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
adjusted maven pom and openapi ignore file to configure build process and limit file generation
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.
What is the purpose of this change?
Generate SEMPv2 client code during build instead of checking in generated code
How was this change implemented?
Removed all generated files
Modified pom.xml to use openapi generator in generate-sources phase of build
Limited generation if files to minimum set required (e.g. omit grade files)
How was this change tested?
Rebuild maven module
Rebuild and rerun module (solace-config-plugin) that uses the client library.
Ensure Unit tests still run successfully
Is there anything the reviewers should focus on/be aware of?