not only it's should not be necessary, it really shouldn't be put there. The convention is to put them in the libs folder and add them to the build path. The reason is that if a member on your team want to use Ant instead of Eclipse, then it'll work too (the Ant script expects them to be in libs/)
I'm going to double check that this is still working. Xav On Sun, Jul 18, 2010 at 7:49 PM, Peter Eastman <[email protected]> wrote: > Thanks, that worked. It appears that the developer documentation page > cited above is incorrect. It explicitly says, "It is not necessary to > put external JARs in the assets folder." > > Peter > > -- > 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
