Description
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.
Attachments
Issue Links
- is related to
-
ACCUMULO-4741 Remove minified versions of JS and CSS
- Resolved
-
ACCUMULO-4739 Make 3rd party web resources (js, css) location configurable
- Resolved
- relates to
-
ACCUMULO-4356 Stop bundling dependencies in binary tarball
- Resolved
For more details about why these may not be included in other packages is because (at the very least) obfuscated/minimized code is not considered free software, according to http://www.gnu.org/philosophy/free-sw.html or open source, according to http://opensource.org/osd .
Additionally, because of these definitions, it may also mean that we shouldn't be releasing the minimized versions of these libraries in our source release. Rather, they should be minimized during the build.