[jira] [Resolved] (HADOOP-10225) Publish Maven javadoc and sources artifacts with Hadoop releases.
[ https://issues.apache.org/jira/browse/HADOOP-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lewis John McGibbney resolved HADOOP-10225. --- Resolution: Won't Fix The original patch was allowed to stagnate. I've closed the Github PR. Someone else can take this on if they deem javadoc and sources being useful for consumers of the software. > Publish Maven javadoc and sources artifacts with Hadoop releases. > - > > Key: HADOOP-10225 > URL: https://issues.apache.org/jira/browse/HADOOP-10225 > Project: Hadoop Common > Issue Type: Improvement > Components: build, documentation >Affects Versions: 3.0.0-alpha1 >Reporter: Lewis John McGibbney >Assignee: Lewis John McGibbney >Priority: Major > Labels: hadoop, javadoc, maven, sources > Attachments: HADOOP-10225.patch > > > Right now Maven javadoc and sources artifacts do not accompany Hadoop > releases within Maven central. This means that one needs to checkout source > code to DEBUG aspects of the codebase... this is not user friendly. > The build script(s) should be amended to accommodate publication of javadoc > and sources artifacts alongside pom and jar artifacts. > Some history on this conversation can be seen below > http://s.apache.org/7qR -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-10225) Publish Maven javadoc and sources artifacts with Hadoop releases.
[ https://issues.apache.org/jira/browse/HADOOP-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551180#comment-15551180 ] Lewis John McGibbney commented on HADOOP-10225: --- cool, I'll have a crack tomorrow afternoon. Can you remind me of the committer workflow again.. it's been a while since I submitted a patch and I don't want to waste anyone's time. Thanks. > Publish Maven javadoc and sources artifacts with Hadoop releases. > - > > Key: HADOOP-10225 > URL: https://issues.apache.org/jira/browse/HADOOP-10225 > Project: Hadoop Common > Issue Type: Improvement > Components: build, documentation >Affects Versions: 3.0.0-alpha1 >Reporter: Lewis John McGibbney > Labels: hadoop, javadoc, maven, sources > Attachments: HADOOP-10225.patch > > > Right now Maven javadoc and sources artifacts do not accompany Hadoop > releases within Maven central. This means that one needs to checkout source > code to DEBUG aspects of the codebase... this is not user friendly. > The build script(s) should be amended to accommodate publication of javadoc > and sources artifacts alongside pom and jar artifacts. > Some history on this conversation can be seen below > http://s.apache.org/7qR -- 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-10225) Publish Maven javadoc and sources artifacts with Hadoop releases.
[ https://issues.apache.org/jira/browse/HADOOP-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551181#comment-15551181 ] Lewis John McGibbney commented on HADOOP-10225: --- cool, I'll have a crack tomorrow afternoon. Can you remind me of the committer workflow again.. it's been a while since I submitted a patch and I don't want to waste anyone's time. Thanks. > Publish Maven javadoc and sources artifacts with Hadoop releases. > - > > Key: HADOOP-10225 > URL: https://issues.apache.org/jira/browse/HADOOP-10225 > Project: Hadoop Common > Issue Type: Improvement > Components: build, documentation >Affects Versions: 3.0.0-alpha1 >Reporter: Lewis John McGibbney > Labels: hadoop, javadoc, maven, sources > Attachments: HADOOP-10225.patch > > > Right now Maven javadoc and sources artifacts do not accompany Hadoop > releases within Maven central. This means that one needs to checkout source > code to DEBUG aspects of the codebase... this is not user friendly. > The build script(s) should be amended to accommodate publication of javadoc > and sources artifacts alongside pom and jar artifacts. > Some history on this conversation can be seen below > http://s.apache.org/7qR -- 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-10225) Publish Maven javadoc and sources artifacts with Hadoop releases.
[ https://issues.apache.org/jira/browse/HADOOP-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551147#comment-15551147 ] Lewis John McGibbney commented on HADOOP-10225: --- Hi [~andrew.wang] wow this is a blast from the past :) Are you planning on a putting a ptch together for 3.0.0-alpha1 or do you want me to do it? > Publish Maven javadoc and sources artifacts with Hadoop releases. > - > > Key: HADOOP-10225 > URL: https://issues.apache.org/jira/browse/HADOOP-10225 > Project: Hadoop Common > Issue Type: Improvement > Components: build, documentation >Affects Versions: 3.0.0-alpha1 >Reporter: Lewis John McGibbney > Labels: hadoop, javadoc, maven, sources > Attachments: HADOOP-10225.patch > > > Right now Maven javadoc and sources artifacts do not accompany Hadoop > releases within Maven central. This means that one needs to checkout source > code to DEBUG aspects of the codebase... this is not user friendly. > The build script(s) should be amended to accommodate publication of javadoc > and sources artifacts alongside pom and jar artifacts. > Some history on this conversation can be seen below > http://s.apache.org/7qR -- 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] [Assigned] (HADOOP-12021) Augmenting Configuration to accomodate description
[ https://issues.apache.org/jira/browse/HADOOP-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lewis John McGibbney reassigned HADOOP-12021: - Assignee: Lewis John McGibbney Augmenting Configuration to accomodate description Key: HADOOP-12021 URL: https://issues.apache.org/jira/browse/HADOOP-12021 Project: Hadoop Common Issue Type: New Feature Components: conf Reporter: Lewis John McGibbney Assignee: Lewis John McGibbney Priority: Minor Fix For: 1.3.0, 2.8.0 Attachments: Screen Shot 2015-05-26 at 2.22.26 PM (2).png Over on the [common-dev|http://www.mail-archive.com/common-dev%40hadoop.apache.org/msg16099.html] ML I explained a use case which requires me to obtain the value of the Configuration description tags. [~cnauroth] advised me to raise the issue to Jira for discussion. I am happy to provide a patch so that the description values are parsed out of the various XML files and stored, and also that the Configuration class is augmented to provide accessors to accommodate the use case. I wanted to find out what people think about this one and whether I should check out Hadoop source and submit a patch. If you guys could provide some advice it would be appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12021) Augmenting Configuration to accomodate description
[ https://issues.apache.org/jira/browse/HADOOP-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14566714#comment-14566714 ] Lewis John McGibbney commented on HADOOP-12021: --- Hi Folks. The suggestions here have convinced me that the place to do this is over in Nutch as it is certainly application specific and just causing too much overhead in Hadoop. The text is not required in-memory within the Hadoop Configuration object. Augmenting Configuration to accomodate description Key: HADOOP-12021 URL: https://issues.apache.org/jira/browse/HADOOP-12021 Project: Hadoop Common Issue Type: New Feature Components: conf Reporter: Lewis John McGibbney Assignee: Lewis John McGibbney Priority: Minor Fix For: 1.3.0, 2.8.0 Attachments: Screen Shot 2015-05-26 at 2.22.26 PM (2).png Over on the [common-dev|http://www.mail-archive.com/common-dev%40hadoop.apache.org/msg16099.html] ML I explained a use case which requires me to obtain the value of the Configuration description tags. [~cnauroth] advised me to raise the issue to Jira for discussion. I am happy to provide a patch so that the description values are parsed out of the various XML files and stored, and also that the Configuration class is augmented to provide accessors to accommodate the use case. I wanted to find out what people think about this one and whether I should check out Hadoop source and submit a patch. If you guys could provide some advice it would be appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HADOOP-12021) Augmenting Configuration to accomodate description
[ https://issues.apache.org/jira/browse/HADOOP-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lewis John McGibbney resolved HADOOP-12021. --- Resolution: Not A Problem Thanks to everyone who commented here. Greatly appreciated. Augmenting Configuration to accomodate description Key: HADOOP-12021 URL: https://issues.apache.org/jira/browse/HADOOP-12021 Project: Hadoop Common Issue Type: New Feature Components: conf Reporter: Lewis John McGibbney Assignee: Lewis John McGibbney Priority: Minor Fix For: 1.3.0, 2.8.0 Attachments: Screen Shot 2015-05-26 at 2.22.26 PM (2).png Over on the [common-dev|http://www.mail-archive.com/common-dev%40hadoop.apache.org/msg16099.html] ML I explained a use case which requires me to obtain the value of the Configuration description tags. [~cnauroth] advised me to raise the issue to Jira for discussion. I am happy to provide a patch so that the description values are parsed out of the various XML files and stored, and also that the Configuration class is augmented to provide accessors to accommodate the use case. I wanted to find out what people think about this one and whether I should check out Hadoop source and submit a patch. If you guys could provide some advice it would be appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HADOOP-12021) Augmenting Configuration to accomodate description
[ https://issues.apache.org/jira/browse/HADOOP-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lewis John McGibbney updated HADOOP-12021: -- Attachment: Screen Shot 2015-05-26 at 2.22.26 PM (2).png Hi [~andrew.wang], please see attached screenshot which illustrates exactly what I am trying to do. You will see on the right hand side that the property description is not available with the current values being duplicates of the propertyname. This is due to the code currently not parsing out the values for the property descriptions. https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/conf/Configuration.java#L2661-L2692 I wanted to see if I could @override Configurtion#loadResource(Properties properties, Resource wrapper, boolean quiet) but I can't. Augmenting Configuration to accomodate description Key: HADOOP-12021 URL: https://issues.apache.org/jira/browse/HADOOP-12021 Project: Hadoop Common Issue Type: New Feature Components: conf Reporter: Lewis John McGibbney Priority: Minor Fix For: 1.3.0, 2.8.0 Attachments: Screen Shot 2015-05-26 at 2.22.26 PM (2).png Over on the [common-dev|http://www.mail-archive.com/common-dev%40hadoop.apache.org/msg16099.html] ML I explained a use case which requires me to obtain the value of the Configuration description tags. [~cnauroth] advised me to raise the issue to Jira for discussion. I am happy to provide a patch so that the description values are parsed out of the various XML files and stored, and also that the Configuration class is augmented to provide accessors to accommodate the use case. I wanted to find out what people think about this one and whether I should check out Hadoop source and submit a patch. If you guys could provide some advice it would be appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HADOOP-12021) Augmenting Configuration to accomodate description
Lewis John McGibbney created HADOOP-12021: - Summary: Augmenting Configuration to accomodate description Key: HADOOP-12021 URL: https://issues.apache.org/jira/browse/HADOOP-12021 Project: Hadoop Common Issue Type: New Feature Components: conf Reporter: Lewis John McGibbney Priority: Minor Fix For: 1.3.0, 2.8.0 Over on the [common-dev|http://www.mail-archive.com/common-dev%40hadoop.apache.org/msg16099.html] ML I explained a use case which requires me to obtain the value of the Configuration description tags. [~cnauroth] advised me to raise the issue to Jira for discussion. I am happy to provide a patch so that the description values are parsed out of the various XML files and stored, and also that the Configuration class is augmented to provide accessors to accommodate the use case. I wanted to find out what people think about this one and whether I should check out Hadoop source and submit a patch. If you guys could provide some advice it would be appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-12021) Augmenting Configuration to accomodate description
[ https://issues.apache.org/jira/browse/HADOOP-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14557145#comment-14557145 ] Lewis John McGibbney commented on HADOOP-12021: --- Hey Joep, I agree and thank you for the context and detail. This was already mentioned in part so it's great to see consensus on it generally being a 'bad' idea. I wonder if I can even override the function which parses out the XML. I wonder f anyone who wrote the original code or who can locate the parsing code can poitb me at it please? I'll then know whether I Can implement this on the Nutch side. Thanks for the prompt feedback it makes a huge difference. -- *Lewis* Augmenting Configuration to accomodate description Key: HADOOP-12021 URL: https://issues.apache.org/jira/browse/HADOOP-12021 Project: Hadoop Common Issue Type: New Feature Components: conf Reporter: Lewis John McGibbney Priority: Minor Fix For: 1.3.0, 2.8.0 Over on the [common-dev|http://www.mail-archive.com/common-dev%40hadoop.apache.org/msg16099.html] ML I explained a use case which requires me to obtain the value of the Configuration description tags. [~cnauroth] advised me to raise the issue to Jira for discussion. I am happy to provide a patch so that the description values are parsed out of the various XML files and stored, and also that the Configuration class is augmented to provide accessors to accommodate the use case. I wanted to find out what people think about this one and whether I should check out Hadoop source and submit a patch. If you guys could provide some advice it would be appreciated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HADOOP-10235) Hadoop tarball has 2 versions of stax-api JARs
[ https://issues.apache.org/jira/browse/HADOOP-10235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13873266#comment-13873266 ] Lewis John McGibbney commented on HADOOP-10235: --- This should be a simple exclusion in Maven no? [~tucu00] are you going to provide a patch? If not then maybe I can look in to it. Hadoop tarball has 2 versions of stax-api JARs -- Key: HADOOP-10235 URL: https://issues.apache.org/jira/browse/HADOOP-10235 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 3.0.0, 2.4.0 Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur They are: stax-api-1.0-2.jar stax-api-1.0.2.jar Maven cannot resolve them property because they are published under different groupIds, because of that for maven are different things. we need to exclude one of them explicitly -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (HADOOP-10225) Publish Maven javadoc and sources artifacts with Hadoop releases.
Lewis John McGibbney created HADOOP-10225: - Summary: Publish Maven javadoc and sources artifacts with Hadoop releases. Key: HADOOP-10225 URL: https://issues.apache.org/jira/browse/HADOOP-10225 Project: Hadoop Common Issue Type: Improvement Components: build Reporter: Lewis John McGibbney Right now Maven javadoc and sources artifacts do not accompany Hadoop releases within Maven central. This means that one needs to checkout source code to DEBUG aspects of the codebase... this is not user friendly. The build script(s) should be amended to accommodate publication of javadoc and sources artifacts alongside pom and jar artifacts. Some history on this conversation can be seen below http://s.apache.org/7qR -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HADOOP-10225) Publish Maven javadoc and sources artifacts with Hadoop releases.
[ https://issues.apache.org/jira/browse/HADOOP-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13869051#comment-13869051 ] Lewis John McGibbney commented on HADOOP-10225: --- Can someone please mark 'fix versions' box and i will produce patches for all branches this concerns? Thanks in advance Lewis Publish Maven javadoc and sources artifacts with Hadoop releases. - Key: HADOOP-10225 URL: https://issues.apache.org/jira/browse/HADOOP-10225 Project: Hadoop Common Issue Type: Improvement Components: build Reporter: Lewis John McGibbney Right now Maven javadoc and sources artifacts do not accompany Hadoop releases within Maven central. This means that one needs to checkout source code to DEBUG aspects of the codebase... this is not user friendly. The build script(s) should be amended to accommodate publication of javadoc and sources artifacts alongside pom and jar artifacts. Some history on this conversation can be seen below http://s.apache.org/7qR -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HADOOP-10225) Publish Maven javadoc and sources artifacts with Hadoop releases.
[ https://issues.apache.org/jira/browse/HADOOP-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13869078#comment-13869078 ] Lewis John McGibbney commented on HADOOP-10225: --- I am developing a patch for common-trunk however I would like to obtain some advice on the following: The parent pom.xml [0] defines X profiles, namely *src*, *dist*, *sign* and *clover*. I am unsure which profile the Hadoop release manager uses for pushing releases. Can someone (a release manager or someone familiar with the Maven profile(s) used within the release process) please confirm what the process actually is? Once I know this I can edit the Maven workflow and add the correct config. Thank you [0] https://svn.apache.org/repos/asf/hadoop/common/trunk/pom.xml Publish Maven javadoc and sources artifacts with Hadoop releases. - Key: HADOOP-10225 URL: https://issues.apache.org/jira/browse/HADOOP-10225 Project: Hadoop Common Issue Type: Improvement Components: build Reporter: Lewis John McGibbney Right now Maven javadoc and sources artifacts do not accompany Hadoop releases within Maven central. This means that one needs to checkout source code to DEBUG aspects of the codebase... this is not user friendly. The build script(s) should be amended to accommodate publication of javadoc and sources artifacts alongside pom and jar artifacts. Some history on this conversation can be seen below http://s.apache.org/7qR -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HADOOP-10225) Publish Maven javadoc and sources artifacts with Hadoop releases.
[ https://issues.apache.org/jira/browse/HADOOP-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lewis John McGibbney updated HADOOP-10225: -- Fix Version/s: 3.0.0 Publish Maven javadoc and sources artifacts with Hadoop releases. - Key: HADOOP-10225 URL: https://issues.apache.org/jira/browse/HADOOP-10225 Project: Hadoop Common Issue Type: Improvement Components: build Reporter: Lewis John McGibbney Fix For: 3.0.0 Right now Maven javadoc and sources artifacts do not accompany Hadoop releases within Maven central. This means that one needs to checkout source code to DEBUG aspects of the codebase... this is not user friendly. The build script(s) should be amended to accommodate publication of javadoc and sources artifacts alongside pom and jar artifacts. Some history on this conversation can be seen below http://s.apache.org/7qR -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HADOOP-10225) Publish Maven javadoc and sources artifacts with Hadoop releases.
[ https://issues.apache.org/jira/browse/HADOOP-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lewis John McGibbney updated HADOOP-10225: -- Labels: hadoop javadoc maven sources (was: ) Publish Maven javadoc and sources artifacts with Hadoop releases. - Key: HADOOP-10225 URL: https://issues.apache.org/jira/browse/HADOOP-10225 Project: Hadoop Common Issue Type: Improvement Components: build Reporter: Lewis John McGibbney Labels: hadoop, javadoc, maven, sources Fix For: 3.0.0 Attachments: HADOOP-10225.patch Right now Maven javadoc and sources artifacts do not accompany Hadoop releases within Maven central. This means that one needs to checkout source code to DEBUG aspects of the codebase... this is not user friendly. The build script(s) should be amended to accommodate publication of javadoc and sources artifacts alongside pom and jar artifacts. Some history on this conversation can be seen below http://s.apache.org/7qR -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HADOOP-10225) Publish Maven javadoc and sources artifacts with Hadoop releases.
[ https://issues.apache.org/jira/browse/HADOOP-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lewis John McGibbney updated HADOOP-10225: -- Attachment: HADOOP-10225.patch Patch for hadoop-common trunk codebase. Adds scm properties as well as a release profile to parent pom.xml. Using the maven-release-plugin like mvn release:clean release:prepare -DautoVersionSubmodules=true to check generated artifacts, then mvn release:perform to push the Maven artifacts to Nexus should do the trick. I've confirmed that sources and Javadoc artifacts are now generated locally. This works perfectly for us over on Apache Gora when we are doing the release procedure. Publish Maven javadoc and sources artifacts with Hadoop releases. - Key: HADOOP-10225 URL: https://issues.apache.org/jira/browse/HADOOP-10225 Project: Hadoop Common Issue Type: Improvement Components: build Reporter: Lewis John McGibbney Fix For: 3.0.0 Attachments: HADOOP-10225.patch Right now Maven javadoc and sources artifacts do not accompany Hadoop releases within Maven central. This means that one needs to checkout source code to DEBUG aspects of the codebase... this is not user friendly. The build script(s) should be amended to accommodate publication of javadoc and sources artifacts alongside pom and jar artifacts. Some history on this conversation can be seen below http://s.apache.org/7qR -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HADOOP-10225) Publish Maven javadoc and sources artifacts with Hadoop releases.
[ https://issues.apache.org/jira/browse/HADOOP-10225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13869165#comment-13869165 ] Lewis John McGibbney commented on HADOOP-10225: --- I would be happy to update documentation to accommodate the new *release* profile introduced here. I've asked for write permissions on the common-dev list http://www.mail-archive.com/common-dev%40hadoop.apache.org/msg11358.html Publish Maven javadoc and sources artifacts with Hadoop releases. - Key: HADOOP-10225 URL: https://issues.apache.org/jira/browse/HADOOP-10225 Project: Hadoop Common Issue Type: Improvement Components: build Reporter: Lewis John McGibbney Labels: hadoop, javadoc, maven, sources Fix For: 3.0.0 Attachments: HADOOP-10225.patch Right now Maven javadoc and sources artifacts do not accompany Hadoop releases within Maven central. This means that one needs to checkout source code to DEBUG aspects of the codebase... this is not user friendly. The build script(s) should be amended to accommodate publication of javadoc and sources artifacts alongside pom and jar artifacts. Some history on this conversation can be seen below http://s.apache.org/7qR -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HADOOP-8510) Implement auto-refresh for dsfhealth.jsp and jobtracker.jsp
[
https://issues.apache.org/jira/browse/HADOOP-8510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13295543#comment-13295543
]
Lewis John McGibbney commented on HADOOP-8510:
--
@Suresh thanks for the feedback. I'll cook up a patch today depending on what
the output is below.
@Devaraj {bp}Don't we have any issues like this for adding it here?{bq} Can you
elaborate a bit please I don't understand... Would this be helpful or not? If
it previously been removed for reasons you state then it would be a pointless
process me patching trunk... no? Thank you
Implement auto-refresh for dsfhealth.jsp and jobtracker.jsp
---
Key: HADOOP-8510
URL: https://issues.apache.org/jira/browse/HADOOP-8510
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 1.0.1
Reporter: Lewis John McGibbney
Priority: Trivial
A simple auto refresh switch would be nice from within the webapp. I am
pretty confused by which version to patch, I've looked in trunk and find
myself even more confused.
If someone would be kind enough to point out where I can check out code and
patch to include this issue then I'll happily submit the trivial patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-8510) Implement auto-refresh for dsfhealth.jsp and jobtracker.jsp
Lewis John McGibbney created HADOOP-8510: Summary: Implement auto-refresh for dsfhealth.jsp and jobtracker.jsp Key: HADOOP-8510 URL: https://issues.apache.org/jira/browse/HADOOP-8510 Project: Hadoop Common Issue Type: Improvement Affects Versions: 1.0.1 Reporter: Lewis John McGibbney Priority: Trivial A simple auto refresh switch would be nice from within the webapp. I am pretty confused by which version to patch, I've looked in trunk and find myself even more confused. If someone would be kind enough to point out where I can check out code and patch to include this issue then I'll happily submit the trivial patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
