give users an option to use Gradle vs Maven

[stevehu]

buildMaven is the parameter in the config.json or config.yaml to control if Maven is used or Gradle is used. The default is false which means the Gradle is the default.

[stevehu]

give users an option to use Gradle vs Maven light-codegen master

[PeterKieu]

Thanks for the grable build option.
However, I checked out the new codegen and give a try (cli + rest) but the default build is still maven, not gradle:
java -jar ./codegen-cli.jar -f openapi -o $OUTPUT -m $MODEL_OPENAPI -c $CONFIG

I am traveling the source code to find more.
I faced many issues when building with gradle, specially with Kafka libs, then I want to share on gradle Rock templates.

[PeterKieu]

Sorry. I used the Release branch while gradle is not the Master.
But another thing shows off: Many sub projects are generated for expected one-rest-project.
include("model", "service", "client", "server") we have 4 sub projects.

I think that the tool should generate gradle project similar to maven (source code, resources), only change the build script from mvn (POM) to gradle scripts.

[stevehu]

We are going to generate multiple modules for the project as this is required by our customers. The model can be shared by both server and client. The service is what developers want to focus on.

[PeterKieu]

Oh, that is the point! We share models and asign services to team members.