You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Dávid Paksy (Jira)" <ji...@apache.org> on 2025/03/27 10:32:00 UTC

[jira] [Updated] (HBASE-29223) Migrate Jamon pages back to JSP

     [ https://issues.apache.org/jira/browse/HBASE-29223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dávid Paksy updated HBASE-29223:
--------------------------------
    Description: 
While I was working on HBASE-28832 to migrate Bootstrap I noticed that HBase have a mix of JSP and Jamon code. Looks like HBASE-3835 started the work in 2011 of converting from JSP to Jamon, but the work didn't finish.

 

After the discussion of this in [https://lists.apache.org/thread/0c9to6rxzbf5f2x6t0x20408n15rdvmt] it seems that it would be a good idea to move the Jamon code back to JSP and get rid of the Jamon compiler dependency.

As a first step we could just move back the Jamon code to JSP (this Jira).

Then we can extract the Java code from JSP files to some backing beans (under new Jiras).

  was:
While I was working on HBASE-28832 to migrate Bootstrap I noticed that HBase have a mix of JSP and Jamon code. Looks like HBASE-3835 started the work in 2011 of converting from JSP to Jamon, but the work didn't finish.

 

After the discussion of this in [https://lists.apache.org/thread/0c9to6rxzbf5f2x6t0x20408n15rdvmt] it seems that it would be a good idea to move the Jamon code back to JSP and get rid of the Jamon compiler dependency.


> Migrate Jamon pages back to JSP
> -------------------------------
>
>                 Key: HBASE-29223
>                 URL: https://issues.apache.org/jira/browse/HBASE-29223
>             Project: HBase
>          Issue Type: Improvement
>          Components: UI
>            Reporter: Dávid Paksy
>            Priority: Major
>
> While I was working on HBASE-28832 to migrate Bootstrap I noticed that HBase have a mix of JSP and Jamon code. Looks like HBASE-3835 started the work in 2011 of converting from JSP to Jamon, but the work didn't finish.
>  
> After the discussion of this in [https://lists.apache.org/thread/0c9to6rxzbf5f2x6t0x20408n15rdvmt] it seems that it would be a good idea to move the Jamon code back to JSP and get rid of the Jamon compiler dependency.
> As a first step we could just move back the Jamon code to JSP (this Jira).
> Then we can extract the Java code from JSP files to some backing beans (under new Jiras).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)