Fix for 2114 - Missing AWS events classes in jandex when building Lambda #2122
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
|
@marcinczeczko could you rebase your PR on master and squash it? It contains a lot of commits. Thanks! |
marcinczeczko
force-pushed
the
fix-for-2114
branch
from
1ee8203
to
3444dda
Compare
…events, missing reflection for lamdba return type
marcinczeczko
force-pushed
the
fix-for-2114
branch
from
3444dda
to
705c943
Compare
|
@gsmet - now it's one commit. |
|
When lambda is used with LAMBDA_PROXY mode, the |
…xyRequestContext but bean doesn't have it
marcinczeczko
force-pushed
the
fix-for-2114
branch
from
6f83295
to
1438748
Compare
gsmet
approved these changes
Apr 20, 2019
|
Merged, thanks! |
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.
This is a fix for #2114