Remove the default Maven phase bound to the metadata-copy
Maven goal to simplify the use of integration tests
#748
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.
metadata-copy
Maven goal to simplify the use of integration tests.test
tointegration-test
apache/shardingsphere#36050 and Native Build Tools cannot recognize Maven modules that only havepom.xml
but no source code #727 .metadata-copy
is not explicitly used on the command line, themetadata-copy
goal will be executed in theprepare-package
phase, which affects the processing of theintegration-test
phase, resulting in the following cumbersome logic to change themetadata-copy
goal. Sincemetadata-copy
is always used manually through the command line like./mvnw -Pnative test native:metadata-copy
,metadata-copy
should not be tied to a specific maven phase at all.