Menu

#7 Problem with spaces in path

closed-invalid
None
5
2002-10-10
2002-10-10
Anonymous
No

If an -injars attribute contains a space character
proguard fails. Example:

-injars "c:\My stupid project location\out\test.jar"

Fails with
Expecting jar name separator ';' before 'stupid....

Related

Bugs: #708

Discussion

  • Eric Lafortune

    Eric Lafortune - 2002-10-10
    • assigned_to: nobody --> lafortune
    • status: open --> closed-invalid
     
  • Eric Lafortune

    Eric Lafortune - 2002-10-10

    Logged In: YES
    user_id=555208

    Spaces in file names are allowed (as of version 1.3), but
    the file names should then be quoted for ProGuard. If your
    shell swallows the quotes, you have to escape them or use
    additional quotes. I'm not sure about Windows, but in Unix,
    you can type

    -injars "'/some directory/some file.jar'"

    This may seem strange, but ProGuard allows any options on
    the command line to be grouped into arguments in any
    arbitrary way (e.g. '-injars "some file.jar"'), so it needs
    additional quotes to interpret file names with spaces. In
    configuration files, a single pair of quotes is sufficient
    because the shell will not interpret it.

    Eric.

     
  • David Jacobson

    David Jacobson - 2002-10-14

    Logged In: YES
    user_id=549708

    I think it's important to note that multiple jars separated
    by a semicolon need quoting separately, like:

    -injars "'/dir ectory1/some file1.jar';'/dir ectory2/some
    file2.jar'"

     

Log in to post a comment.

MongoDB Logo MongoDB