Re: [android-developers] R17: a library project cannot depend on another library project?
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 nikolay.elen...@gmail.com On Mon, Mar 26, 2012 at 12:08 PM, James Su james...@gmail.com 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 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 -- 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
Re: [android-developers] R17: a library project cannot depend on another library project?
On Mon, Mar 26, 2012 at 4:10 PM, James Su james...@gmail.com wrote: 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? I'm pretty sure this changed in R17, but check the project site for details: http://tools.android.com/ -- 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
Re: [android-developers] R17: a library project cannot depend on another library project?
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 james...@gmail.com 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 nikolay.elen...@gmail.com On Mon, Mar 26, 2012 at 12:08 PM, James Su james...@gmail.com 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 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 -- 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
Re: [android-developers] R17: a library project cannot depend on another library project?
On Mon, Mar 26, 2012 at 4:15 PM, James Su james...@gmail.com wrote: The code works again by adding project B into A's Java Build Path. Not sure if it's the correct solution. It's not. -- 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
Re: [android-developers] R17: a library project cannot depend on another library project?
Thanks a lot for your information. Is there any document describing the difference between adding a library into Java Build Path or as an android Library? 2012/3/26 Nikolay Elenkov nikolay.elen...@gmail.com On Mon, Mar 26, 2012 at 4:15 PM, James Su james...@gmail.com wrote: The code works again by adding project B into A's Java Build Path. Not sure if it's the correct solution. It's not. -- 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 -- 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
Re: [android-developers] R17: a library project cannot depend on another library project?
On Mon, Mar 26, 2012 at 7:47 PM, James Su james...@gmail.com wrote: Thanks a lot for your information. Is there any document describing the difference between adding a library into Java Build Path or as an android Library? This explains the changes in ADT17 and how libraries are handled, as well as the change that causes your issue (Cf 'Important change'). https://sites.google.com/a/android.com/tools/recent/dealingwithdependenciesinandroidprojects The best thing you can do is update your projects, or have them updated. If you can't do it right now, use ADT16 for the time being. -- 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
Re: [android-developers] R17: a library project cannot depend on another library project?
How does one downgrade to r16, or any non-latest version of the SDK at any time? Doug On Monday, March 26, 2012 6:35:18 AM UTC-7, Nikolay Elenkov wrote: The best thing you can do is update your projects, or have them updated. If you can't do it right now, use ADT16 for the time being. -- 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
[android-developers] R17: a library project cannot depend on another library project?
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? Thanks a lot James Su -- 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
Re: [android-developers] R17: a library project cannot depend on another library project?
On Mon, Mar 26, 2012 at 12:08 PM, James Su james...@gmail.com 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 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
