HDDS-4647. Avoid hadoop-ozone-filesystem-shaded as transitive dependency #1761
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.
What changes were proposed in this pull request?
If
hadoop-ozone-filesystem-hadoop2
orhadoop-ozone-filesystem-hadoop3
is added as dependency in some project,hadoop-ozone-filesystem-shaded
is included as a transitive dependency. But it should not be required for such downstream projects, as both Hadoop version-specific modules already repackage most of it. This change marks the dependency as optional (doc) so that such projects do not need to addexclusion
for this module.https://issues.apache.org/jira/browse/HDDS-4647
How was this patch tested?
Checked dependency tree of downstream project no longer includes
hadoop-ozone-filesystem-shaded
:Regular CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/465890389