To add more to what Anton said, the 'mvn clean verify' step takes hours and fails frequently due to bad tests. I spent the first few days working with beam trying to figure out what was wrong with my system when I was just hitting test flaps. If we're going to gradle that would be a great place to update. If not, adding directions on how to skip the tests in maven and just run the build would be good too.
Andrew On Wed, Mar 14, 2018 at 11:54 AM Anton Kedin <[email protected]> wrote: > Not sure if it was mentioned in other threads, but it probably makes sense > to add gradle instructions there. > > > On Wed, Mar 14, 2018 at 11:48 AM Alan Myrvold <[email protected]> wrote: > >> There is a contribution guide at >> https://beam.apache.org/contribute/contribution-guide/ >> Has anyone had challenges / pain points when getting started with new >> contributions? >> Any suggestions for making this better? >> >> Alan >> >
