Hi Dan,
Makes sense. Based on this response, I'm thinking that most likely if you were to create a Sling-based application you would not use the Sling Starter as a prototype for a couple reasons. First, you wouldn't want to be tied to Sling Starter's releases and secondly Starter has a relatively opinionated configuration and requires a fair number of removals for extension.
Right, it might make sense to use the starter feature model to get something up and running quickly. But then you have to live with the decisions made their. So agreed, its better to not use it as a base.
Based on that, it feels like once we transition to feature model, it would make a lot of sense to create a number of feature projects for common Sling sub-module groups, such as repoinit, composum, oak, etc so that implementers of Sling can pull those features rather than defining everything from scratch.
Yes, right, I think we said that we transition to these smaller feature models - and the starter will aggregate and enhance those.
Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
