i like the approach to have these infos in one place in each git repo, instead of a central file in some tooling repo.
i've no experience if the chosen file format (xml) and the given structure is the best, for me it's fine. i did not understand how the "aggregator" part is supposed to work - can each module define on or multiple "group memberships", and some other script picks up all modules subscribed to a certain group name to build a subset reactor pom and repo group? stefan >-----Original Message----- >From: Robert Munteanu [mailto:[email protected]] >Sent: Thursday, November 9, 2017 1:57 PM >To: [email protected] >Subject: Sling module descriptor for tooling automation > >Hi, > >For aiding with tooling automation I propose that we add a Sling module >descriptor for git repositories that need some special treatment. > >Note that this is only for usage from tooling, e.g. Jenkins, repo >scripts, and not intended to be used in any way at run time or even at >build time ( Maven ). > >The complete write-up is at > > https://cwiki.apache.org/confluence/display/SLING/Sling+module+descriptor > >Comments welcome, > >Thanks, > >Robert
