Hi team Looking at the Project Archetype I see that I did not add support for FMs. So I was wondering if that would be something you might be interested. I was thinking to keep the current code / layout around with Bundle and Content Package(s) but add support for FMs and FARs.
This would require: - Add a ‘far’ module that creates a FM and FAR like the All does - Migrate the rest to be able to generate FMs and convert if needed - Added a Bundle Content Module for the traditional and FM version - Use the post processing to remove unwanted modules or parts of them - Use kickstart to test the deployment of the FM / FAR module Cheers - Andy > On Oct 8, 2021, at 12:34 PM, Andreas Schaefer <[email protected]> > wrote: > > Hi > > I did not work on the Project Archetype for a while but I am going to have a > look into it with respect to FMs. > There were some suggestions on how to improve it a while back and I will try > to find them again. > > Cheers - Andy > >> On Oct 8, 2021, at 8:01 AM, Robert Munteanu <[email protected]> wrote: >> >> On Fri, 2021-10-08 at 08:44 -0400, Cris Rockwell wrote: >>> Hi >>> >>>> Shall we mark those archetypes as deprecated for now? >>> Yes. I can make that update to the site (if no one objects). It makes >>> sense to deprecate broken archetypes, at least temporarily. These >>> provide an initial starting point for developers looking to try the >>> framework, so I think they should not only work properly but also >>> have good documentation if possible. I also understand resource >>> constraints. >> >> +1 from me. >>> >>> >>>> I would be in favour of just maintaing the sling-project-archetype >>>> and >>>> making sure that a) it works and b) is a reasonable starting point >>>> for >>>> Sling-based apps. >>> >>> FYI. I used sling-project-archetype two days ago. It worked well for >>> me. It provided a reasonable starting basis for my new project. >> >> Good to know, thanks. >> Robert >
