New branch 'lkrejci/jon-api-comp' available with the following commits: commit e5e1732961e6444eabe8ff0c644e307f9bb04e68 Author: Lukas Krejci lkrejci@redhat.com Date: Fri Sep 27 17:43:01 2013 +0200
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA. [BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.
Commit 0ba8c5f (among other things) removed several public constants in MeasurementScheduleCriteria because they were improperly named and didn't do what they seemed to.
Users might be using those constants even if they don't do what they're supposed to. The constants have therefore been re-introduced with a deprecation notice.
commit 753b518342cb0e61eb0e1d0bd6840e800269bdb5 Author: Lukas Krejci lkrejci@redhat.com Date: Fri Sep 27 16:20:45 2013 +0200
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.
Commit 26959a31d8c37bcb86dc6a845b5707a277bff3cb made the constructor of the DatabaseQueryUtility private, which it should be, and removed an unused class.
While the chances of anyone either instantiating the utility class or using the absolutely useless DatabaseQueryUtility.StatementParameter are very slim, we need to keep API back-compat.
The public constructor and the class have been reintroduced with a deprecation notice.
commit 33bedccfcc7ab9e338eff685c0cfe136ce02bc1a Author: Lukas Krejci lkrejci@redhat.com Date: Fri Sep 27 15:06:43 2013 +0200
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.
The fix for bug 840512 changed the way we handle the value of an obfuscated property, which rendered the obfuscate() method unused. It has been removed which unfortunately is an API breaking change due to its protected visibility.
While the chances of anyone using that method are miniscule we cannot break the API. The method was re-introduced but made a NOOP so that it doesn't break the obfuscation. The deprecation notice on the method suggests to stop using it.
commit d551c40411cd790a13e9b35ba0bb06c4717bf910 Author: Lukas Krejci lkrejci@redhat.com Date: Fri Sep 27 15:02:58 2013 +0200
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.
The fix for bug 1000006 declared the constructor of o.r.c.d.configuration.ConfigurationUtility private. It previously had the default pulic constructor and hence this was a API breaking change.
While the utility class should have had the private constructor in first place, we cannot break the API, so the public constructor has been re-introduced with a deprecation notice.
commit 3efb3e45a976187e9e5558ead43bc9e6cf83445e Author: Lukas Krejci lkrejci@redhat.com Date: Fri Sep 27 14:46:57 2013 +0200
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.
Commit 85f75e0 removed 2 enum fields from the server details, because they are no longer used due to our move from DB to Cassandra for metric storage.
Nevertheless the clients might be using those fields to get back that information. To retain the backwards compatibility, we need to keep those enum fields, making the server details work without recompilation. The server details will no longer contain any information for the for those fields. The fact that some information might be missing is part of the contract of the ServerDetails class though, so the users should be able to handle that situation.
commit 52020fb226a9141901e9b07d95b9bc74937fe0e3 Author: Lukas Krejci lkrejci@redhat.com Date: Fri Sep 27 14:40:42 2013 +0200
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.
Commit a4b78eb6e1adeffaa519115a9ef07b3f00025168 fixed the handling of the server status, but changed the signature of o.r.c.d.cloud.Server#clearStatus() method in an incompatible way. Adding the old method back with a deprecation notice.
The chances of anyone using this method are miniscule but we need to retain back-compat.
commit 0d6c9e334f1310ee0bf21caf5d748e214a3eccf9 Author: Lukas Krejci lkrejci@redhat.com Date: Fri Sep 27 14:37:22 2013 +0200
[BZ 873866] - Minimizing API changes between JON 3.1.2.GA and JON 3.2.0.GA.
Bug 888927 changed the signature of the AlertConditionAvailabilityCategoryComposite class to add a missing parameter.
While the chances of anyone using this method miniscule, we need to retain the back-compat. Therefore I added the wrong constructor back with a deprecation notice.
commit 07cf818ae7d14e3a45422855e1439d2798f3754f Author: Lukas Krejci lkrejci@redhat.com Date: Mon Sep 23 15:37:06 2013 +0200
Adding intentional api changes for the new methods ported over from RHQ 4.4.0.
commit 715c9bdcd9709755711c5c9d70229f7b332a71da Author: Lukas Krejci lkrejci@redhat.com Date: Fri Sep 20 21:09:02 2013 +0200
(Almost) regain back-compat with RHQ 4.4.0 in script bindings.
rhq-commits@lists.fedorahosted.org