On Wed, Mar 4, 2009 at 5:59 AM, Jean-Baptiste Queru <[email protected]> wrote: > > There are two steps in apicheck: > > -whether you changed a public API at all (that's the part that uses > current.xml), so that there is a mechanism to have any API change > reviewed and approved before they're submitted. > > -whether you broke binary compatibility by changing an API (that's the > part that uses 3.xml), so that applications compiled against previous > levels of the API (in this case 1 is 1.0 and 2 is 1.1) can continue to > work on this version. > > The first one is something that's open for review, but the second one > typically isn't.
Thanks JBQ. I am running into the second one. :-( This makes it important for me to try getting the changes to public api, I suppose. https://review.source.android.com/9070 [Dianne Hackborn] https://review.source.android.com/9069 [Jeff Hamilton] are the changes that would help devices with Ringer switch. -Jey --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
