RE: [YETUS] let's start getting some releases out the door

2015-08-31 Thread Brahma Reddy Battula
Sean Busbey, thank for submitting a proposal. I am thinking , HADOOP-12312 needs to fixed...Since currently Findbugs HTML report link shows 0 warnings despite errorrs(Observed from couple of jira's). Thanks & Regards Brahma Reddy Battula From: Kengo Sek

[jira] [Created] (HADOOP-12369) Point hadoop-project/pom.xml java.security.krb5.conf within target folder

2015-08-31 Thread Andrew Wang (JIRA)
Andrew Wang created HADOOP-12369: Summary: Point hadoop-project/pom.xml java.security.krb5.conf within target folder Key: HADOOP-12369 URL: https://issues.apache.org/jira/browse/HADOOP-12369 Project:

[jira] [Reopened] (HADOOP-10571) Use Log.*(Object, Throwable) overload to log exceptions

2015-08-31 Thread Arpit Agarwal (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-10571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal reopened HADOOP-10571: Assignee: (was: Arpit Agarwal) Thanks Steve. The original patch is quite out of date

Build failed in Jenkins: Hadoop-common-trunk-Java8 #330

2015-08-31 Thread Apache Jenkins Server
See Changes: [cmccabe] HDFS-8965. Harden edit log reading code against out of memory errors (cmccabe) [wang] HADOOP-12368. Mark ViewFileSystemBaseTest and ViewFsBaseTest as abstract. -

[jira] [Created] (HADOOP-12367) Move TestFileUtil's test resources to resources folder

2015-08-31 Thread Andrew Wang (JIRA)
Andrew Wang created HADOOP-12367: Summary: Move TestFileUtil's test resources to resources folder Key: HADOOP-12367 URL: https://issues.apache.org/jira/browse/HADOOP-12367 Project: Hadoop Common

Build failed in Jenkins: Hadoop-common-trunk-Java8 #329

2015-08-31 Thread Apache Jenkins Server
See Changes: [jianhe] YARN-4092. Fixed UI redirection to print useful messages when both RMs are in standby mode. Contributed by Xuan Gong [jianhe] Move YARN-4092 to 2.7.2 [yliu] HDFS-8946. Improve choosing datanode storage

[jira] [Created] (HADOOP-12366) expose calculated paths

2015-08-31 Thread Allen Wittenauer (JIRA)
Allen Wittenauer created HADOOP-12366: - Summary: expose calculated paths Key: HADOOP-12366 URL: https://issues.apache.org/jira/browse/HADOOP-12366 Project: Hadoop Common Issue Type: New F

Build failed in Jenkins: Hadoop-common-trunk-Java8 #328

2015-08-31 Thread Apache Jenkins Server
See Changes: [wheat9] HDFS-8990. Move RemoteBlockReader to hdfs-client module. Contributed by Mingliang Liu. -- [...truncated 3900 lines...] [INFO] [INFO] <<< maven-source-plugin:2.3:j

Jenkins build is back to normal : Hadoop-Common-trunk #1630

2015-08-31 Thread Apache Jenkins Server
See

[jira] [Created] (HADOOP-12365) plugin for password, key, etc detection

2015-08-31 Thread Allen Wittenauer (JIRA)
Allen Wittenauer created HADOOP-12365: - Summary: plugin for password, key, etc detection Key: HADOOP-12365 URL: https://issues.apache.org/jira/browse/HADOOP-12365 Project: Hadoop Common I

Build failed in Jenkins: Hadoop-Common-trunk #1629

2015-08-31 Thread Apache Jenkins Server
See Changes: [jing9] HDFS-8980. Remove unnecessary block replacement in INodeFile. Contributed by Jing Zhao. -- [...truncated 5192 lines...] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0,

Build failed in Jenkins: Hadoop-common-trunk-Java8 #327

2015-08-31 Thread Apache Jenkins Server
See Changes: [jing9] HDFS-8980. Remove unnecessary block replacement in INodeFile. Contributed by Jing Zhao. -- [...truncated 3900 lines...] [INFO] [INFO] <<< maven-source-plugin:2.3:j

Re: Log4J 1.x -> EoL

2015-08-31 Thread Andrew Purtell
> Who knows what changes in the log4j configs? Will they still all work We looked at moving up to log4j2 over in HBase. One major stumbling block was the backwards incompatibility of configuration file format changes ( https://logging.apache.org/log4j/2.x/manual/migration.html). There is a bridge

Log4J 1.x -> EoL

2015-08-31 Thread Steve Loughran
https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces As of early August, Log4J 1.x is now officially dead outside some of the test runners, nothing in the code itself assumes log4j, just commons logging. Presumably the tests could be patched to move to 2.x -tho