Colin Cross 635acc9446 Rearrange manifest file handling in merge_zips and soong_zip ... Jar always puts default MANIFEST.MF files in if none was specified. Copying that behavior in soong_zip causes problems with merge_zips, because it ends up taking the default manifest from the classes.jar instead of the user's manifest from res.jar. We don't want the user's manifest in the classes.jar, otherwise a change to the manifest will cause all the class files to rebuild. Instead, move the manifest insertion to the final merge_zips stage. Test: m -j checkbuild Change-Id: Id6376961dbaf743c2fb92843f9bdf2e44b963be0		2017-09-20 13:20:45 -07:00
..
config	Add -XDskipDuplicateBridges=true flag to javac	2017-09-19 12:19:36 -07:00
androidmk.go	Use same module name for java binary wrapper and jar	2017-09-07 17:00:22 -07:00
app.go	Rename no_standard_libraries to no_standard_libs	2017-08-31 13:48:52 -07:00
app_builder.go	Prettify soong ninja build descriptions	2017-05-10 11:04:16 -07:00
builder.go	Rearrange manifest file handling in merge_zips and soong_zip	2017-09-20 13:20:45 -07:00
gen.go	Remove non-idiomatic inheritance	2017-06-23 10:57:36 -07:00
java.go	Rearrange manifest file handling in merge_zips and soong_zip	2017-09-20 13:20:45 -07:00
java_test.go	Rearrange manifest file handling in merge_zips and soong_zip	2017-09-20 13:20:45 -07:00
resources.go	Make javac rules output a jar with soong_zip	2017-09-05 22:08:13 -07:00