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.
> 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. - Cris > On Oct 8, 2021, at 4:53 AM, Bertrand Delacretaz <[email protected]> > wrote: > > Hi, > > On Fri, Oct 8, 2021 at 10:35 AM Robert Munteanu <[email protected]> wrote: >> ...Thanks for looking into this. We do have lots of archetypes, and >> technically all of them are supported, even the launchpad one... > > Technically yes, but in practice not really, until someone is willing > to spend time maintaining them. > > Shall we mark those archetypes as deprecated for now? > > It would make the situation clearer, that doesn't prevent people from > using them, and that status can be reverted if someone wants to work > on them later. > > -Bertrand
