Solution: Include the SDK and tools in your repository. Then tags/ branches will continue to build with the version they always did, and it takes an explicit action to upgrade them.
Problem introduced by solution: The SDK upgrade process is repository- hostile, and doesn't interact with things like .svn directories that track repository state, as it renames and deletes directories. Best to upgrade a separate copy, and use a suitable tool to merge in the changes. I use Araxis Merge for the purpose; it works well. But basic SCM practice is to capture as much of the build environment as possible. Tools that require installation in specific places or hooks into the OS can make that difficult-to-impossible, but this is Java. The change is still bad, in my opinion, but at least it's not necessary to be held hostage to tool changes. On Dec 10, 10:41 am, Matt Quigley <[email protected]> wrote: > AHH! This latest update to Android SDK v8 has made my life hell. > > 1. The change that makes the compiler fail when strings have multiple > formatter specifications (%d, %s, etc.) without position arguments > (%1d, %2s, etc.) is new. This means that ALL PREVIOUS TAGS/BRANCHES/ > ETC. IN THE REPOSITORY HISTORY WILL NO LONGER BUILD. -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
