don't make people think about how to setup/install

[xquery]

I think we need a top level entry point for building the various aspects of the project ... making people spend any additional time thinking (even if its just hunting in nested dirs) will reduce the 'first five minutes' impression.

Whats stopping us from providing top level gradle (or bash, or ) for building which makes an opinionated decision about a default setup ?

[laurelnaiad]

Today, the entry point for a developer who only wants to work in gradle/java is in the java-spring directory. A "built" copy of the browser app is always hosted on port 8090. I don't know if you knew that -- if not, we should probably document it better.

Conversely, I did some work with gradle early on to drive the javascript build. It is possible, either with a gradle-node plugin or using manual interprocess communication. (bash is a no go unless it were mirrored with a windows shell version.)

When you say "makes an opinionated decision about a default setup," I'm not sure I understand. Do you mean, "as to whether or not I am a browser developer and a middle tier developer?" The only thing that isn't pre-configured is that you get to choose whether you want to dig into the browser development or not. Everything else should be configured out of the box (after dependencies are installed).

[laurelnaiad]

Let's put a priority tag on this so bugtrack is happy.