It's in branch-1.8. I left the commits in master so we can still use them to verify changes. Then porting commits to the 1.8 branch will be safer.
rb On Thu, Aug 4, 2016 at 10:34 AM, Sean Busbey <bus...@cloudera.com> wrote: > I pulled from the git repo last night to run through things again, but > I didn't see any revert. > > On Wed, Aug 3, 2016 at 2:36 PM, Sean Busbey <bus...@cloudera.com> wrote: > > sweet. I'll pull down an updated repo tonight and restart the run. > > > > On Wed, Aug 3, 2016 at 11:41 AM, Ryan Blue <rb...@netflix.com.invalid> > wrote: > >> Sorry about this, I ran into it the last time and forgot to fix the > problem. > >> > >> The addition of the dev-tools Java module (AVRO-1838) to run checkstyle > >> isn't compatible with our current script. I think the easiest thing to > do > >> is to revert the changes that added the module and instead patch the > >> original checkstyle rules. To get the 1.8.1 release out, I just reverted > >> the dev-tools module since it only affected the build. > >> > >> rb > >> > >> On Wed, Aug 3, 2016 at 6:55 AM, Sean Busbey <bus...@cloudera.com> > wrote: > >> > >>> This weekend I tried getting my ASF release machine to do a full > >>> build, in prep for a 1.8 RC. I followed the instructions in BUILD.txt > >>> to use docker to handle the dependencies. > >>> > >>> Once I was in the docker shell, I tried both `./build.sh test` and > >>> `./build.sh dist` and both failed while trying to build the java > >>> language libraries due to an unsatisfied dependency on > >>> org.apache.avro:dev-tools. > >>> > >>> Anyone know if this is more likely to be an error in my setup vs a gap > >>> in the build script? My intuition says gap in the build script, but I > >>> haven't had time to dig in at all. > >>> > >>> -- > >>> busbey > >>> > >> > >> > >> > >> -- > >> Ryan Blue > >> Software Engineer > >> Netflix > > > > > > > > -- > > busbey > > > > -- > busbey > -- Ryan Blue Software Engineer Netflix
