Open fross opened 4 years ago
I can reproduce the issue, and I imagine it is a regression problem that needs to be investigated. For now you can work around it by specifying the output jars explicitly. ProGuard can only represent a single copy of each file, so you can filter out the manifest files, or with a small trick, temporarily rename them in the filter so they don't clash:
-injars input1.jar (META-INF/MANIFEST.MF->META-INF/MANIFEST.MF1,**)
-outjars output1.jar(META-INF/MANIFEST.MF1->META-INF/MANIFEST.MF,**)
-injars input2.jar (META-INF/MANIFEST.MF->META-INF/MANIFEST.MF2,**)
-outjars output2.jar(META-INF/MANIFEST.MF2->META-INF/MANIFEST.MF,**)
processed_applications
contains processed class files, all combined, and no jarsNote: duplicate definition of resource file [META-INF/MANIFEST.MF]
is output because of the combining process