I am having the same issues. I previously used the tutorial on the official Android Developers Blog to set up an Ant build that integrated ProGuard and it all worked fine. After updating the SDK and tools to 2.3, that automated build broke, so I tried using the new integration method for Eclipse and ProGuard. I think it's not finding my external JARs in the 'libs' directory, but no matter what I specify in '-libraryjars' it can't seem to find them.
Is there any special format for defining paths on this '-libraryjars' option? I have more than 1 external JAR. On Dec 8, 4:08 pm, jb <cona...@gmail.com> wrote: > Hi, > > I just updated my SDK to 2.3 and ADT to 8.01. > I updated 'default.properties' to include: > proguard.config=proguard.cfg > proguard.cfg is in my project root directory. > One of the entries in my proguard.cfg is '- > dontskipnonpubliclibraryclasses' > > When I run a release with ant (or export with Eclipse) it appears that > the proguard.cfg is not being read by proguard. I get the following > message from proguard. > > Warning: there were 247 unresolved references to classes or > interfaces. > [proguard] You may need to specify additional library jars > (using '-libraryjars'), > [proguard] or perhaps the '-dontskipnonpubliclibraryclasses' > option. > > Any ideas or suggestions. > > jb -- 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
