[BZ 1114600] - Cannot load Metric red error when client time is different from server - Renaming Moment.java -> Instant.java to be 'language compliant' with Joda time and Java 8 time API.
itests-2 were broken beacuse Server and StorageNode entities now have a version column
[BZ 1114600] - Bulk revert of 3448429138161, cb5078b367f9e and 546cf53e3c588 - I reproduced the issue by changing the time on a client (browser) machine. But we don't support such a behavior. When changing only the timezone, I didn't reproduce the exception.

* Revert "[BZ 1114600] - Cannot load Metric red error when client time is different from server - Renaming Moment.java -> Instant.java to be 'language compliant' with Joda time and Java 8 time API."

This reverts commit 3448429138161a1fd329b3f937488ee65fd9a199.

* Revert "[BZ 1114600] - Cannot load Metric red error when client time is different from server - Moving Moment.java to core/domain module. There was CNF exception during the install, but also CLI can benefit from this timezone independent class as well. (because depending on number millis from 1970 is confusing - it may return different number on different timezones)"

This reverts commit cb5078b367f9ed8d268669fbdc122422e08dfa19.

* Revert "[BZ 1114600] - Cannot load Metric red error when client time is different from server - trying to resolve the time into # of milliseconds on the server side where the referential time zone is used. Introducing a new class called Moment for storing 5 integers: year, month, day, hours, minutes."

This reverts commit 546cf53e3c58825ca089aa90e49f1897de937887.
Bug 1074633 - RFE: Manage storage node snapshots

Fix StorageNodeComponentItest - basically our tests were running too fast.
Failures happened beause of fact, that lastModified file attribute is stored
in seconds - so our tests tended to generate several snapshots within same
second and that led to incorrect behavior of tested "takeSnapshot"
operation. Several console logging has also been added.
changes. Lines starting
Fix core domain tests and server itests when database does not have Server and StorageNode version columns

Version columns are not created as part of the db-upgrade process, but only when running the installer.
So we need something when running itests or core domain tests against an upgraded database.
[BZ 1149265] - Main menu bar appears on top of Favorites menu in IE - bringing favorites menu into foreground (by resetting the z-index to all it's parrents and setting it's z-index to a high value, all in CSS)
Fix server itests-2 : when creating a Storage Node or a Server as part of an itest, set the version column
[BZ 1149265] - Main menu bar appears on top of Favorites menu in IE - Incorporating the changes from Jay's pr #137. I.e. I18n, Remove the '#' href from the current user dropdown
[BZ 1152807] changing aggregation settings should not require server server restart
[1139735] fix test failures
Now that the storage installer needs to contact the DB to version-stamp the
rhq_storage_node table, the cassandra installer upgrade tests failed, because
they support no DB infrastructure.  To get around this added an installer
option to ignore the version stamping.  These options are not user-visible,
and who knows, maybe someday support will have a reason to use it.
[1151441] fix i-test failures
We can't cache the server name in the static block because i-tests don't
set rhq.server.high-availbility.name that early in the setup. It was fine
for production. So, now lazily cache the server name at the time
of the first request for server name.
[1151441] fix i-test failures (2)
The i-tests actually set/restore rhq.server.high-availability.name sysprop
in the before/after methods.  This allows testng to jump around and execute
tests in different classes, in different orders, while the server name
remains correct for each test.  Update the server name caching
mechanism to reset the cache when sysprop changes are detected.  I don't
think this has any production use case, but it's required for testing,
doesn't cost much, and still keeps the original fix for this BZ intact.
BZ 1145292 - Heap max size is variable, not trait

For PS Eden size, there is a new value every time this metric is collected. It
should not be a trait, and probably should be only captured very infrequently.

Reduce frequency by moving summary to detail for other pool data.
Bug 1135136 - NPE in MySQL plugin when PID_FILE value not found in database
Merge pull request #140 from genman/bug/1135136

Bug 1135136 - NPE in MySQL plugin when PID_FILE value not found in database
[BZ 1149265] - Main menu bar appears on top of Favorites menu in IE - z-index++
Merge pull request #138 from genman/bug/1145292

BZ 1145292 - Heap max size is variable, not trait

Agreed these traits should be turned into numeric metrics.
[BZ 1138688] - [windows] unable to log in to JON from FF - adding some magic to make the logging in working on newer browsers. Basically, some waiting (20ms) needed to be added before the redirect. Because of the fact that /login and /Coregui.html both uses the same gwt module some logic was added to distinguish between them and prevent the UI from rendering when user is still on the /login page.
[1139735] More i-test fallout, oracle only
Unlike Postgres, where DDL changes can be transactional, Oracle executes
DDL (like adding a column) like autocommit=true.  As such, it can't happen
within an existing Tx, which is what we have by default in out itest
setup beans (@PostConstruct).  Change things to execute the DDL outside
of an existing Tx.
BZ 1152154 - wait a few times during startup to ensure the agent has been given a fair chance to register before aborting