[ 
https://issues.apache.org/jira/browse/HADOOP-19086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932716#comment-17932716
 ] 

ASF GitHub Bot commented on HADOOP-19086:
-----------------------------------------

steveloughran opened a new pull request, #7472:
URL: https://github.com/apache/hadoop/pull/7472

   
   It is not used directly, but httpclient has a dependency, as do other 
apps/libraries.
   
   
   ### How was this patch tested?
   
   did a local release and verified that the commons-logging artifacts in a 
distro were 1.3.0;
   
   
   
   ### For code changes:
   
   - [X] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [X] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> Update commons-logging to 1.3.0
> -------------------------------
>
>                 Key: HADOOP-19086
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19086
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 3.4.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> although hadoop doesn't use the APIs itself, it bundles commons-logging as 
> things it depends on (http components) do.
> the version hadoop declares (1.1.3) is out of date compared to its 
> dependencies
> * update pom and LICENSE-binary



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to