New Client Name #128
Closed
New Client Name #128
Conversation
This file contains hidden or 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
|
Oh, I think we should still merge this at some point - maybe after a release or 2. I'm looking to move the avaje-http-client git repo into avaje-http and keep it all together. |
|
Actually no, generation is busted if you try the new name: try the run.sh on this https://github.com/SentryMan/avaje-javalin-api-example. (Ah, It seems I forgot to clear my maven cache nvm) |
|
Replacing this PR with #133 .. so may as well close this now. |
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.
Updates generators to use the new HTTP Client Name.
Relies on avaje/avaje-http-client#57 and avaje/avaje-http-client#58