This release is an attempt to mitigate common issues related to development life-cycle phases such as testing, the running of application and deployment in various environments. The archetype leverages upon the flexible building process and on the top-most featured IoC (Inversion of Control) management system.
When creating application modules for linking services through HTTP, JMS or any other connector type, this archetype is refined and can be applied for satisfying these requirements:
- Automatic testing, building and continuous integration.
- A different configuration for each environment (development, integration, production).
- Springframework based system.
- Groovy support.
The project consists of:
- Utility classes for given Spring context.
- Grails-like DSL for Spring setup (beans.groovy).
- Logging and application configuration properties for each environment (development/integration/production).
- Gradle config file.
Problems exist using Maven in Groovy projects due to the gmaven plugin, which may indicate that it is not ready for the groovy-user community. Indeed, Gradle works perfectly on Groovy projects. It is so concise and elastic that you don?t have just a building system, you have a programming tool. When a customized behaviours proper plugin cannot be found in the registry, you may add custom tasks by writing groovy code directly to the build.gradle descriptor. Gradle is a swiss army knife for developers.
git clone email@example.com:gfrison/proto-app.git myApp
where myApp is the name of your project.
- Edit property ?projectName? in ?build.gradle? with project name.
- Add classes, and manage them with spring ?beans.groovy?.
- You are now ready to test, run and deploy your project through a continuous integration system such as Jenkins.
If you have suggestions, or pull requests from Github, myself the author, would be happy to consider them.