+1 Is the plan to have them be part of every build or to use an optional build profile? I’m partial to the latter; that said, I could see the argument wanting whatever the clean install is to be how we build and test for an Apache release since we will now need those to be voted on for every release.
-joey On Jan 8, 2018, 1:44 PM -0700, Trevor Grant <trevor.d.gr...@gmail.com>, wrote: > +1 > > On Mon, Jan 8, 2018 at 2:27 PM, Suneel Marthi <smar...@apache.org> wrote: > > > +1 > > > > On Mon, Jan 8, 2018 at 3:26 PM, Steve Blackmon <sblack...@apache.org > > wrote: > > > > > I’d like to discuss consolidating apache/streams-examples into > > > apache/streams under a new top-level module ‘examples’. > > > > > > We had some good reasons for keeping them isolated during incubation, but > > > I’ve come around to the perspective that the significant simplification > > to > > > our setup, test, CI, website publish, and release processes we would get > > by > > > merging them in would outweigh all of the benefits of keeping them apart. > > > > > > Also I think the negatives of having the examples reside inside the > > project > > > can largely be mitigated by adding a new profile that shades and > > > integration tests the examples but is disabled by default. > > > > > > Lastly, given that Flink, Kafka, and Spark are all getting by with their > > > examples hosted inside their primary SCM, I see no reason Streams > > couldn’t > > > do the same > > > > > > Any +1 or alternative perspectives on the matter? > > > > > > Steve > > > > >
