[android-developers] Re: Proguard problem after 2.3 update
Hi Roshan,
I use linux, and the adding to tools/lib did not help :(
maybe the add-proguard-release.xml should be updated in some way (due
to interface change?!?) ?
On 8 Feb., 07:44, roshan vidapanakal roshanrani2...@gmail.com wrote:
Add this file in the android-sdk-windows\tools\lib path. It will be solved
i too had the same prob before i solved it by adding
On Tue, Feb 8, 2011 at 12:00 PM, LeX fink.ale...@googlemail.com wrote:
Hi folks,
same problem here after update:
add-proguard-release.xml:35: Expecting class path separator ':'
before '{' in argument number 1
android-tools r9, target: android-8
Does anyone have a solution?!?
--
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
--
Regards,
Roshan
proguard.cfg
1KAnzeigenHerunterladen
--
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
[android-developers] Re: Proguard problem after 2.3 update
Fount the solution, that worked for me:
adding
external.libs.dir=libs
to
default.properties
finally...
found at
http://stackoverflow.com/questions/4356979/proguard-error-expecting-class-path-seperator-not-sure-where-i-need-to-put-a-p
On 8 Feb., 07:30, LeX fink.ale...@googlemail.com wrote:
Hi folks,
same problem here after update:
add-proguard-release.xml:35: Expecting class path separator ':'
before '{' in argument number 1
android-tools r9, target: android-8
Does anyone have a solution?!?
--
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
[android-developers] Re: Proguard problem after 2.3 update
Hi folks,
same problem here after update:
add-proguard-release.xml:35: Expecting class path separator ':'
before '{' in argument number 1
android-tools r9, target: android-8
Does anyone have a solution?!?
--
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
[android-developers] Re: Proguard problem after 2.3 update
Hi folks,
same problem here after update:
add-proguard-release.xml:35: Expecting class path separator ':'
before '{' in argument number 1
android-tools r9, target: android-8
Does anyone have a solution?!?
--
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
Re: [android-developers] Re: Proguard problem after 2.3 update
Add this file in the android-sdk-windows\tools\lib path. It will be solved
i too had the same prob before i solved it by adding
On Tue, Feb 8, 2011 at 12:00 PM, LeX fink.ale...@googlemail.com wrote:
Hi folks,
same problem here after update:
add-proguard-release.xml:35: Expecting class path separator ':'
before '{' in argument number 1
android-tools r9, target: android-8
Does anyone have a solution?!?
--
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
--
Regards,
Roshan
--
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
proguard.cfg
Description: Binary data
[android-developers] Re: Proguard problem after 2.3 update
Hi,
I am seeing the same problem as well. I followed the instructions
here:
http://android-developers.blogspot.com/2010/09/proguard-android-and-licensing-server.html,
and everything worked well for a while.
Then I did android update project today and since then I 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.
I have also added proguard.config=proguard.cfg to
default.properties.
Has anybody found a solution to this problem yet?
thanks!
CG
On Dec 22 2010, 12:56 pm, David C. Sousa davidcesar...@gmail.com
wrote:
Sameproblem, same message. If I knew I would have all this trouble, I
wouldn't have updated the android SDK. Even the docs are somewhat
outdated, wrong file names now (no big deal here, but it all adds up).
On 22 dez, 11:30, licorna lico...@gmail.com wrote:
I've tried different setting with no success:
- I've set PROGUARD_HOME ANDproguard.dir (in local.properties) to:
a)proguardincluded with SDK, b)proguard4.5 --stable-- c)proguard
4.6 --beta-- both HOME and /lib directories
- I'm using ant 1.8.1 (ant -version)
After changingproguard.dir to proguard_dir/lib I'm getting another
error: Expecting class path separator ':' before '{' in argument
number 1
I've lost almost an entire day trying to make this work!
Thanks!
On Dec 21, 7:15 pm, Fred Grott(Android
Expert,http://mobilebytes.wordpress.com)
fred.gr...@gmail.com wrote:
set PROGUARD_HOME to point to theproguardin your android sdk install..
I also had to do a manual ant 1.81 install on Ubuntu 10.04.1 Ubuntu 11
will
have ant 1.8 but Eclipse 3.7 will not have ant 1.81. until the end of the
beta process...ie May 2011..
I use a plugin called wickedshell to run ant 1.8.1 from shell in eclipse..
--
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
[android-developers] Re: Proguard problem after 2.3 update
Tried same script I used for windows and linux on mac It worked perfectly on mac and windows but not in Linux. Any one able to make proguard, ant script build with sdk r8 working in linux? I am using suse linux. Error I am getting is: ../ant/main_rules.xml:430: Expecting class path separator ':' before 'hands-free' in argument number 1 Thanks! -- 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
[android-developers] Re: Proguard problem after 2.3 update
Same problem, same message. If I knew I would have all this trouble, I
wouldn't have updated the android SDK. Even the docs are somewhat
outdated, wrong file names now (no big deal here, but it all adds up).
On 22 dez, 11:30, licorna lico...@gmail.com wrote:
I've tried different setting with no success:
- I've set PROGUARD_HOME AND proguard.dir (in local.properties) to:
a) proguard included with SDK, b) proguard 4.5 --stable-- c) proguard
4.6 --beta-- both HOME and /lib directories
- I'm using ant 1.8.1 (ant -version)
After changing proguard.dir to proguard_dir/lib I'm getting another
error: Expecting class path separator ':' before '{' in argument
number 1
I've lost almost an entire day trying to make this work!
Thanks!
On Dec 21, 7:15 pm, Fred Grott(Android
Expert,http://mobilebytes.wordpress.com)
fred.gr...@gmail.com wrote:
set PROGUARD_HOME to point to the proguard in your android sdk install..
I also had to do a manual ant 1.81 install on Ubuntu 10.04.1 Ubuntu 11 will
have ant 1.8 but Eclipse 3.7 will not have ant 1.81. until the end of the
beta process...ie May 2011..
I use a plugin called wickedshell to run ant 1.8.1 from shell in eclipse..
--
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
[android-developers] Re: Proguard problem after 2.3 update
I've tried different setting with no success:
- I've set PROGUARD_HOME AND proguard.dir (in local.properties) to:
a) proguard included with SDK, b) proguard 4.5 --stable-- c) proguard
4.6 --beta-- both HOME and /lib directories
- I'm using ant 1.8.1 (ant -version)
After changing proguard.dir to proguard_dir/lib I'm getting another
error: Expecting class path separator ':' before '{' in argument
number 1
I've lost almost an entire day trying to make this work!
Thanks!
On Dec 21, 7:15 pm, Fred Grott(Android Expert,
http://mobilebytes.wordpress.com)
fred.gr...@gmail.com wrote:
set PROGUARD_HOME to point to the proguard in your android sdk install..
I also had to do a manual ant 1.81 install on Ubuntu 10.04.1 Ubuntu 11 will
have ant 1.8 but Eclipse 3.7 will not have ant 1.81. until the end of the
beta process...ie May 2011..
I use a plugin called wickedshell to run ant 1.8.1 from shell in eclipse..
--
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
[android-developers] Re: Proguard problem after 2.3 update
Is there any way to disable this functionality. I just want to keep working so I think I will disable proguard for now. -- 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
[android-developers] Re: Proguard problem after 2.3 update
I am also getting problem with compiling the project with combination of linux (sdk updated r8), android-2.2, ant (1.8.1 ant -version says compiled on April 30 2010 ) and proguard. The problem i am getting from ant script is: .../ant/main_rules.xml:430: Expecting class path separator ':' before 'hands-free' in argument number 1 I checked all my paths and make sure all are clean. There is no problem with it. The strange thing is same build script and source code works perfectly fine in windows (sdk updated r8), android--2.2, ant (1.8.1) and proguard. I feel the android SDK r8 version for linux is not fully baked yet Or i might be missing some thing. I end up disabling proguard on linux for the time being. Is there any one able to make this combination working on Linux ? Thank! -- 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
[android-developers] Re: Proguard problem after 2.3 update
I disabled the Proguard build from Eclipse by commenting out the proguard.cfg reference in default.properties. Then did a Refresh from the project's menu so it would take effect. On Dec 22, 7:20 am, licorna lico...@gmail.com wrote: Is there any way to disable this functionality. I just want to keep working so I think I will disable proguard for now. -- 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
[android-developers] Re: Proguard problem after 2.3 update
I just update SDK to 2.3 and I'm facing the same problem here. I don't
use Eclipse, only ant to build my project. This is a list of
everything you recommend to do, and that I did:
1. Added key.store and key.alias to local.properties
2. Updated the project with android update project --path .
3. Added proguard.dir to local.properties with the path of the
proguard lib that came with the SDK (.../android_sdk/tools/proguard)
4. Added proguard.config=proguard.cfg to default.properties
I'm getting the same error: Problem: failed to create task or type
proguard.
Any ideas?
On Dec 15, 4:30 pm, jtoolsdev brianjto...@gmail.com wrote:
No I didn't do anything to Eclipse and looking at the Ant section it
is pointing to the 1.7.1 version but maybe a different one than in /
usr/bin/. All I know is after doing that it exported to Proguard.
What I haven't had time to try yet was a build from the console. Also
commenting out the proguard config in the default.properties did turn
off Proguard on the Export either as I wanted a build without it to
more easily track down a bug. Another thing I did do was rename my
Android SDK folder as it was ancient and I thought perhaps characters
in the path may have caused a problem. However I don't think that in
itself fixed the problem.
On Dec 15, 7:30 am, jb cona...@gmail.com wrote:
Did you update the ant plugin for Eclipse to 1.8.1? I know the current
version is 1.7.1 in Helios 3.6. If so how did you do that?
Or did you just install apache ant to your system? Did you have to
change the Ant preferences in Eclipse to point to your 1.8.1
installation?
Also, did you have to add -ignorewarning to your proguard.cfg to get
it to complete the Proguard phase?
jb
On Dec 14, 4:37 pm, jtoolsdev brianjto...@gmail.com wrote:
Well, after updating ant and exporting a signed app from Eclipse it
worked. I'll try command line later but for now it's out of the way.
The other problem which I see others posted on this group is LVL isn't
registering any license with emulators since the 2.3 update. I put
the signed obfuscated app on an emulator on another machine and the
license worked there but that installation is 2.2. It would be nice
to know what is causing that.
On Dec 14, 3:01 pm, jtoolsdev brianjto...@gmail.com wrote:
For those following this Android sneaked in an instruction that to
even use Proguard in Eclipse you need to modify the default.properties
file with the proguard.config=proguard.cfg (or wherever it is). This
however did not solve the problem. They also state elsewhere that you
need ant 1.8 or better (Ubuntu 10.04 comes with 1.7.1). Now that may
be the source of the parsing problem as soon as I figure out how this
apache-ant 1.8.1 install works. So far by instructions given it
isn't. Big problem with open source development is good developers
lousy docs. IT people probably shake their heads but we programmers
don't do these things everyday so concise and clear docs are
necessary. Development isn't supposed to be an adventure game.
I would also like to see centralized upgrade info for Android
development rather having to do a scavenger hunt for what has changed
in the development environment. Next time I'll wait for revision 2 or
higher.
On Dec 13, 12:56 pm, jtoolsdev brianjto...@gmail.com wrote:
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 x...@android.com 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
[android-developers] Re: Proguard problem after 2.3 update
I was successful with Eclipse in getting a build but it is hard to say
why. I still can't do a Proguard build from a command line and what
it looks like is for some reason the script has a hard time finding
the Proguard jar. Tried all kinds of combinations and none worked. I
am pointing to the recommended 1.8.1 ant in my ANT_HOME path though
Eclipse seems to be using the built-in 1.7.1 ant successfully. There
are many variables with this 2.3 SDK release that need to be sorted
out. Are problems with the Eclipse build due to not running Eclispe
Classic as I'm running Galileo and if so why? We really would like to
hear the reasons for such changes.
On Dec 21, 9:44 am, licorna lico...@gmail.com wrote:
I just update SDK to 2.3 and I'm facing the same problem here. I don't
use Eclipse, only ant to build my project. This is a list of
everything you recommend to do, and that I did:
1. Added key.store and key.alias to local.properties
2. Updated the project with android update project --path .
3. Added proguard.dir to local.properties with the path of the
proguard lib that came with the SDK (.../android_sdk/tools/proguard)
4. Added proguard.config=proguard.cfg to default.properties
I'm getting the same error: Problem: failed to create task or type
proguard.
Any ideas?
On Dec 15, 4:30 pm, jtoolsdev brianjto...@gmail.com wrote:
No I didn't do anything to Eclipse and looking at the Ant section it
is pointing to the 1.7.1 version but maybe a different one than in /
usr/bin/. All I know is after doing that it exported to Proguard.
What I haven't had time to try yet was a build from the console. Also
commenting out the proguard config in the default.properties did turn
off Proguard on the Export either as I wanted a build without it to
more easily track down a bug. Another thing I did do was rename my
Android SDK folder as it was ancient and I thought perhaps characters
in the path may have caused a problem. However I don't think that in
itself fixed the problem.
On Dec 15, 7:30 am, jb cona...@gmail.com wrote:
Did you update the ant plugin for Eclipse to 1.8.1? I know the current
version is 1.7.1 in Helios 3.6. If so how did you do that?
Or did you just install apache ant to your system? Did you have to
change the Ant preferences in Eclipse to point to your 1.8.1
installation?
Also, did you have to add -ignorewarning to your proguard.cfg to get
it to complete the Proguard phase?
jb
On Dec 14, 4:37 pm, jtoolsdev brianjto...@gmail.com wrote:
Well, after updating ant and exporting a signed app from Eclipse it
worked. I'll try command line later but for now it's out of the way.
The other problem which I see others posted on this group is LVL isn't
registering any license with emulators since the 2.3 update. I put
the signed obfuscated app on an emulator on another machine and the
license worked there but that installation is 2.2. It would be nice
to know what is causing that.
On Dec 14, 3:01 pm, jtoolsdev brianjto...@gmail.com wrote:
For those following this Android sneaked in an instruction that to
even use Proguard in Eclipse you need to modify the default.properties
file with the proguard.config=proguard.cfg (or wherever it is). This
however did not solve the problem. They also state elsewhere that you
need ant 1.8 or better (Ubuntu 10.04 comes with 1.7.1). Now that may
be the source of the parsing problem as soon as I figure out how this
apache-ant 1.8.1 install works. So far by instructions given it
isn't. Big problem with open source development is good developers
lousy docs. IT people probably shake their heads but we programmers
don't do these things everyday so concise and clear docs are
necessary. Development isn't supposed to be an adventure game.
I would also like to see centralized upgrade info for Android
development rather having to do a scavenger hunt for what has changed
in the development environment. Next time I'll wait for revision 2 or
higher.
On Dec 13, 12:56 pm, jtoolsdev brianjto...@gmail.com wrote:
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
[android-developers] Re: Proguard problem after 2.3 update
set PROGUARD_HOME to point to the proguard in your android sdk install.. I also had to do a manual ant 1.81 install on Ubuntu 10.04.1 Ubuntu 11 will have ant 1.8 but Eclipse 3.7 will not have ant 1.81. until the end of the beta process...ie May 2011.. I use a plugin called wickedshell to run ant 1.8.1 from shell in eclipse.. -- 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
[android-developers] Re: Proguard problem after 2.3 update
Did you update the ant plugin for Eclipse to 1.8.1? I know the current
version is 1.7.1 in Helios 3.6. If so how did you do that?
Or did you just install apache ant to your system? Did you have to
change the Ant preferences in Eclipse to point to your 1.8.1
installation?
Also, did you have to add -ignorewarning to your proguard.cfg to get
it to complete the Proguard phase?
jb
On Dec 14, 4:37 pm, jtoolsdev brianjto...@gmail.com wrote:
Well, after updating ant and exporting a signed app from Eclipse it
worked. I'll try command line later but for now it's out of the way.
The other problem which I see others posted on this group is LVL isn't
registering any license with emulators since the 2.3 update. I put
the signed obfuscated app on an emulator on another machine and the
license worked there but that installation is 2.2. It would be nice
to know what is causing that.
On Dec 14, 3:01 pm, jtoolsdev brianjto...@gmail.com wrote:
For those following this Android sneaked in an instruction that to
even use Proguard in Eclipse you need to modify the default.properties
file with the proguard.config=proguard.cfg (or wherever it is). This
however did not solve the problem. They also state elsewhere that you
need ant 1.8 or better (Ubuntu 10.04 comes with 1.7.1). Now that may
be the source of the parsing problem as soon as I figure out how this
apache-ant 1.8.1 install works. So far by instructions given it
isn't. Big problem with open source development is good developers
lousy docs. IT people probably shake their heads but we programmers
don't do these things everyday so concise and clear docs are
necessary. Development isn't supposed to be an adventure game.
I would also like to see centralized upgrade info for Android
development rather having to do a scavenger hunt for what has changed
in the development environment. Next time I'll wait for revision 2 or
higher.
On Dec 13, 12:56 pm, jtoolsdev brianjto...@gmail.com wrote:
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 x...@android.com 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 brianjto...@gmail.com
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 zvasv...@gmail.com wrote:
You cannot use your pre-2.3 files. You basically need to renerate
using android update/
On Dec 13, 9:26 am, jtoolsdev brianjto...@gmail.com wrote:
I updated the android 2.3 and when I try to run the proguard builds
that worked
[android-developers] Re: Proguard problem after 2.3 update
Did you update the ant plugin for Eclipse to 1.8.1? I know the current
version is 1.7.1 in Helios 3.6. If so how did you do that?
Or did you just install apache ant to your system? Did you have to
change the Ant preferences in Eclipse to point to your 1.8.1
installation?
Also, did you have to add -ignorewarning to your proguard.cfg to get
it to complete the Proguard phase?
jb
On Dec 14, 4:37 pm, jtoolsdev brianjto...@gmail.com wrote:
Well, after updating ant and exporting a signed app from Eclipse it
worked. I'll try command line later but for now it's out of the way.
The other problem which I see others posted on this group is LVL isn't
registering any license with emulators since the 2.3 update. I put
the signed obfuscated app on an emulator on another machine and the
license worked there but that installation is 2.2. It would be nice
to know what is causing that.
On Dec 14, 3:01 pm, jtoolsdev brianjto...@gmail.com wrote:
For those following this Android sneaked in an instruction that to
even use Proguard in Eclipse you need to modify the default.properties
file with the proguard.config=proguard.cfg (or wherever it is). This
however did not solve the problem. They also state elsewhere that you
need ant 1.8 or better (Ubuntu 10.04 comes with 1.7.1). Now that may
be the source of the parsing problem as soon as I figure out how this
apache-ant 1.8.1 install works. So far by instructions given it
isn't. Big problem with open source development is good developers
lousy docs. IT people probably shake their heads but we programmers
don't do these things everyday so concise and clear docs are
necessary. Development isn't supposed to be an adventure game.
I would also like to see centralized upgrade info for Android
development rather having to do a scavenger hunt for what has changed
in the development environment. Next time I'll wait for revision 2 or
higher.
On Dec 13, 12:56 pm, jtoolsdev brianjto...@gmail.com wrote:
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 x...@android.com 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 brianjto...@gmail.com
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 zvasv...@gmail.com wrote:
You cannot use your pre-2.3 files. You basically need to renerate
using android update/
On Dec 13, 9:26 am, jtoolsdev brianjto...@gmail.com wrote:
I updated the android 2.3 and when I try to run the proguard builds
that worked
[android-developers] Re: Proguard problem after 2.3 update
No I didn't do anything to Eclipse and looking at the Ant section it
is pointing to the 1.7.1 version but maybe a different one than in /
usr/bin/.All I know is after doing that it exported to Proguard.
What I haven't had time to try yet was a build from the console. Also
commenting out the proguard config in the default.properties did turn
off Proguard on the Export either as I wanted a build without it to
more easily track down a bug. Another thing I did do was rename my
Android SDK folder as it was ancient and I thought perhaps characters
in the path may have caused a problem. However I don't think that in
itself fixed the problem.
On Dec 15, 7:30 am, jb cona...@gmail.com wrote:
Did you update the ant plugin for Eclipse to 1.8.1? I know the current
version is 1.7.1 in Helios 3.6. If so how did you do that?
Or did you just install apache ant to your system? Did you have to
change the Ant preferences in Eclipse to point to your 1.8.1
installation?
Also, did you have to add -ignorewarning to your proguard.cfg to get
it to complete the Proguard phase?
jb
On Dec 14, 4:37 pm, jtoolsdev brianjto...@gmail.com wrote:
Well, after updating ant and exporting a signed app from Eclipse it
worked. I'll try command line later but for now it's out of the way.
The other problem which I see others posted on this group is LVL isn't
registering any license with emulators since the 2.3 update. I put
the signed obfuscated app on an emulator on another machine and the
license worked there but that installation is 2.2. It would be nice
to know what is causing that.
On Dec 14, 3:01 pm, jtoolsdev brianjto...@gmail.com wrote:
For those following this Android sneaked in an instruction that to
even use Proguard in Eclipse you need to modify the default.properties
file with the proguard.config=proguard.cfg (or wherever it is). This
however did not solve the problem. They also state elsewhere that you
need ant 1.8 or better (Ubuntu 10.04 comes with 1.7.1). Now that may
be the source of the parsing problem as soon as I figure out how this
apache-ant 1.8.1 install works. So far by instructions given it
isn't. Big problem with open source development is good developers
lousy docs. IT people probably shake their heads but we programmers
don't do these things everyday so concise and clear docs are
necessary. Development isn't supposed to be an adventure game.
I would also like to see centralized upgrade info for Android
development rather having to do a scavenger hunt for what has changed
in the development environment. Next time I'll wait for revision 2 or
higher.
On Dec 13, 12:56 pm, jtoolsdev brianjto...@gmail.com wrote:
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 x...@android.com 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 brianjto...@gmail.com
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
[android-developers] Re: Proguard problem after 2.3 update
For those following this Android sneaked in an instruction that to
even use Proguard in Eclipse you need to modify the default.properties
file with the proguard.config=proguard.cfg (or wherever it is). This
however did not solve the problem. They also state elsewhere that you
need ant 1.8 or better (Ubuntu 10.04 comes with 1.7.1). Now that may
be the source of the parsing problem as soon as I figure out how this
apache-ant 1.8.1 install works. So far by instructions given it
isn't. Big problem with open source development is good developers
lousy docs. IT people probably shake their heads but we programmers
don't do these things everyday so concise and clear docs are
necessary. Development isn't supposed to be an adventure game.
I would also like to see centralized upgrade info for Android
development rather having to do a scavenger hunt for what has changed
in the development environment. Next time I'll wait for revision 2 or
higher.
On Dec 13, 12:56 pm, jtoolsdev brianjto...@gmail.com wrote:
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 x...@android.com 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 brianjto...@gmail.com 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 zvasv...@gmail.com wrote:
You cannot use your pre-2.3 files. You basically need to renerate
using android update/
On Dec 13, 9:26 am, jtoolsdev brianjto...@gmail.com 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
[android-developers] Re: Proguard problem after 2.3 update
Got ant 1.8.1 running, didn't help. Bizarre.
On Dec 14, 3:01 pm, jtoolsdev brianjto...@gmail.com wrote:
For those following this Android sneaked in an instruction that to
even use Proguard in Eclipse you need to modify the default.properties
file with the proguard.config=proguard.cfg (or wherever it is). This
however did not solve the problem. They also state elsewhere that you
need ant 1.8 or better (Ubuntu 10.04 comes with 1.7.1). Now that may
be the source of the parsing problem as soon as I figure out how this
apache-ant 1.8.1 install works. So far by instructions given it
isn't. Big problem with open source development is good developers
lousy docs. IT people probably shake their heads but we programmers
don't do these things everyday so concise and clear docs are
necessary. Development isn't supposed to be an adventure game.
I would also like to see centralized upgrade info for Android
development rather having to do a scavenger hunt for what has changed
in the development environment. Next time I'll wait for revision 2 or
higher.
On Dec 13, 12:56 pm, jtoolsdev brianjto...@gmail.com wrote:
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 x...@android.com 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 brianjto...@gmail.com 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 zvasv...@gmail.com wrote:
You cannot use your pre-2.3 files. You basically need to renerate
using android update/
On Dec 13, 9:26 am, jtoolsdev brianjto...@gmail.com 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
[android-developers] Re: Proguard problem after 2.3 update
Well, after updating ant and exporting a signed app from Eclipse it
worked. I'll try command line later but for now it's out of the way.
The other problem which I see others posted on this group is LVL isn't
registering any license with emulators since the 2.3 update. I put
the signed obfuscated app on an emulator on another machine and the
license worked there but that installation is 2.2. It would be nice
to know what is causing that.
On Dec 14, 3:01 pm, jtoolsdev brianjto...@gmail.com wrote:
For those following this Android sneaked in an instruction that to
even use Proguard in Eclipse you need to modify the default.properties
file with the proguard.config=proguard.cfg (or wherever it is). This
however did not solve the problem. They also state elsewhere that you
need ant 1.8 or better (Ubuntu 10.04 comes with 1.7.1). Now that may
be the source of the parsing problem as soon as I figure out how this
apache-ant 1.8.1 install works. So far by instructions given it
isn't. Big problem with open source development is good developers
lousy docs. IT people probably shake their heads but we programmers
don't do these things everyday so concise and clear docs are
necessary. Development isn't supposed to be an adventure game.
I would also like to see centralized upgrade info for Android
development rather having to do a scavenger hunt for what has changed
in the development environment. Next time I'll wait for revision 2 or
higher.
On Dec 13, 12:56 pm, jtoolsdev brianjto...@gmail.com wrote:
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 x...@android.com 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 brianjto...@gmail.com 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 zvasv...@gmail.com wrote:
You cannot use your pre-2.3 files. You basically need to renerate
using android update/
On Dec 13, 9:26 am, jtoolsdev brianjto...@gmail.com 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
Re: [android-developers] Re: Proguard problem after 2.3 update
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 brianjto...@gmail.com 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 zvasv...@gmail.com wrote: You cannot use your pre-2.3 files. You basically need to renerate using android update/ On Dec 13, 9:26 am, jtoolsdev brianjto...@gmail.com 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 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 -- 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 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
[android-developers] Re: Proguard problem after 2.3 update
Hi Xavier, I ran android update project I made sure proguard.config=proguard.cfg was in default.properties. When I run ant release it gets to the proguard section and fails with: [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. proguard.cfg does include '-dontskipnonpubliclibraryclasses' I'm stuck, can't build, can't release. Please advise. jb On Dec 13, 12:07 am, Xavier Ducrohet x...@android.com 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 brianjto...@gmail.com 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 zvasv...@gmail.com wrote: You cannot use your pre-2.3 files. You basically need to renerate using android update/ On Dec 13, 9:26 am, jtoolsdev brianjto...@gmail.com 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 toandroid-develop...@googlegroups.com To unsubscribe from this group, send email toandroid-developers+unsubscr...@googlegroups.com 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 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
Re: [android-developers] Re: Proguard problem after 2.3 update
Can you give some details about your setup (jar files? libraries?) On Mon, Dec 13, 2010 at 6:19 AM, jb cona...@gmail.com wrote: Hi Xavier, I ran android update project I made sure proguard.config=proguard.cfg was in default.properties. When I run ant release it gets to the proguard section and fails with: [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. proguard.cfg does include '-dontskipnonpubliclibraryclasses' I'm stuck, can't build, can't release. Please advise. jb On Dec 13, 12:07 am, Xavier Ducrohet x...@android.com 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 brianjto...@gmail.com 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 zvasv...@gmail.com wrote: You cannot use your pre-2.3 files. You basically need to renerate using android update/ On Dec 13, 9:26 am, jtoolsdev brianjto...@gmail.com 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 toandroid-develop...@googlegroups.com To unsubscribe from this group, send email toandroid-developers+unsubscr...@googlegroups.com 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 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 -- 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 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
[android-developers] Re: Proguard problem after 2.3 update
These are the jar files I have that are part of my build [proguard] Reading input... [proguard] Reading program jar [/Users/xxx/dev/java/android/MyProg/ bin/proguard/original.jar] [proguard] Reading program jar [/Users/xxx/dev/java/android/MyProg/ libs/acra-2.0.3.jar] [proguard] Reading program jar [/Users/xxx/dev/java/android/MyProg/ libs/activation.jar] [proguard] Reading program jar [/Users/xxx/dev/java/android/MyProg/ libs/additionnal.jar] [proguard] Reading program jar [/Users/xxx/dev/java/android/MyProg/ libs/android-push.jar] [proguard] Reading program jar [/Users/xxx/dev/java/android/MyProg/ libs/mail.jar] [proguard] Reading library jar [/usr/local/JavaApps/android-sdk- mac_86/platforms/android-8/android.jar] [proguard] Reading library jar [/usr/local/JavaApps/android-sdk- mac_86/add-ons/addon_google_apis_google_inc_8/libs/maps.jar] [proguard] Initializing... [proguard] Warning: org.apache.harmony.awt.datatransfer.DataProxy: can't find superclass or interface java.awt.datatransfer.Transferable [proguard] Warning: org.apache.harmony.awt.datatransfer.NativeClipboard: can't find superclass or interface java.awt.datatransfer.Clipboard [proguard] Warning: javax.activation.CommandInfo: can't find referenced class java.beans.Beans [proguard] Warning: javax.activation.CommandInfo: can't find referenced class java.beans.Beans [proguard] Warning: com.sun.mail.imap.protocol.IMAPSaslAuthenticator: can't find referenced class javax.security.sasl.Sasl [proguard] Warning: com.sun.mail.imap.protocol.IMAPSaslAuthenticator: can't find referenced class javax.security.sasl.Sasl [proguard] Warning: com.sun.mail.imap.protocol.IMAPSaslAuthenticator: can't find referenced class javax.security.sasl.SaslClient [proguard] Warning: com.sun.mail.imap.protocol.IMAPSaslAuthenticator: can't find referenced class javax.security.sasl.SaslClient [proguard] Warning: com.sun.mail.imap.protocol.IMAPSaslAuthenticator: can't find referenced class javax.security.sasl.SaslClient [proguard] Warning: com.sun.mail.imap.protocol.IMAPSaslAuthenticator: can't find referenced class javax.security.sasl.SaslClient This is a partial list of about 247 can't find referenced class messages. If I add -ignorewarning to proguard.cfg then the release build completes. jb On Dec 13, 11:59 am, Xavier Ducrohet x...@android.com wrote: Can you give some details about your setup (jar files? libraries?) On Mon, Dec 13, 2010 at 6:19 AM, jb cona...@gmail.com wrote: Hi Xavier, I ran android update project I made sure proguard.config=proguard.cfg was in default.properties. When I run ant release it gets to the proguard section and fails with: [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. proguard.cfg does include '-dontskipnonpubliclibraryclasses' I'm stuck, can't build, can't release. Please advise. jb On Dec 13, 12:07 am, Xavier Ducrohet x...@android.com 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 brianjto...@gmail.com 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 zvasv...@gmail.com wrote: You cannot use your pre-2.3 files. You basically need to renerate using android update/ On Dec 13, 9:26 am, jtoolsdev brianjto...@gmail.com 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
[android-developers] Re: Proguard problem after 2.3 update
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 x...@android.com 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 brianjto...@gmail.com 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 zvasv...@gmail.com wrote:
You cannot use your pre-2.3 files. You basically need to renerate
using android update/
On Dec 13, 9:26 am, jtoolsdev brianjto...@gmail.com 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 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
--
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 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
[android-developers] Re: Proguard problem after 2.3 update
You cannot use your pre-2.3 files. You basically need to renerate using android update/ On Dec 13, 9:26 am, jtoolsdev brianjto...@gmail.com 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 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
[android-developers] Re: Proguard problem after 2.3 update
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 zvasv...@gmail.com wrote: You cannot use your pre-2.3 files. You basically need to renerate using android update/ On Dec 13, 9:26 am, jtoolsdev brianjto...@gmail.com 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 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
[android-developers] Re: Proguard problem after 2.3 update
I've had the same problem and solved it, but I don't remember exactly what I had done. I tried so many things, that I don't remember what fixed it. I do remember doing the android update, which is why I mentioned it. On Dec 13, 11:13 am, jtoolsdev brianjto...@gmail.com 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 zvasv...@gmail.com wrote: You cannot use your pre-2.3 files. You basically need to renerate using android update/ On Dec 13, 9:26 am, jtoolsdev brianjto...@gmail.com 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?- Hide quoted text - - Show quoted text - -- 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
