And proguard.config=/path/to/proguard.cfg goes where? In the
build.xml? local.properties? There already seems to be a reference
to it in the add-proguard-release.xml:
<property name="proguard-conf" value="${proguard-conf.absolute.dir}/
proguard.cfg" />
I'm now thinking the previous error:
add-proguard-release.xml:35: Expecting class path separator ':' before
'{' in argument number 1
is the problem which somehow messes up it finding proguard if I
surround the path with quotes though it does away with this error.
The path has no spaces so quotes shouldn't be necessary and they
weren't needed before the 2.3 update. And I tried it pointing to the
Proguard installation previously used and also with the installation
that came with the 2.3 update.
As for Eclipse it doesn't seem to be running it through Proguard when
generating a signed release as it's not shrinking the size and the obf
folder is not getting updated unless it is putting one in some
undocumented location. I tried the signed release yesterday thinking
an option for Proguard might be the but saw none. In fact I see none
whatsoever in the Properties.
On Dec 13, 12:07 am, Xavier Ducrohet <[email protected]> wrote:
> once you've generated a standard build.xml with "android update
> project" all you need to do is set
> proguard.config=/path/to/proguard.cfg
>
> "android update project" should create a default proguard.cfg in the
> root of your folder as well. This file is very close to the one we
> gave in the blog post. That's all you need. no more mofiying
> build.xml, as it's built-in.
>
> As for Eclipse, proguard is there in release mode. This is when you
> export a release (signed / unsigned) app. default debug (incremental)
> builds are not run through proguard.
>
> Xav
>
>
>
> On Sun, Dec 12, 2010 at 7:13 PM, jtoolsdev <[email protected]> wrote:
> > The android update project --path <project> was done and it updated.
> > Since I do this infrequently I keep a text file with the instructions
> > handy. This seems to be some problem that the proguard.dir var no
> > longer works the same way it did before. IOW, previously it pointed
> > to:
>
> > proguard.dir=/Directory/Proguard/Is/Installed/In
>
> > or the lib directory where the proguard.jar is located. I also tried
> > pointing to the version of proguard that came with the 2.3 update.
> > I've tried a variety of combinations to no avail and was hoping
> > someone else found the same problem and solved it. The only mention
> > of the error message I supplied was rather cryptic and related to
> > Ganymede not Galileo.
>
> > On Dec 12, 6:08 pm, Zsolt Vasvari <[email protected]> wrote:
> >> You cannot use your pre-2.3 files. You basically need to renerate
> >> using android update/
>
> >> On Dec 13, 9:26 am, jtoolsdev <[email protected]> wrote:
>
> >> > I updated the android 2.3 and when I try to run the proguard builds
> >> > that worked before am getting this:
>
> >> > /add-proguard-release.xml:35: Problem: failed to create task or type
> >> > proguard
> >> > Cause: The name is undefined.
> >> > Action: Check the spelling.
> >> > Action: Check that any custom tasks/types have been declared.
> >> > Action: Check that any <presetdef>/<macrodef> declarations have taken
> >> > place.
>
> >> > This is on Ubuntu 10.04 with Eclipse 3.5.2 (Galileo). I've tried
> >> > pointing to both proguard directories the one I used before than the
> >> > one that was installed with 2.3. Also I had to add quotes around the
> >> > path or ant would stop dead with those with a classpath error (found
> >> > references to this error but only for Windows but quotes worked for
> >> > Linux too).
>
> >> > So what has changed? And also aren't we supposed to now be able to do
> >> > this with Eclipse rather than going to a terminal and running ant?
> >> > It's mentioned in the release notes but I don't see it in Eclipse (and
> >> > yes using 8.01 dev tools) nor anything on the Android development
> >> > site.
>
> >> > Isn't it fun when you update your app in a few minutes then get to
> >> > spend the afternoon trying to figure out some tool error like this to
> >> > do your release build?
>
> > --
> > 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
