accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2983) Separate javascript resources (jquery, flot) from monitor
Date Thu, 07 Jul 2016 23:14:11 GMT


Christopher Tubbs commented on ACCUMULO-2983:

I was thinking about this a bit today, while examining our LICENSE/NOTICE files, and I think
this issue could simplify some of that, also.

Here are some options:

# Make the paths to the javascript and flot libraries configurable. The default could be to
retrieve them from a publicly available CDN. Customers requiring they be served locally can
change the configuration to retrieve them from an alternate source.
# Provide a way to load and serve these from the classpath without bundling them into our
jars. Make it easy to download these resources to the classpath.

These options could be combined... if it's served locally from the classpath, the configuration
could point to where it's served from Jetty, rather than require a separate local webservice
or CDN.

> Separate javascript resources (jquery, flot) from monitor
> ---------------------------------------------------------
>                 Key: ACCUMULO-2983
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: monitor
>            Reporter: Christopher Tubbs
>             Fix For: 2.0.0
> The javascript resources (namely jquery, and flot) are included directly in the monitor
jar, for inclusion on the classpath. The monitor then loads these resources, as needed, from
the classpath.
> Since these are third-party libraries, it may be better to include them as a dependency,
and put them in the lib directory.
> At the very least, this would help with downstream packaging, especially in situations
where third-party libraries cannot be included in a package, but it may help in other situations,
if we need to swap out a different version of jquery/flot dependencies.

This message was sent by Atlassian JIRA

View raw message