I create the repositories (including the slingfeature-maven-plugin). regards,
Karl On Thu, Apr 26, 2018 at 8:34 PM, Carsten Ziegeler <[email protected]> wrote: > Sounds good to me, sling-slingfeature-maven-plugin sounds like a good > name as well. As we'll need a plugin at some point, I think it makes > sense to create it now already > > Regards > > Carsten > > David Bosschaert wrote >> Hi all, >> >> Thanks all for supporting the idea! >> >> I would propose the following Git repository names: >> >>> * feature - The Feature Model API >> sling-org-apache-sling-feature >> >>> * feature-analyser - Analyser Module for Features >> sling-org-apache-sling-feature-analyser >> >>> * feature-applicationbuilder - Command line tool for building >> Applications from Features >> sling-org-apache-sling-feature-applicationbuilder >> >>> * feature-io - Deals with reading and writing features to disk >> sling-org-apache-sling-feature-io >> >>> * feature-karaf - Turn Features into Karaf Features >> sling-org-apache-sling-feature-karaf >> >>> * feature-launch - Launch a Feature-based application >> sling-org-apache-sling-feature-launcher >> >>> * feature-modelconverter - Convert between Features and the Sling >> Provisioning Model >> sling-org-apache-sling-feature-modelconverter >> >>> * feature-resolver - Resolve Features and contents, can compute ordering >> sling-org-apache-sling-feature-resolver >> >>> * osgifeature-maven-plugin - Similar to slingstart-maven-plugin but then >> for features (maybe this one should be renamed, e.g. >> slingfeature-maven-plugin?) >> So I would suggest to go for sling-slingfeature-maven-plugin but if this >> needs additional discussion we can postpone this one for now I guess. >> >> Since I'm not a PMC member I can't perform this task, but Karl Pauls has >> kindly offered help here. (Thanks Karl!) >> >> Thoughts anyone? >> >> Best regards, >> >> David >> > -- > Carsten Ziegeler > Adobe Research Switzerland > [email protected] -- Karl Pauls [email protected]
