Hi Robert I know I dropped the ball here but the entire Feature Model thing on Sling is still developing.
I assume from the post that Sling 12 is still a good old fashioned PM based release which is fine for me. So a FM based ’super archetype’ is not really going to work as long as Sling is not supporting FMs OOTB. That said as far as I know the Sling Project Archetype should work with Sling 12 but the dependencies might need to be updated but that should be an easy fix as soon as the PMs are frozen. Let me know when you want to start that process and I will squeeze in the update of the Archetype. Cheers - Andy > On May 7, 2020, at 8:57 AM, Robert Munteanu <[email protected]> wrote: > > Hi, > > We had several discussions related archetypes and content-packages > [1],[2], [3]. I was personally very enthusiastic about reorganising the > Sling archetypes and converging on the sling-project-archetype. > > However, it seems that there was no movement in that direction, and I > did not find the time to invest in retiring the other archetypes. > > As "perfect is the enemy of good", I'd like to propose that for Sling > 12 we create a simple content-project Maven archetype, in the spirit of > the other Maven archeypes. This would make the 'content-package based > development' theme [4] complete for Sling 12, which can only be a good > thing. > > Then, for lucky Sling 13, we can focus on getting a polished Sling > Project archetype ready. > > Thoughts? > > Thanks, > Robert > > [1]: https://issues.apache.org/jira/browse/SLING-6203 > [2]: > https://lists.apache.org/thread.html/1fc520167471cb264f5cae7f590d0adddcaa45fe4fa8be8984e5bf2a%40%3Cdev.sling.apache.org%3E > [3]: > https://lists.apache.org/thread.html/048c181ae57fff8be79f17aa3c7f33fe999d90f81dc431710726b62c%40%3Cdev.sling.apache.org%3E > [4]: https://issues.apache.org/jira/browse/SLING-6950 >
