Oh, and one more thing - if you're merging these two into a single bundle, you should just be able to merge the contents of the META-INF/services files with the same name...
On 23 December 2013 14:34, David Bosschaert <[email protected]> wrote: > Hi Charles, > > If these files are just for use with ServiceLoader you might not want > to export the packages at all and look at the OSGi Service Loader > Mediator spec [1] or the Apache Aries SPI-Fly project [2] (which > implements that spec) for a solution? > > Cheers, > > David > > [1] Chapter 133 in OSGi Enterprise R5 http://www.osgi.org/Download/Release5 > [2] http://aries.apache.org/modules/spi-fly.html > > On 23 December 2013 14:20, Charles Moulliard <[email protected]> wrote: >> Hi, >> >> I'm facing issues to generate a bundle (= merge of ElasticSearch + Lucene >> artifacts). Why : They both share same files under this directory >> META-INF/services : >> >> org.apache.lucene.codecs.Codec >> org.apache.lucene.codecs.DocValuesFormat >> org.apache.lucene.codecs.PostingsFormat >> >> and org.apache.lucene.codecs.PostingsFormat file content diverges >> >> Lucene >> >> org.apache.lucene.codecs.lucene40.Lucene40PostingsFormat >> org.apache.lucene.codecs.lucene41.Lucene41PostingsFormat >> >> ElasticSearch >> >> org.elasticsearch.index.codec.postingsformat.BloomFilterPostingsFormat >> org.elasticsearch.index.codec.postingsformat.ElasticSearch090PostingsFormat >> org.elasticsearch.search.suggest.completion.Completion090PostingsFormat >> >> I'm using split-package / maven-shade but the result generated >> (merge-first, merge-last, first or last) does not allow to merge both >> files. Is there a trick/solution ? >> The pom file that I use to generate the elasticsearch bundle is available >> here : https://gist.github.com/8097375 >> >> Regards, >> >> -- >> Charles Moulliard >> Apache Committer / Architect @RedHat >> Twitter : @cmoulliard | Blog : http://cmoulliard.github.io --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
