You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2013/05/24 20:52:23 UTC

[jira] [Commented] (ACCUMULO-1462) resources config.html has hardcoded version

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

Christopher Tubbs commented on ACCUMULO-1462:
---------------------------------------------

This hard-coded version reflects what the shell looks like (will look like) at that version.

* The wrong way to fix this would be to simply update the version number.
* One right way to fix this would be to perform these commands in the newer version, as part of a documentation review process to update all documentation, and not just update the version, but update what the shell (or other command) actually outputs, so the documentation matches the behavior.
* The best way to fix this is to automate the generation of documentation based on shell output.

Automating some of the documentation would benefit a lot of our example READMEs, too.
                
> resources config.html has hardcoded version
> -------------------------------------------
>
>                 Key: ACCUMULO-1462
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1462
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: scripts
>            Reporter: John Vines
>            Priority: Minor
>             Fix For: 1.6.0, 1.5.1
>
>
> core/src/main/resources/org/apache/accumulo/core/conf/config.html is the file used for the header of the code generated based on the Properties. This file has a hardcoded version, which could also benefit from the mavenification of automated builds. But then again, it's also based on shell output, so there might be other magic involved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira