[jira] [Commented] (HADOOP-13660) Upgrade commons-configuration version to 2.1

2017-01-17 Thread Steve Loughran (JIRA) 

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

Steve Loughran commented on HADOOP-13660:
-

thanks...what I will do is have a patch for s3guard which also fixes up the 
dynamo reference; this will need to go into trunk without that bit of the 
patch. 

Testing things locally now in HADOOP-13994

> Upgrade commons-configuration version to 2.1
> 
>
> Key: HADOOP-13660
> URL: https://issues.apache.org/jira/browse/HADOOP-13660
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.0.0-alpha2
>Reporter: Sean Mackrory
>Assignee: Sean Mackrory
> Fix For: 3.0.0-alpha2
>
> Attachments: HADOOP-13660.001.patch, HADOOP-13660.002.patch, 
> HADOOP-13660.003.patch, HADOOP-13660.004.patch, HADOOP-13660.005.patch, 
> HADOOP-13660.006.patch, HADOOP-13660.007.patch, 
> HADOOP-13660-configuration2.001.patch
>
>
> We're currently pulling in version 1.6 - I think we should upgrade to the 
> latest 1.10.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

[jira] [Commented] (HADOOP-13660) Upgrade commons-configuration version to 2.1

2017-01-17 Thread Sean Mackrory (JIRA) 

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

Sean Mackrory commented on HADOOP-13660:


I don't recall but I just took a quick look. I'll bet what happened is I ran 
into the convergence issue in Azure (because as you said, that comes up if you 
remove the exclusion), and I excluded it and meant to go back and 
version-manage that more properly once everything else was working.

All tests pass for me now, and would have back then, but that's as close as I 
get to being confident that all azure storage codepaths are valid without that 
dependency. I'd be all for properly declaring the version we depend on in the 
hadoop-project pom as you're suggesting...

> Upgrade commons-configuration version to 2.1
> 
>
> Key: HADOOP-13660
> URL: https://issues.apache.org/jira/browse/HADOOP-13660
> Project: Hadoop Common
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 3.0.0-alpha2
>Reporter: Sean Mackrory
>Assignee: Sean Mackrory
> Fix For: 3.0.0-alpha2
>
> Attachments: HADOOP-13660.001.patch, HADOOP-13660.002.patch, 
> HADOOP-13660.003.patch, HADOOP-13660.004.patch, HADOOP-13660.005.patch, 
> HADOOP-13660.006.patch, HADOOP-13660.007.patch, 
> HADOOP-13660-configuration2.001.patch
>
>
> We're currently pulling in version 1.6 - I think we should upgrade to the 
> latest 1.10.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org