exclude commons-io and reflections class from ml-commons client jar #796
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.
Description
exclude commons-io and reflections class from ml-commons client jar
Now we are using GHA to publish ml-commons jar.
But the jar built by running
./gradlew publishShadowPublicationToSnapshotsRepository
contains other classes from commons-io and reflectionBefore this PR, we can see such classes in
client/build/libs/opensearch-ml-client-2.7.0.0-SNAPSHOT.jar
, that will cause Jarhell issue for SQL plugin as it depends on both commons-utils and ml-commons client .After this PR, these classes will be removed from ml-commons client jar.
Issues Resolved
#778
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.