On May 11, 1:44 am, Vinay S <[email protected]> wrote: > Hi Karteek, > > As Mr. Mark Murphy has suggested create a new project for your > reusable set of code. > > Export the same as Jar and include where ever you need them. > > Regards, > Vinay
I prefer instead something I saw recommended earlier on this list: Create your library in its own Android project in Eclipse, but link the library source directly into any other projects where you want to use it. On Windows, you have to use Eclipse's "link to source" option in the Build Path. On other platforms you can use a symlink to the root package of your library source if you like. With the export as jar option, you build the jar project, export it, and then supposedly the other projects will use the new jar. Unfortunately, what happens is that the other projects don't recognize that the jar is updated, and won't until you: refresh the project, remove the jar from the build path, and re-add it to the build path. With linked source I just compile and it all works. HTH, Bobby -- 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
