having 3.xml while the cupcake API is still changing is a hack to hide a situation where according to the tools cupcake isn't backward-compatible with 1.1 (where the 1.1 API is 2.xml). When the cupcake API freezes, we'll copy the then-current current.xml into the "real" 3.xml.
(manually) modifying 3.xml should only be for cases where we're knowingly hiding a case where the tool complains about API compatibility but for one reason or another we've determined that it's actually OK. That's a very rare instance, though. JBQ On Wed, Mar 4, 2009 at 3:23 PM, Jey Michael <[email protected]> wrote: > >> 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. > > This 3.xml is mapping to cupcake release (1.5?) I suppose. > In my case, I created a new recent workspace just to push code into > gerrit. With my changes, now the build does not complain about 3.xml > anymore. Should I still add the new entries in 3.xml and include in > my submission? > > -Jey > > > > -- Jean-Baptiste M. "JBQ" Queru Android Engineer, Google. Questions sent directly to me that have no reason for being private will likely get ignored or forwarded to a public forum with no further warning. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
