Yes, this is not great. The problem is our need to compile the library code as part of the main project, and Eclipse only really gives us access to linked source folder (it's so much easier in Ant because we control the input to javac). I'm not sure there are other ways, except than replacing the Java builder with our own (and this is not something I want to do).
Xav On Tue, May 25, 2010 at 6:51 AM, Mark Carter <[email protected]> wrote: > For me, the biggest problem with the Android Library Project feature, > is that library source files are showing up multiple times (once for > the library project and then once for each project that uses that > library project) in: > > 1. The main source view > 2. Call Hierarchy > 3. Compiler warnings/errors > > i.e. everything is duplicated making things much harder to manage. > > (this is a bit more detail of what I wrote earlier - but essentially > the same problem) > > -- > 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 > -- 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 [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
