On Monday 06 November 2017 08:22:45 Radu Cotescu wrote: > Hello, Hi Radu,
> After using the Sling Aggregator [0] to clone all modules I was wondering > if somebody else missed the previous "functional" structure of the modules > or not. While I fully support the 1 module / SCM repository code > organisation, I think that sometimes it's beneficial to have a reactor that > would build all related modules with one command. > > I would not use these reactors in any CI jobs, but rather use them locally, > for quickly testing changes that span across multiple modules. > > WDYT? you can set up your own reactor/aggregator/builder projects, e.g. search for sling in my GitHub repos: https://github.com/oliverlietz?tab=repositories&q=sling But we should have some basic reactors ("core", commons, scripting, models, validation, ...) for convenience anyway. Regards, O. > Cheers, > Radu > > [0] - https://github.com/apache/sling-aggregator
