[AMORO-2853] Improve the packaging and compilation process for amoro project#2854
Merged
Conversation
Member
Author
|
cc @zhoujinsong |
Member
Author
|
Hi @zhoujinsong for the suggestion. Patch is updated accordingly, can you please take another look? Had tried following mvn commad in local environment.
Originally posted by @zhoujinsong in #2853 (comment) |
zhoujinsong
approved these changes
May 23, 2024
zhoujinsong
left a comment
Contributor
There was a problem hiding this comment.
LGTM.
Thanks a lot for the contribution!
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
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.
Why are the changes needed?
Close #2853.
Brief change log
It not friendly for users to use
mvn clean package -DskipTests -pl '!amoro-mixed-format/amoro-mixed-format-trino'to build the amoro project. Add a newskip-trino-buildprofile to improve the build command.How was this patch tested?
Add some test cases that check the changes thoroughly including negative and positive cases if possible
Add screenshots for manual tests if appropriate
Run test locally before making a pull request
Documentation