Hi Matt, I think your choice to introduce Foo2 has caused some of these issues. Maybe I'm misunderstanding something, but you're implying that you're adding more functionality to Foo by creating a new interface called Foo2 that extends Foo. In doing so, you'll have to have a dex class entry for both Foo and Foo2, which is what brings backwards compatibility into question (older Interface.jar files will not contain a class def for Foo2, which your newer Implementation.jar will depend on. You attempted to move your Interface.jar definitions into Implementation.jar to get around this, but that causes problems in MyApp.apk, right?)
However, if you simply modify foo (backwards compatible-changes only), then there's no need for a new Dex entry. If you need a non-backwards compatible change, or if you add new interfaces, you're going to need a different Implementation.jar chosen automatically (either at build-time or run-time.) -Kenley -- 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
