[BZ 1070521] Fixed retrieval of OOB datapoints.
Make the test link for forced OOB calculation work again.
Deprecating the measurement aggregate JPA entity classes.
They're no longer used anywhere.
Revert "[BZ 1070521] Fixed retrieval of OOB datapoints."

The storage queries still don't work as expected.
This is what you get for late night commits.

This reverts the premature commit 6bf49506b834a6bcac699712610b76fdbd4d9e96.
BZ 991510 - Add method javadoc
[BZ 1070521] Fixed retrieval of OOB datapoints.
[BZ 1149687] - Storage Node's cluster status is DOWN when cluster maintenance is scheduled - considering the MAINTENANCE operation mode as NORMAL cluster status.
[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.
[1151441] JON server was unexpectedly stopped
Only resolve the identity of the running server (i.e. the SERVER_NAME) one
time and cache it as a static for ServerManagerBean.  This is more efficient
as the server name can not change at runtime, and actually should not change
for a defined server, ever, in general.  Moreover, for server where
rhq.server.high-availability.name is not set, it prevents repeated calls to
InetAddress.getLocalhost(), which can fail if there is a temporary DNS
issue, and the localhost can not be resolved.
[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)
[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.