Bug 863063 - API changes between JON 3.0.1 and JON 3.1.0
Summary: API changes between JON 3.0.1 and JON 3.1.0
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Core Server
Version: JON 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: JON 3.1.2
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-04 11:10 UTC by Lukas Krejci
Modified: 2012-11-06 21:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-06 21:03:12 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
api-check-4.4.0.JON310GA-against-4.2.0.JON.3.0.1.GA.txt (41.99 KB, text/plain)
2012-10-04 11:10 UTC, Lukas Krejci 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 873866 0 urgent CLOSED Enable API Diff Checkbuild between JON minor/micro versions 2021-02-22 00:41:40 UTC

Internal Links: 873866

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)
Note You need to log in before you can comment on or make changes to this bug.