Bug 863063

Summary: API changes between JON 3.0.1 and JON 3.1.0
Product: [JBoss] JBoss Operations Network Reporter: Lukas Krejci <lkrejci>
Component: Core ServerAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED WONTFIX QA Contact: Mike Foley <mfoley>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: JON 3.1.0CC: loleary, myarboro
Target Milestone: ---   
Target Release: JON 3.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-06 21:03:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
api-check-4.4.0.JON310GA-against-4.2.0.JON.3.0.1.GA.txt none

Description Lukas Krejci 2012-10-04 11:10:03 UTC 
Created attachment 621568 [details]
api-check-4.4.0.JON310GA-against-4.2.0.JON.3.0.1.GA.txt

Description of problem:
Since this was not done rigorously during the JON 3.1.0 release, I've locally augmented the JON 3.1.0 build with the support for api checks using Clirr and ran the check against JON 3.0.1.GA.

The results are attached. I don't think all of them represent a real problem but at least the one mentioned by bug 861434 is:
Comment 1 Larry O'Leary 2012-10-09 00:10:08 UTC 
There seem to be quite a few changes that will have negative impact on plug-in compatibility. 

Additionally, there are many changes to domain objects that will impact both plug-ins and client code running against the remote API.
Comment 2 mark yarborough 2012-11-06 21:03:12 UTC 
See https://bugzilla.redhat.com/show_bug.cgi?id=873866 for 3.1.2 equivalent (to perform same test for 3.1.2)