OZ-196: Remove default exclusions from Maven parent so new Ozone distro is usable #68
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
|
@rbuisson @Ruhanga This one was a suggestion (I think from @mks-d), but also trying to be responsive to this Slack conversation. |
Ruhanga
approved these changes
Apr 23, 2024
rbuisson
approved these changes
Apr 23, 2024
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.
In order to make setting up a new distro easier, we remove the default exclusions from the maven-parent. Most concrete distributions will end up with their own custom exclusions anyways, so this is not just redundant, but makes the experience of setting up Ozone more difficult.