Project folder structure

I would like to propose we follow more closely the project structure Spark is using, where we clearly define a folder for samples, another for dev utilities, etc instead of getting everything buried inside the /scripts folder where it might be confusing/hard for users to find what they are

Re: Project folder structure

On Tue, Feb 9, 2016 at 12:43 PM, Matthias Boehm wrote: > -1 > > I don't see a compelling argument for this unnecessary change to a more > complex project structure just to follow Spark which is not directly > comparable - both in project size and content. For example, our

Re: Project folder structure

On Tue, Feb 9, 2016 at 1:25 PM, Niketan Pansare wrote: > -1 for changing the folder structure. I don't think the current setup is > confusing for the end user and also agree with Matthias that our project > structure does not have to be in sync with Spark. > +1 for having

Re: Project folder structure

With regards to DML and PyDML, the test scripts are in src/test/scripts, so something similar in main (src/main/scripts) may have some good points to it. I've used Maven for a long time so personally I'm biased towards Maven's "convention over configuration" paradigm. However, at the same time it

Re: Project folder structure

I would advise not making significant project structure changes unless absolutely required. Regarding release.sh, I think we can find a good place for it without a major overhaul of the project structure. I don't have a strong opinion on any particular location (be it dev or scripts or something