[Visualizers] (WIP CCUK-1659, CCUK-1658, CCUK-1649) Workaround for JSDoc issue to fix repeated namespaces and externals appearing in generated jsdoc documentation'. JSDoc doesn't de-duplicate namespaces declared in different files, e.g. https://github.com/jsdoc3/jsdoc/issues/272 . Since every visualizer uses the 'autn' namespace, they all declared it in a separate file, so you got a copy of the 'autn' namespace for every class which used it. While you can workaround this within one maven project, you'd get problems when all the artifacts were merged together for the master visualizer-docs template. As a workaround, we declare each namespace in a separate file and folder following a standard naming convention so duplicates overwrite each other and there's effectively only one file per namespace when the JsDoc documentation is generated.
[Visualizers] (WIP CCUK-1659, CCUK-1658, CCUK-1649) Workaround for JSDoc issue to fix repeated namespaces and externals appearing in generated jsdoc documentation'. JSDoc doesn't de-duplicate namespaces declared in different files, e.g. https://github.com/jsdoc3/jsdoc/issues/272 . Since every visualizer uses the 'autn' namespace, they all declared it in a separate file, so you got a copy of the 'autn' namespace for every class which used it. While you can workaround this within one maven project, you'd get problems when all the artifacts were merged together for the master visualizer-docs template. As a workaround, we declare each namespace in a separate file and folder following a standard naming convention so duplicates overwrite each other and there's effectively only one file per namespace when the JsDoc documentation is generated.

[git-p4: depot-paths = "//depot/products/frontend/visualizers/topicmap/ui/trunk/src/main/lib/autn/vis/topicmap/js/": change = 1082861]

hpe-idol/topic-map,hpe-idol/topic-map,hpautonomy/topic-map,hpautonomy/topic-map