that's really strange. If this happens again, can you check if you have the corresponding .class files in the bin folder of your project?
Xav On Fri, Jun 25, 2010 at 2:10 AM, deg <d...@degel.com> wrote: > I mean that it did not include the library classes at all. Somehow, > even though all classes were visible at compile time (so the referring > classes in the main app compiled without error), the library classes > were not found at runtime, nor were they present when I spelunked into > the .apk file. > > This presumably caused by some form of my operator error. But, it's > not clear what I did wrong nor how I fixed it. (I'm still very much an > Eclipse newbie). > > > (That said, thanks for the auto-refresh tip. That will eliminate some > other nagging annoyances I've had). > > David > > On Jun 25, 1:06 am, Xavier Ducrohet <x...@android.com> wrote: >> What do you mean by "does not include the library classes"? >> >> Does it not include the code at all, or does it seem to include an >> older version of it? >> >> If it the later, I think this may be due to how Eclipse handles the >> linked folder. For eclipse, the files inside src/ in the library is a >> different file from the one in the main project in the linked folder >> coming from the library. >> >> If you edit the one from the library, you have to refresh the main >> project so that it picks it up. >> >> I would change your workspace to automatically refresh, it's a lot >> safer/better/easier. It's in the preferences under General > >> Workspace. >> >> >> >> >> >> On Thu, Jun 24, 2010 at 6:07 AM, deg <d...@degel.com> wrote: >> > Thanks. >> >> > It would be great if you could publish a roadmap of how the library >> > feature will look in the future. >> > For example, it would be great if library project could depend on >> > another library project. (Yes, I know I can use an external jar >> > instead. I'm doing that now, but the experience is not as smooth as >> > I'd like). >> >> > Also, per my original message, above, I sometimes see cases where >> > an .apk compiles without errors but does not include the library >> > classes. >> >> > David >> >> > On Jun 23, 8:03 pm, Xavier Ducrohet <x...@android.com> wrote: >> >> That's correct. >> >> >> At the moment the manifest of the library is only used to compile the >> >> resource of the library and figure out its package name, so it doesn't >> >> need to contain permissions, activities, services, etc... used by the >> >> library. >> >> >> However, all projects using the library must include those in their >> >> own manifest. >> >> >> In the future (hopefully not too distant) we'll be able to merge the >> >> content of the library manifest so that you don't have to do it >> >> manually for all projects using the library. >> >> >> Xav >> >> >> On Wed, Jun 23, 2010 at 8:52 AM, String <sterling.ud...@googlemail.com> >> >> wrote: >> >> > On Jun 23, 11:06 am, deg <d...@degel.com> wrote: >> >> >> >> Also, what are the rules for AndroidManifest elements? >> >> >> - Does the main package or an Android library (or both) need to >> >> >> declare a uses-permission for something that happens in library code? >> >> >> - If a library implements a BroadcastReceiver should it be declared in >> >> >> its manifest, or that of the application (or both)? >> >> >> - etc. >> >> >> > The library's manifest ONLY needs a <manifest> element with a >> >> > package="com.mylibrary.packagename" attribute. This isn't in the docs >> >> > AFAIK, but was stated in a post on this group by the Android platform >> >> > dev responsible for libraries. I can attest that I've done mine this >> >> > way and it works fine. >> >> >> > String >> >> >> > -- >> >> > You received this message because you are subscribed to the Google >> >> > Groups "Android Developers" group. >> >> > To post to this group, send email to android-developers@googlegroups.com >> >> > To unsubscribe from this group, send email to >> >> > android-developers+unsubscr...@googlegroups.com >> >> > For more options, visit this group at >> >> >http://groups.google.com/group/android-developers?hl=en >> >> >> -- >> >> Xavier Ducrohet >> >> Android SDK Tech Lead >> >> Google Inc. >> >> >> Please do not send me questions directly. Thanks!- Hide quoted text - >> >> >> - Show quoted text - >> >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Android Developers" group. >> > To post to this group, send email to android-developers@googlegroups.com >> > To unsubscribe from this group, send email to >> > android-developers+unsubscr...@googlegroups.com >> > For more options, visit this group at >> >http://groups.google.com/group/android-developers?hl=en >> >> -- >> Xavier Ducrohet >> Android SDK Tech Lead >> Google Inc. >> >> Please do not send me questions directly. Thanks! > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
