Fount the solution, that worked for me:
adding
external.libs.dir=libs
to
default.properties
finally...
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 wrote:
> Hi folks,
>
> same problem here a
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 wrote:
> Add this file in the android-sdk-windows\tools\lib path. It will be solved
> i too h
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 wrote:
> Hi folks,
>
> same problem here after update:
>
> add-proguard-release.xml:35: Expecting class path separator ':'
> befo
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
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
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-
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 wrote:
> I've tried different setting with no success:
>
> - I
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 '
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 wrote:
> Is there any way to disable this functionality. I just want to keep working
>
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 ':' bef
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.co
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
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 an
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
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.
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 pr
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
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
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
Got ant 1.8.1 running, didn't help. Bizarre.
On Dec 14, 3:01 pm, jtoolsdev 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
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 bett
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:
I'm now thinking the previous error:
add-proguard-release.xml:35: Expecting class path separator ':' before
'{' in argument num
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
Can you give some details about your setup (jar files? libraries?)
On Mon, Dec 13, 2010 at 6:19 AM, jb 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 fail
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
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. Th
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 wrote:
> The android update project --path was
The android update project --path 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/Prog
You cannot use your pre-2.3 files. You basically need to renerate
using android update/
On Dec 13, 9:26 am, jtoolsdev 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 tas
29 matches
Mail list logo
