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

stack commented on HBASE-6259:
------------------------------

IIRC, our current state spanning jsp and jamon is because the convertion went 
90% of the ways and Todd left the last few templates for someone else to do so 
someone other than he would know about jamon; none of us took him up on the 
last few convertions.

If you want to do something else, and I'd suggest that there should be a good 
reason for moving off one system to another, there is the spreadsheet Luke did 
a while back looking at templating systems for hadoop: 
https://spreadsheets.google.com/pub?key=0AtkkDCT2WDMXdC1HOEtnUHpCejJMbUhGeGJWUmh5dVE&hl=en&output=html
  Its out of HADOOP-7532.  That spreadsheet, while it looks great and 
comprehensive, it must be wrong because it has the Grails abomination coming 
out on top.  Besides Luke wanted something else altogether (See HADOOP-7532 for 
interesting templating system discussion).


                
> Unify all of the templates into one templating language
> -------------------------------------------------------
>
>                 Key: HBASE-6259
>                 URL: https://issues.apache.org/jira/browse/HBASE-6259
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>    Affects Versions: 0.96.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>              Labels: noob
>
> Right now .jsp and jammon templates can't share common parts as they are 
> un-related.  We should move to one templating language.  Maybe also move away 
> from jamon.

--
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

        

Reply via email to