[
https://issues.apache.org/jira/browse/HBASE-27802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932945#comment-17932945
]
Nick Dimiduk commented on HBASE-27802:
--------------------------------------
I would very much prefer to avoid introducing a dependency on node/npm/&c.
until we want it for product features, even as a build-time dependency. My
preferences is that we rely only on existing dependencies, which would suggest
something like an exec plugin incantation that makes use of {{curl}}. Better
still if we could pull the resources from a mirror that's maintained by ASF
Infra rather than a 3rd party CDN.
Of course I'm open to other ideas.
> Manage static javascript resources programatically
> --------------------------------------------------
>
> Key: HBASE-27802
> URL: https://issues.apache.org/jira/browse/HBASE-27802
> Project: HBase
> Issue Type: Improvement
> Reporter: Nihal Jain
> Assignee: Nihal Jain
> Priority: Major
>
> Currently, the static JavaScript resources need to be manually managed. That
> is, if any of these has to be updated, we will be required to download them
> from web and place them under the appropriate path. This can be cumbersome.
> See list of JS under hbase-server at
> [https://github.com/apache/hbase/tree/master/hbase-server/src/main/resources/hbase-webapps/static/js]
> Need to find a way to manage them with minimal manual effort. Best case would
> be to manage them as part of build.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
