Perhaps, the ADT plugin checks if your project has got a newer build thats different from the previous one. And since you make changes to the library's code, the apk is not re-generated, and thus this problem.
On Sat, Nov 6, 2010 at 3:27 AM, Andy Selvig <ajsel...@gmail.com> wrote: > I'm developing an application that uses a library project to store > much of the functionality and content. When I edit the code and/or > content in the library and then run the app, it doesn't properly > restart the activity with the changes, giving the warning: > > Warning: Activity not started, its current task has been brought to > the front > > I understand that this warning comes from the SK not thinking that > there were any changes to the app, but there were (to the library, not > to the app itself). > > The only way that I've found to force the app to recompile with the > library changes is to do Project->Clean. While this is effective, it's > a bit annoying to have to do this every time a make a change. Does > anyone know of a way to force the SDK to recognize that a library > change should result in reloading the application? > > Thanks. > > -- > 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<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- Kumar Bibek http://techdroid.kbeanie.com http://www.kbeanie.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
