- currently there are lots of sling maven archetypes, and most of them not well maintained - we would favor to have only one single "project" archetypes, probably the new "project" archetype contributed by andy - add parameters to switch features on and off, e.g. for generating only with bundle but not with the content packages - this can be done using the groovy prost process - there is already a groovy script with a lot of logic in it, to be reviewed if it already covers all use cases - the plan is to no longer have the need to maintain multiple archetypes - review the generated structure of the current project archetypes. the structure is derived from the adobe AEM project archetype, but we like not all of it. e.g. the "ui." prefix for the contant packages, probably introduce "bundles" and "content-packages" folders to but bundles and content packages in.
stefan
