What would such a profile do though? In general building for a specific vendor version means setting hadoop.verison and/or yarn.version. Any hard-coded value is unlikely to match what a particular user needs. Setting protobuf versions and so on is already done by the generic profiles.
In a similar vein, I am not clear on why there's a mapr profile in the build. Its versions are about to be out of date and won't work with upcoming Hbase changes for example. (Elsewhere in the build I think it wouldn't hurt to clear out cloudera-specific profiles and releases too -- they're not in the pom but are in the distribution script. It's the vendor's problem.) This isn't any argument about being purist but just that I am not sure these are things that the project can meaningfully bother with. It makes sense to set vendor repos in the pom for convenience, and makes sense to run smoke tests in Jenkins against particular versions. $0.02 Sean On Mon, Aug 4, 2014 at 6:21 PM, Steve Nunez <snu...@hortonworks.com> wrote: > I don’t think there is an hwx profile, but there probably should be. > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
