[jira] Commented: (HADOOP-7070) JAAS configuration should delegate unknown application names to pre-existing configuration

[ https://issues.apache.org/jira/browse/HADOOP-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973499#action_12973499 ] Hadoop QA commented on HADOOP-7070: --- +1 overall. Here are the results of testing the la

[jira] Updated: (HADOOP-7070) JAAS configuration should delegate unknown application names to pre-existing configuration

[ https://issues.apache.org/jira/browse/HADOOP-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HADOOP-7070: Attachment: hadoop-7070.txt Same patch, simpler unit test. > JAAS configuration should delegate u

[jira] Commented: (HADOOP-7069) Replace forrest with supported framework

[ https://issues.apache.org/jira/browse/HADOOP-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973497#action_12973497 ] Eli Collins commented on HADOOP-7069: - Forrest is dog slow. The hadoop tar build spen

[jira] Commented: (HADOOP-7069) Replace forrest with supported framework

[ https://issues.apache.org/jira/browse/HADOOP-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973495#action_12973495 ] Carl Steinbach commented on HADOOP-7069: You can make Forrest work with JDK5 by ma

[jira] Commented: (HADOOP-7069) Replace forrest with supported framework

[ https://issues.apache.org/jira/browse/HADOOP-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973496#action_12973496 ] Carl Steinbach commented on HADOOP-7069: Sorry, what I meant is that it's possible

[jira] Assigned: (HADOOP-7010) Typo in FileSystem.java

[ https://issues.apache.org/jira/browse/HADOOP-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins reassigned HADOOP-7010: --- Assignee: Jingguo Yao > Typo in FileSystem.java > --- > >

[jira] Assigned: (HADOOP-7052) misspelling of threshold in conf/log4j.properties

[ https://issues.apache.org/jira/browse/HADOOP-7052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins reassigned HADOOP-7052: --- Assignee: Jingguo Yao > misspelling of threshold in conf/log4j.properties >

[jira] Assigned: (HADOOP-7061) unprecise javadoc for CompressionCodec

[ https://issues.apache.org/jira/browse/HADOOP-7061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins reassigned HADOOP-7061: --- Assignee: Jingguo Yao > unprecise javadoc for CompressionCodec > ---

[jira] Commented: (HADOOP-7070) JAAS configuration should delegate unknown application names to pre-existing configuration

[ https://issues.apache.org/jira/browse/HADOOP-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973459#action_12973459 ] Hadoop QA commented on HADOOP-7070: --- +1 overall. Here are the results of testing the la

[jira] Updated: (HADOOP-7070) JAAS configuration should delegate unknown application names to pre-existing configuration

[ https://issues.apache.org/jira/browse/HADOOP-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HADOOP-7070: Status: Patch Available (was: Open) > JAAS configuration should delegate unknown application name

[jira] Updated: (HADOOP-7070) JAAS configuration should delegate unknown application names to pre-existing configuration

[ https://issues.apache.org/jira/browse/HADOOP-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HADOOP-7070: Attachment: hadoop-7070.txt This should fix it - I did a similar version of this patch for our 20

[jira] Created: (HADOOP-7070) JAAS configuration should delegate unknown application names to pre-existing configuration

JAAS configuration should delegate unknown application names to pre-existing configuration -- Key: HADOOP-7070 URL: https://issues.apache.org/jira/browse/HADOOP-7070

[jira] Commented: (HADOOP-6298) BytesWritable#getBytes is a bad name that leads to programming mistakes

[ https://issues.apache.org/jira/browse/HADOOP-6298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973380#action_12973380 ] Hudson commented on HADOOP-6298: Integrated in Hadoop-Common-22-branch #8 (See [https://h

[jira] Commented: (HADOOP-7038) saveVersion script includes an additional \r while running whoami under windows

[ https://issues.apache.org/jira/browse/HADOOP-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973378#action_12973378 ] Hudson commented on HADOOP-7038: Integrated in Hadoop-Common-22-branch #8 (See [https://h

[jira] Commented: (HADOOP-7057) IOUtils.readFully and IOUtils.skipFully have typo in exception creation's message

[ https://issues.apache.org/jira/browse/HADOOP-7057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973379#action_12973379 ] Hudson commented on HADOOP-7057: Integrated in Hadoop-Common-22-branch #8 (See [https://h

[jira] Commented: (HADOOP-7019) Refactor build targets to enable faster cross project dev cycles.

[ https://issues.apache.org/jira/browse/HADOOP-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973354#action_12973354 ] Chris Douglas commented on HADOOP-7019: --- This is losing focus. The issue is trying t

[jira] Commented: (HADOOP-7019) Refactor build targets to enable faster cross project dev cycles.

[ https://issues.apache.org/jira/browse/HADOOP-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973355#action_12973355 ] Konstantin Boudnik commented on HADOOP-7019: +1 patch looks good. Thank you Lu

[jira] Commented: (HADOOP-7019) Refactor build targets to enable faster cross project dev cycles.

[ https://issues.apache.org/jira/browse/HADOOP-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973345#action_12973345 ] Hadoop QA commented on HADOOP-7019: --- -1 overall. Here are the results of testing the la

[jira] Updated: (HADOOP-7019) Refactor build targets to enable faster cross project dev cycles.

[ https://issues.apache.org/jira/browse/HADOOP-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Lu updated HADOOP-7019: Attachment: hadoop-7019-trunk-v2.patch v2 patch only moves si artifact out of mvn-install, as fi test issu

[jira] Commented: (HADOOP-7019) Refactor build targets to enable faster cross project dev cycles.

[ https://issues.apache.org/jira/browse/HADOOP-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973331#action_12973331 ] Konstantin Boudnik commented on HADOOP-7019: I'll try to explain it once more:

[jira] Commented: (HADOOP-7019) Refactor build targets to enable faster cross project dev cycles.

[ https://issues.apache.org/jira/browse/HADOOP-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973309#action_12973309 ] Luke Lu commented on HADOOP-7019: - I appreciate your concern, cos. But the fi tests are al