Menu

#528 outjars = (directory) makes Proguard assume I'm NOT writing jars

v4.11
closed-fixed
warning (1)
High
2019-12-05
2014-05-25
leonbloy
No

I'm using 4.11 in this (not quite atypical, I hope) setup:

-injars '.../jars_raw' <--- this contains 3 raw jars
-outjars '.../jars_obfuscated' <--- this will contain 3 obfuscated jars

That is, I obfuscate 3 jars copying them to a different directory. I get the warning:

you're writing the processed class files to a directory [.../jars_obfuscated].
This will likely cause problems with obfuscated mixed-case class names.
You should consider writing the output to a jar file, or otherwise
specify '-dontusemixedcaseclassnames'.

This makes no sense. It's true that the output is a directory, but because the input are jars, so will be the outputs files, so this warning is inappropiate and misleading.

Discussion

  • Eric Lafortune

    Eric Lafortune - 2014-05-25

    Thanks for your report. You're right. ProGuard doesn't check if the input contains unpackaged .class files before printing this warning. For now, you can ignore the note, or even suppress it with -dontnote.

     
  • Eric Lafortune

    Eric Lafortune - 2014-05-25
    • status: open --> open-accepted
    • assigned_to: Eric Lafortune
     
  • T. Neidhart

    T. Neidhart - 2019-12-05
    • status: open-accepted --> closed-fixed
    • Priority: 5 --> High
     
  • T. Neidhart

    T. Neidhart - 2019-12-05

    That warning is not printed anymore when using the latest version 6.2.0.

     

Log in to post a comment.

MongoDB Logo MongoDB