Added support for s3-event-notifications in migration tool #6059
+435
−0
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.
Motivation and Context
This PR added support for s3-event-notifications in migration tool. s3-event-notifications is a separate module in v2, while in v1 it is in s3.event folder. All nested class in S3EventNotification class in v1 is a separated class in v2.
Modifications
Added transform for all package names.
Added transform for all different method names.
Added transform for different return types (getEventNameAsEnum() and getEventTime())
Testing
Added new integration test class for s3-event-notifications module
Screenshots (if appropriate)
Types of changes
Checklist
mvn install
succeedsscripts/new-change
script and following the instructions. Commit the new file created by the script in.changes/next-release
with your changes.License