I guess you've probably looked into this already, but is there any way to make this work by adding the Android project to the build path (as opposed to making it a library project and then adding it as a library)?
>From a developer's perspective this would be more intuitive because projects would be referencing java projects and android projects in the same way. This would stop the problems regarding code apparently existing in two locations. As for the resources, couldn't your pre compiler handle that? For a shared Android project, the R class would be generated in the same way as before. For an Android project referencing shared Android projects, the R class would also include all the aggregated resources. If there is a way to make this work, it would be ideal, because it also supports deep nesting of Android projects. On May 25, 8:30 pm, Mark Carter <[email protected]> wrote: > One thing that makes things slightly easier is to uncheck the Builders -> > Java Builder of the Library project. This means that compiler > errors/warnings will not be duplicated. You still need to be sure you are > editing the code from MyApp/MyLibrary rather than MyLibrary. > > This doesn't help the call hierarchy problem though. > > Another option is just to use resource-only libraries and live with > replicating the java code in the top level apps. > > On 25 May 2010 19:49, Xavier Ducrohet <[email protected]> wrote: > > > > > > > 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]<android-developers%2Bunsubs > > > [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]<android-developers%2Bunsubs > > [email protected]> > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en > > -- > 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 > athttp://groups.google.com/group/android-developers?hl=en -- 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
