The code works again by adding project B into A's Java Build Path. Not sure if it's the correct solution.
2012/3/26 James Su <[email protected]> > But the problem is that the code of library A and B are not owned by us, > we can't simply change their source code, though we can access them. I'm > just wondering if it's a change made in R17, as the code works with R16? > > > 2012/3/26 Nikolay Elenkov <[email protected]> > >> On Mon, Mar 26, 2012 at 12:08 PM, James Su <[email protected]> wrote: >> > Hi all, >> > Yesterday I updated my development environment to Android SDK R17, and >> > then it failed to build one of my library project (say A) which depends >> on >> > another library project (say B), because B's R class cannot be found in >> A. I >> > checked the code in A's gen/ and found that B's R class was no longer >> there, >> > but it was there when using R16. >> > Does anybody know how to fix this issue? >> > >> >> Change each project to use it's own R file. It will include all resources >> from >> projects it depends on. For example: >> >> In project B: >> >> import com.project.b.R; >> >> In project A: >> >> import com.project.a.R; >> >> -- >> 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 > > > -- 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
