Tidy logging, javadocs, ...
[NXCM-5148] Install all icon styles for an iconcontainer instance into a single stylesheet (ie{8,9,?} have limitations on the # of these before it looses its shit)
Will need to optimize this further to allow all iconcontainer instances to share a single stylesheet so this can scale better past 31
Remove custom Ext.util.CSS implementation which was handling ie9 due to ^^^, but once ^^^ its not needed.
Merge pull request #788 from sonatype/one-stylesheet-per-iconcontainer

REVIEW: Reduce # of dynamic stylesheets for better IE compat
nexus oss 2.4.0-06

Signed-off-by: Sonatype Release Machine <release@sonatype.com>
NEXUS-5639: Rename WL

UI panel mods:
* tab title renamed from "Whitelist" to "Routing"
* tab name changed from "whitelist" to "routing"
* "Force remote discovery" button renamed to "Update now"
NEXUS-5639: Cleaning log messages

In EventDispatcher
NEXUS-5639: Cleaning log messages

In WLManagerImpl
NEXUS-5639: Cleaning log messages

In AbstractMavenRepo
NEXUS-5639: "Deep" rename WL to Routing

Initial code changes, bundle smoke tested and is working.

Tests and ITs not verified yet.
NEXUS-5639: URL change of the resources

Client is handled too
NEXUS-5639: M2 repo external config change

Renamed externalConfiguration nodes too
NEXUS-5639: Rename thread names

From "wl" to "ar" as Auto routing...
Merge pull request #794 from sonatype/nexus-5639-rename-wl

[2.4 blocker] NEXUS-5639: Rename WL
Merge pull request #795 from sonatype/nexus-5639-rename-wl-deep

[blocker 2.4] NEXUS-5639: Deep rename of WL into Routing
Back to version 2.4-SNAPSHOT
NEXUS-5602: Using the periodic update thread for initial updates too

On 1st boot of updated instances, a lot of MavenRepository
instances (hosted and proxy) will be piled up in the array
needUpdateRepositories in WLManagerImpl#startup().

Currently, as the thread pool with fixed size of 5 and
blocking queue was deferring update.

With this change, the for-loop doing initial WL build
(walk of the content for hosted and discovery for proxies)
is deferred, and periodic updater thread is used.

This also means, that upon boot, the initial delay of
first run will be applied, and on that moment on, hosted
reposes will have WL, not before that.

Initial change breaks all the UTs and ITs that uses
exposed-for-tests-only method to reach a state when
the test should start.

isUpdateWhitelistJobRunning() method used for this
is now updated, and will flag (and make tests wait)
as long as boot sequence is done (newly added) AND
there are no bg updates running (as before).

Also, EventDispatcher simplified, the feature active
flag is not passed anymore, instead, it is not
registered to event bus when feature is not
active, resulting in same behavior (before, when
feature was inactive EventDispatcher got events
but simply did not invoke WL Manager).
Merge pull request #792 from sonatype/nexus-5602-using-updater-for-initial-update

REVIEW: NEXUS-5602: Using the periodic update thread for initial updates too
Fixing the build.

Prefix updates happens async on config
save, and the UT did not properly wait for
them.
NEXUS-5654 fixed deadlock during concurrent deploy

Propagation of prefix file changes from members to group repositories
was acquiring read-lock on all group members while holding write-lock
on one of the members. Two such changes executed concurrently for
different members of the same group will almost certainly result in
deadlock. Solution is to execution group prefix file update on a
separate thread.

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
Cleanup: removed extra prefix and noscrape paths

There is currently no use case for these extra file paths,
they complicate the code and make proper synchronization
harder to implement.

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>