[
https://issues.apache.org/jira/browse/HBASE-29582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dávid Paksy updated HBASE-29582:
--------------------------------
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.
The sub-tasks capture all the work required for this.
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-29582
> URL: https://issues.apache.org/jira/browse/HBASE-29582
> Project: HBase
> Issue Type: Umbrella
> 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.
>
> The sub-tasks capture all the work required for this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
