3 Commits

Author SHA1 Message Date
David Pursehouse
3ec838e578 Revert "Buck: Wipe out the machinery for merging JARs"
We need it again after the upgrade to Lucene 5.4.1.

This reverts commit 08cc835f99961b19b41c5958f5bdafe7ee458cc4.

Change-Id: I1798907e5e792005e6b78fcf9bbaaf36535d711b
2016-02-08 14:34:10 +09:00
David Ostrovsky
08cc835f99 Buck: Wipe out the machinery for merging JARs
Since I146fc74ed6 core-and-backward-codecs target was removed but
the toolchain that was added to merge non-generically maven JARs
was preserved. Remove it as well. We hope that we don't need it
and if yes, it would be easy to restore it again.

Change-Id: I65f7bdb39f9632e879071cdebf2083474738d333
2016-01-07 23:14:37 +01:00
Dave Borowitz
9a4efd3fff Merge Lucene core and backward-codecs jars
Both of these jars provide a provider-configuration file in
META-INF/services/org.apache.lucene.codecs.Codec registering their
respective implementations as providers of this codec. The proper way
to merge these files is to concatenate them, but the normal Buck build
process would otherwise choose one arbitrarily.

Add a new custom rule merge_maven_jars to merge multiple Maven jars
together using a simple Python script. The script concatenates all the
entries in two zip files, preferring the entry found in the first file
on the command line, which is still arbitrary but at least
deterministic. It specially handles files in the META-INF/services
directory by concatenating them.

Use this new rule to merge the old :core and :backward-codecs rules
into a single :core-and-backward-codecs rule.

Change-Id: I42fd1a130e42cb0eebf7bee61cfdf8545397cd09
2015-09-01 14:34:25 -04:00