Xavier, yes, I'm referencing it through the Android settings, as the R files and resources seem to be handled correctly.
However, I found a work-around last night, which is adding a linked source to the app project, which is pointing to the library source directory. I didn't not think this was necessary, because I assumed this would be done by the plugin automatically. Seems the plugin is "forgetting" to add this linked source, at least in my case. Maybe you can have a look and fix this in one of the next versions. For now it seems to work for me. Thanks anyway! Cheers, Günther On 28 Aug., 02:26, Xavier Ducrohet <[email protected]> wrote: > Are you sure you're referencing it through the library system and not > in the standard JDT build-path? > > > > > > On Wed, Aug 25, 2010 at 1:54 AM, Günther <[email protected]> wrote: > > Xavier, > > > sorry to intrude here after a month, but I'm having the problem > > described above that the class files from the library project are not > > included in the apk-file at all. Compiling seems to be working, but I > > cannot run the application of course, since the classes are missing. I > > have a single library project (no external JARs), and an application > > project referencing it. > > > Since deg seems to have had problems more related to auto-refresh, > > what could cause my kind of behavior? > > > Thanks, > > Günther > > > On 13 Jul., 18:58, Xavier Ducrohet <[email protected]> wrote: > >> On Tue, Jul 13, 2010 at 1:33 AM, deg <[email protected]> wrote: > >> > A related question, too: I'm stuck with a few warning messages in one > >> > of my library files. This is bad enough on it's own (my dev style is > >> > generally a "zero warnings tolerated") but it's worse because Eclipse > >> > shows multiple copies of each warning; one for each open app that is > >> > using the library. Is there any way to educate Eclipse to treat all > >> > mentions of the library as the same? > > >> Not with the current implementation (linked folders). I haven't found > >> anything (yet?) that allows me to do what I want without creating a > >> linked folder in the main project. JDT is not flexible enough for > >> this. > > >> > Re shipping in binary form... that's really a pity. It defeats one of > >> > the major reasons to uselibraries. Any plans to fix this in the > >> > future? > > >> We don't have any plan at this time, but I hope to look into it later this > >> year. > > >> > I'll reply to Mark's message in a moment. Perhaps some merge between > >> >Androidlibrariesand his parcels would work well for everyone? > > >> This is a possibility. > > >> Xav > >> -- > >> Xavier DucrohetAndroidSDK Tech Lead > >> Google Inc. > > >> Please do not send me questions directly. Thanks! > > > -- > > You received this message because you are subscribed to the Google > > Groups "AndroidDevelopers" group. > > To post to this group, send email [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 > > -- > Xavier DucrohetAndroidSDK 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 [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
