just to provide an alternative, maybe one that needs a new thread, is there a reason that a version-info-plugin in Yetus is a better idea than trying to get it into the Maven project itself?
On Fri, Aug 28, 2015 at 10:09 AM, Sean Busbey <bus...@cloudera.com> wrote: > How about the Version-Info maven plugin? > > > https://github.com/apache/hadoop/blob/trunk/hadoop-maven-plugins//src/main/java/org/apache/hadoop/maven/plugin/versioninfo/VersionInfoMojo.java > > It seems generally useful outside of Hadoop and it helps projects be > specific when referencing their versions in other places (like if we add a > maven plugin that runs releasedocmaker, or when building their api docs). > > On Thu, Aug 27, 2015 at 3:53 PM, Allen Wittenauer <a...@altiscale.com> > wrote: > >> >> On Aug 27, 2015, at 8:21 AM, Sean Busbey <bus...@cloudera.com> wrote: >> > >> > Allen, you've been chugging away at the build support changes in >> > test-patch[4]. That looks like it's going to change a bunch of stuff. >> > Should we wait for it to land to have an initial release? >> >> I think so, yes. It’s getting very very close to finished. >> Adding gradle & scala support requires a lot of deep changes with some >> major API changes to go with them. I’d rather get those in sooner rather >> than later, since those changes open the door to add even more build tools >> and compiled language support in a much easier fashion. >> >> > Thoughts? Concerns? Other things folks want to make sure get done? Maybe >> > the build question for test-patch[5]? ;) >> >> HADOOP-12298 is definitely a blocker. Otherwise builds break and >> the output is weird with mvn site. >> >> > > > -- > Sean > -- Sean
