I created two Sling Maven Archetypes: 1. Project
Creates a Content Package (ui.apps) that contains a Bundle (core) as embedded object using wcmio content manager maven plugin to deploy. The ticket tor that is here: https://issues.apache.org/jira/browse/SLING-7276 <https://issues.apache.org/jira/browse/SLING-7276> 1. Project-All Creates a Content Package (all) that wraps an Content Package (ui.apps) and a Bundle (core) as sub project and embedded object and then deployed by the wcmio content manager maven plugin. This is the ticket for this: https://issues.apache.org/jira/browse/SLING-7277 Let me know what you think and what can be done to improve it. Cheers - Andreas Schaefer > On Nov 28, 2017, at 8:18 AM, Konrad Windszus <[email protected]> wrote: > > Just create a new repo inside your personal Github space. Then create the > JIRA and link the repo there. > Then it should be easy to clone and also push it to a decicated Sling Repo > (once that is created). > > Konrad >> On 28. Nov 2017, at 17:16, Bertrand Delacretaz <[email protected]> >> wrote: >> >> Hi, >> >> On Tue, Nov 28, 2017 at 5:10 PM, Andreas Schaefer <[email protected]> wrote: >>> ...What is the best way to create a PR for Sling for a non-committer >>> when I want to add a new module?... >> >> I don't think you can do that if those new modules are going into new >> Git repositories (which is our usual plan now). >> >> Best is probably to attach the code as an archive to a jira ticket. >> >> -Bertrand >
