Summary

Somewhat related to #11 , we should create a Maven Archetype and push it to the maven repo. This will allow users to quickly and efficiently get started with a new project without having to worry about the organization and formatting of their codebase.

We should think about what exactly is going to be created with this archetype. Should we create an archetype that provides similar purpose to what the example code base does? In this case, having a runnable example from the moment you create the new project with the archetype. Or, should we only worry about the package structure and some default files like the application.properties file?

I think open discussion is warranted regarding what we would like to see with the archetype.

Questions/Concerns

Should this archetype live with the Scaffold repo or should we create a new repo for this?
What should we include in the archetype?

A/C

Figure out what we'd like to see with the maven archetype
Do the work!
Update this A/C once the requirements have been figured out

kgress / scaffold

Create a maven archetype #6

Summary

Questions/Concerns

A/C