anupamme commented on PR #57779:
URL: https://github.com/apache/spark/pull/57779#issuecomment-5229820650

   > Hi @anupamme — I only came across this PR after opening #57872. It takes 
the same approach and keeps the `hadoop-huaweicloud` exclusion from 
`hadoop-cloud-storage`.
   > 
   > I hit the same dependency check and found two more transitive entries that 
need to go: `esdk-obs-java` and `java-xmlbuilder` from the dependency manifest, 
plus `java-xmlbuilder` from `LICENSE-binary`. I pushed that follow-up in 
[zhangxinyao88@8fc414a](https://github.com/zhangxinyao88/spark/commit/8fc414a9206e7765a80bc0196bee470ee83d9f27),
 and the License and Dependencies tests are now green: 
https://github.com/zhangxinyao88/spark/actions/runs/31277824689/job/93154558709
   > 
   > The full CI run on #57872 has now completed successfully, and the PR is 
ready for review. Happy to avoid duplicating work, so please feel free to use 
that commit here—or we can proceed with #57872 if you prefer. Whatever works 
best for you and the maintainers.
   
   Thanks for catching this and for pushing the follow-up commit. I agree 
there’s no value in duplicating the work in #57872.
   
   I’ve incorporated `8fc414a` here, including the removal of esdk-obs-java and 
java-xmlbuilder from the dependency metadata and java-xmlbuilder from 
LICENSE-binary, and rerun the relevant License/Dependencies checks.
   
   I’d prefer to continue with this PR since it already contains the original 
context and discussion, but I’m also happy to defer to the maintainers if 
they’d rather proceed with #57872.
   
   Thanks again for finding the remaining dependency entries.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to