I am far from being a maven expert and I also may not understand your requirements. However, as far as the avro-mapred jar goes, I am able to get the one I want in my projects by using something like
<dependency> <groupId>org.apache.avro</groupId> <artifactId>avro-mapred</artifactId> <version>1.7.3</version> <classifier>hadoop2</classifier> </dependency> If all your users need is the ability to get the correct version (hadoop1 vs hadoop2) of hbase jars for their projects, I imagine doing it the same way as avro-mapred should work. But please consult your maven experts. On Fri, Mar 29, 2013 at 12:23 PM, Stack <[email protected]> wrote: > On Fri, Mar 29, 2013 at 11:41 AM, Wing Yew Poon <[email protected]> wrote: > >> Stack, >> you could take a look at >> >> http://svn.apache.org/repos/asf/avro/tags/release-1.7.3/lang/java/mapred/pom.xml >> to see how they do it with classifiers. > > > Thank you for the pointer Wing Yew. > > In the cited pom, the classifier is appended to the generated jar and that > is it. > > We want everything to carry the hadoop? label including published poms as > well as published jars so that in the downstream pom, they can explicitly > say what hbase-client they want .. the one that was built against hadoop2 > (At least, that is my understanding). > > Thanks, > St.Ack
