Have you seen any successful applications of this for Spark 1.x/2.x? >From the doc "The classifier allows to distinguish artifacts that were built from the same POM but differ in their content."
We'd be building from different POMs, since we'd be modifying the Spark dependency version (and presumably any other dependencies that needed the same Spark 1.x/2.x distinction). On Wed, Aug 24, 2016 at 11:49 AM, Sean Owen <so...@cloudera.com> wrote: > This is also what "classifiers" are for in Maven, to have variations > on one artifact and version. https://maven.apache.org/pom.html > > It has been used to ship code for Hadoop 1 vs 2 APIs. > > In a way it's the same idea as Scala's "_2.xx" naming convention, with > a less unfortunate implementation. > > > On Wed, Aug 24, 2016 at 5:41 PM, Michael Heuer <heue...@gmail.com> wrote: > > Hello, > > > > We're a project downstream of Spark and need to provide separate > artifacts > > for Spark 1.x and Spark 2.x. Has any convention been established or even > > proposed for artifact names and/or qualifiers? > > > > We are currently thinking > > > > org.bdgenomics.adam:adam-{core,apis,cli}_2.1[0,1] for Spark 1.x and > Scala > > 2.10 & 2.11 > > > > and > > > > org.bdgenomics.adam:adam-{core,apis,cli}-spark2_2.1[0,1] for Spark 1.x > and > > Scala 2.10 & 2.11 > > > > https://github.com/bigdatagenomics/adam/issues/1093 > > > > > > Thanks in advance, > > > > michael >
