> On Jan 16, 2017, at 11:49 AM, Jacob Barrett <jbarr...@pivotal.io> wrote: > > So you envision a world where someone who doesn't care about native clients > must build the native clients as part of the root gradle build and a person > not interested in building the Java bits must you gradle to build the > native clients? > > Both those scenarios don't sound great to me. As a developer only > interested in one of the component of project I really don't want to have > to build them all to get one. I would actually use that to echo Mark's > suggestion of a separate repo. Especially as a native developer I would not > want to have all the dependencies of server project in my environment just > to build native bits. Even worse would be requiring someone only interested > in the Java bits to meet all the dependencies of the native build. > > Am I misunderstanding what you are suggesting? > > On Mon, Jan 16, 2017 at 11:04 AM Anthony Baker <aba...@pivotal.io> wrote:
The reason why I want a single integrated build is to make it super simple for *anyone* to build the project. This is also useful for doing releases. I think that your suggestions about working patterns make sense and could be worked this approach. Of course, if we split this source into its own repo this discussion is moot. Anthony
