[GRADLE-1387] Gradle Archetypes Created: 13/Feb/11 Updated: 01/May/13 Resolved: 01/May/13 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | 1.7-rc-1 |
| Type: | Improvement | ||
| Reporter: | James R. Carr | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 17 |
| Description |
|
It'd be nice to have some way to publish and use something similar to maven archetypes. Perhaps something like this: gradle create http://www.example.com/some-archetype with perhaps some built in archetypes: gradle createWarProject Foo Just some ideas. I know this would save me a lot of typing/manually creating stuff (for now I have empty projects that I checkout from git and rename). Thanks, |
| Comments |
| Comment by Rajmahendra Hegde [ 01/Jun/11 ] |
|
My Suggestion is We can add this inside Gradle plugin like Java, Web etc. and when user types gradle createWarProject Foo It automatically creates. So any plugin you add to gradle will internally have all the setup. |
| Comment by Kelly Robinson [ 04/Oct/12 ] |
|
This project provides a script you can 'apply' to your build script which provides functionality for creating a variety of new projects easily: https://launchpad.net/gradle-templates |
| Comment by Adam Murdoch [ 01/May/13 ] |
|
Gradle 1.6 and 1.7 add some support for setting up a new Gradle build using the `build-setup` plugin. This initial support is very basic and we want to grow it in future releases, but I've marked this issue as 'fixed'. If you find problems or have suggestions for improvements to this build initialization support, please feel free to raise new issues via the forums. You can find out more about our plans in this design spec: https://github.com/gradle/gradle/blob/master/design-docs/build-initialisation.md |