> On Apr 3, 2019, at 2:18 PM, Mike Billman <mikebill...@qcsoftware.com> wrote: > > Figured out what was causing this...conflicting files. At one point, we had > a build.gradle file in the same directory so that a gradle command could be > issue to build the webui into our local environment. That is no longer > needed, so I deleted that file and it behaves as I would expect it. >
This is pointing out a general issue I’d like to focus on at some point “fairly” soon in NB which is the ability to blend builds and projects. As an example, Gradle is a build tool, not just Java specific, and as such one can use it for Angular projects with Gradle plugins which will make sure the proper Node and NPM etc are setup and installed in a special cached way to allow for easier consistent builds with nothing more than a JDK and a Gradle wrapper. This is super handy; both for QA and backend devs to work together with front-end folks. Of course then, one needs to be able to work on both the Node and Gradle projects; blended. This project structure can include C++ and even Python. We are currently blending Gradle and Python, but at some point will also have Angular & Node in the mix. This is a similar usage in the DotNet world to using Cake as a general purpose build tool. Wade
