2014-09-29 10:46 GMT+02:00 Bertrand Delacretaz <[email protected]>:
> On Sat, Sep 27, 2014 at 5:49 PM, Carsten Ziegeler <[email protected]> > wrote: > > 2014-09-27 13:23 GMT+02:00 Oliver Lietz <[email protected]>: > >> ...is the common model able to represent such dependencies > >> between subsystems/features? > >> > > Not directly right now, the question is what is missing? A feature can > > define configurations, these can be special configurations (starting > with a > > colon) and we could use this to specify the information... > > Might be cleaner to have a dedicated "requires" attribute on the > instance model's features? > Maybe, if we just have a single use case which we can solve with the special configs, than I would rather go that route. But let's look at what exactly needs to be specified? > > Also makes me thing that Sling features should have maven coordinates, > a unique name and a version? > I don't think this is part of the model. This can be done by whatever tooling is processing it. For example for a maven project, the maven coordinates are already there and the run mode could be used the qualifier to promote the artifacts. Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
