Suppress warning duplicate input class
Java class file shrinker, optimizer, obfuscator, and preverifier
Brought to you by:
guardsquare
Menu
▾
▴
Logged In: YES
user_id=555208
The -ignorewarnings and -dontwarn options refer to warnings
about incomplete or corrupt input jars. These types of
problems may result in unusable output jars. Processing is
halted if there are any such warnings; no output jar is
produced. However, developers who know what they are doing
can chose to ignore the warnings:
-ignorewarnings still prints out the warnings but continues
processing,
-dontwarn doesn't even print out the warnings and continues
processing.
Using these options can be dangerous! It's always safer to
resolve the problems than to ignore the warnings.
Warnings about duplicate classes are different, since
duplicate classes don't hinder further processing.
Processing is never halted, but a warning is always printed.
This behavior might be changed, but it doesn't seem vital.
Different levels of verbosity might be useful.
Eric.
Logged In: YES
user_id=192116
Hi,
I understand that this is another level of verboisity. But from
the users point of view this is just another warning.
Probably it would be better to solve this by selecting a name
for these options that are easier to understand.
For the moment I understand that I don't have the possibility
to suppress this aoutput.
Dirk
Logged In: YES
user_id=227987
I hunted thru the code on this issue as well to see if there
was any conditional flag. Hopefully a future release will
supply a means to turn this specific warning off as well.
Thanks,
Dan
Logged In: YES
user_id=88952
Seems to me that what are currently called warnings in
proguard are in fact errors (they most likely will make the
result unusable), while the considered situation is a real
warning. Maybe introducing the notion of error
(-ignoreerrors and -dontprinterrors) would reduce the
confusion, and allow -dontprintwarnings to do what the
submitter expected.