Warning: can't write resource [META-INF/MANIFEST.MF] (Duplicate zip entry [yyy.jar:META-INF/MANIFEST

转自：http://www.dancartoon.com/2012/01/14/fixing-proguard-warning-cant-write-resource-meta-infmanifest-mf/转自：

We're using ProGuard in our Android build and were getting a number of warnings regarding duplicate entries in the output jar. When ProGuard encounters resources in an input jar, it will by default copy the resources into the output jar. This is fine as long as you don't have multiple jars that contain resources with the same name. All jars(that I'm aware of) have manifest files, so attempting to use ProGuard with multiple input jars will cause warnings that look like: "Warning: can't write resource [META-INF/MANIFEST.MF] (Duplicate zip entry [yyy.jar:META-INF/MANIFEST.MF])".

The warnings are harmless, but a clean build is a happy build, so we might as well try and get rid of them. The ProGuard Manual actually describes what needs to be done, but it only provides a solution for the case where input jars are specified individually:

123	-injars in1.jar -injars in2.jar(!META-INF/MANIFEST.MF) -injars in3.jar(!META-INF/MANIFEST.MF)

view raw gistfile1.txt hosted with ❤ by GitHub

When using ProGuard in the Android build process, the default behavior is to pass in all input jars in a giant delimited(semi-colon on Windows) blob. I have done some experimentation, but was unable to determine how an input filter can be used when multiple jars(having absolute paths) are passed in this way. Fortunately, it's not too difficult to change the build process to pass in a list of input jars individually and with individual filters.

This is the relevant section of the standard Android build.xml(starting around line 700):

123456789101112131415161718192021222324252627282930313233

<!-- Build a path object with all the jar files that must be obfuscated.

This include the project compiled source code and any 3rd party jar

files. -->

</path>

<!-- Set the project jar files Path object into a single property. It'll be

all the jar files separated by a platform path-separator.

Each path must be quoted if it contains spaces.

-->

</firstmatchmapper>

</pathconvert>

<jar basedir="${out.classes.absolute.dir}"

destfile="${preobfuscate.jar.file}" />

@${proguard.config}

-injars ${project.jars}

-outjars "${obfuscated.jar.file}"

-libraryjars ${android.libraryjars}

-dump "${obfuscate.absolute.dir}/dump.txt"

-printseeds "${obfuscate.absolute.dir}/seeds.txt"

-printusage "${obfuscate.absolute.dir}/usage.txt"

-printmapping "${obfuscate.absolute.dir}/mapping.txt"

</proguard>

view raw gistfile1.xml hosted with ❤ by GitHub

The directives above create a new object that combines the location of the compiled jar along with other jars that were used during compilation. These locations are then joined into a string by the pathconvert task, which also does some transformation to ensure that paths containing spaces are quoted properly. Finally, the string from pathconvert(stored in project.jars) is passed into proguard via the statement: "-injars ${project.jars}"

Update(2013/02/11): paulpv has provided an updated config since the Android build system has changed since my original post. I have included his config here:

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394

<?xml version="1.0" encoding="UTF-8"?>

<!--

Suppress "Warning: can't write resource [META-INF/MANIFEST.MF] (Duplicate zip entry [classes.jar:META-INF/MANIFEST.MF])".

Per http://www.dancartoon.com/2012/01/14/fixing-proguard-warning-cant-write-resource-meta-infmanifest-mf/

Target "-obfuscate" copied from ${sdk.dir}/tools/ant/build.xml v21.

-->

<then>

<!-- Set the android classpath Path object into a single property. It'll be

all the jar files separated by a platform path-separator.

Each path must be quoted if it contains spaces.

-->

</firstmatchmapper>

</pathconvert>

<!-- Build a path object with all the jar files that must be obfuscated.

This include the project compiled source code and any 3rd party jar

files. -->

</path>

<!-- Set the project jar files Path object into a single property. It'll be

all the jar files separated by a platform path-separator.

Each path must be quoted if it contains spaces.

-->

<!--

Old:

New:

-->

<!--

Old:

New:

-->

</firstmatchmapper>

</pathconvert>

<!-- Turn the path property ${proguard.config} from an A:B:C property

into a series of includes: -include A -include B -include C

suitable for processing by the ProGuard task. Note - this does

not include the leading '-include "' or the closing '"'; those

are added under the <proguard> call below.

-->

</path>

<echo>proguard: $${project.all.classes.value}=${project.all.classes.value}</echo>

<jar basedir="${out.classes.absolute.dir}"

destfile="${preobfuscate.jar.file}" />

-include "${proguard.configcmd}"

-include "${out.absolute.dir}/proguard.txt"

-injars ${preobfuscate.jar.file}

${project.all.classes.value}

-outjars "${obfuscated.jar.file}"

-libraryjars ${project.target.classpath.value}

-dump "${obfuscate.absolute.dir}/dump.txt"

-printseeds "${obfuscate.absolute.dir}/seeds.txt"

-printusage "${obfuscate.absolute.dir}/usage.txt"

-printmapping "${obfuscate.absolute.dir}/mapping.txt"

</proguard>

</then>

</if>

</target>

</project>

view raw custom_rules.xml hosted with ❤ by GitHub

The goal of my changes is to preserve the manifest files from the original jar("preobfuscate.jar.file") and ignore(filter) the manifest files from the remaining input jar files. Since I haven't figured out how to filter input jars when passed in as a blob, I instead use the pathconvert task to transform each input jar location into a separate "-injars" statement with its own manifest filter. The property containing these locations is then passed into ProGuard directly via: "${project.jars}"

The solution isn't as clean as I would have liked, but it does fix the warnings.

Warning: can't write resource [META-INF/MANIFEST.MF] (Duplicate zip entry [yyy.jar:META-INF/MANIFEST相关推荐

java jar manifest文件,java打包jar，以及manifest文件使用说明
java打包jar,以及manifest文件使用说明 http://20921556.javaeye.com/blog/263974 关键字: java jar Java的一种文档格式,JAR文件非常 ...
java原生和SpringBoot读取jar包中MANIFEST.MF的方式
我们经常看到java的一些jar包META-INF目录下包含一个MANIFEST.MF文件,里面包含一些版本信息,标题,实现组织,很多第三方的jar包还会自定义一个属性. 本文讲解如何读取jar包中M ...
Maven打包自定义MANIFEST.MF键值对
编写java后,一般都是通过打包生成jar.war包提供使用,一般在打包后都会在jar包中生成MANIFEST.MF文件编写一个简单的java文件. package cn.kanyun;public ...
meta-inf文件夹以及MANIFEST.MF文件的作用
meta-inf相当于一个信息包,目录中的文件和目录获得Java 2平台的认可与解释,用来配置应用程序.扩展程序.类加载器和服务 manifest.mf文件,在用jar打包时自动生成的. META-I ...
MANIFEST.MF属性读写
本案例完整演示项目 https://download.csdn.net/download/cs4380/10835284 一.maven打包写入MANIFEST.MF属性本案例采用maven写入,可 ...
META-INF/MANIFEST.MF介绍
META-INF文件夹相当于一个信息包,目录中的文件和目录获得Java 2平台的认可与解释,用来配置应用程序.扩展程序.类加载器和服务.这个文件夹和其中的 MANIFEST.MF文件,在用jar打包时 ...
META-INF/MANIFEST.MF介绍 _
原文地址:https://www.cnblogs.com/jayworld/p/9767228.html META-INF文件夹相当于一个信息包,目录中的文件和目录获得Java 2平台的认可与解释,用 ...
Idea打包jar，MANIFEST.MF文件没有Main-Class属性 xxx.jar中没有主清单属性
Idea打包jar 下图中圈出来的路径不能是默认的,需要放在项目根路径下,修改为:D:\IntelliJIdea\project\MyFtpServer\META-INF\MANIFEST.MF. 修 ...
MANIFEST.MF文件的格式
MANIFEST.MF文件的格式 1. 基本格式属性名称+:+空格+属性值 2. 没行最多72个字符,换行继续必须以空格开头 3. 文件最后必须要有一个回车换行 4. Class-Path 当前路径 ...

Warning: can't write resource [META-INF/MANIFEST.MF] (Duplicate zip entry [yyy.jar:META-INF/MANIFEST

Warning: can't write resource [META-INF/MANIFEST.MF] (Duplicate zip entry [yyy.jar:META-INF/MANIFEST相关推荐

最新文章

热门文章