Hi Kumar, here they are:
Bouncycastle jdk14 Mortbay w3cdom javaxservlet they are needed by sun's jxta to compile - the resulting jxta jar is about 1.8MB and all jars together imported into my app are close to 5.2MB. Thanks On Jul 26, 12:09 am, Kumar Bibek <[email protected]> wrote: > I have never come across such a problem. But I am wondering which jars > you are using and what are there combined sizes? > > -Kumar Bibekhttp://tech-droid.blogspot.com > > On Jul 25, 7:44 pm, kypriakos <[email protected]> wrote: > > > Hi all, > > > I looked for any info on this but could not find much. Originally > > I had a number of 3rd jars that I was importing into the Android > > project. The general concensus I got was that I needed to find > > the source for them and compile them in Android - well I kicked > > my behind and did all that and finally I have all jars in place for > > my Android app. The compilation and packaging of apk of the > > app with those jars sitting in the libs dir of the app takes 10-12 > > mins and towards the end it gives an Eclipse internal error > > and it quits! I tried doing this outside Eclipse using ant and still > > the same result. I have the java heap params jacked up for > > -xmx and -xms to 256MB and still no luck. The jars sum up > > to 6MB and the actual app to 0.25MB. The individual library > > directories that use to compile each of the 3rd jars compile > > fairly fast. > > > So I am wondering if anyone has any insights on this - is the > > Android plugin or in general the Android devices not meant to > > handle such large apks? Is there anything else I need to > > configure or look into to get this packaged? > > > Thanks very much > > Demetris -- 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
