Thanks, I've finally resolved the issues...my problems were to do with using Google's RequestFactory and the related dependencies: I have a GWT project using RequestFactory, and my Android project depended on the proxy declarations in that project. For others in a similar situation, if you're switching to 17:
(a) Make sure you use ServiceForName rather than Service so Android doesn't complain about dependencies on the server/entity classes (b) Create a JAR with the classes you need (the proxy interfaces and related stuff) and place it in the Anrdoid project's libs/ directory (note: it is libs/ and not lib/) - the new SDK will automatically make the jar accessible both at compile and run time (c) Make sure you include the classes in .apt_generated/ (the obfuscator class) On Thursday, March 22, 2012 6:37:42 PM UTC-7, Nikolay Elenkov wrote: > > On Fri, Mar 23, 2012 at 9:14 AM, Sekhar <allur <[email protected]>efx> > wrote:: > I updated to SDK 17 this morning and have been struggling ever since with > a > > ton of problems: library errors, run time issues, etc. Is there a way to > > revert to 16? > > > > Eclipse save old versions of plugins, so you could probably revert from the > 'Installation history' tab. Help->Install new software->Click the 'What's > already installed' link (there may be a more straightforward way to get > there). > > That said, dependency management in ADT17 is much, much better. Do > yourself a favour, read the changelog and update your projects. There are > also a couple of blogs with pretty pictures :) > > http://tools.android.com/recent/dealingwithdependenciesinandroidprojects<http://tools.android.com/recent/dealingwithdependenciesinandroidprojects> > > -- 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
