+1 The only reason I have my custom sling launchpad jar (without including project related bundles) is to include Composum in the launchpad at the moment :)
Greets Roy > On 21 Nov 2016, at 11:12, Robert Munteanu <[email protected]> wrote: > > Hi, > > With the default Sling launchpad we're still shipping the content > explorer from bundles/extensions/explorer. While this has the benefit > of being available as a basic tool, it's pretty buggy and unmaintained > - last 'non-administrative' commit was in Feb 2012 . > > I think it's time to retire this explorer to the attic and look for > other options. > > I for one have been using Composum [1] with good results for some > months. The resource explorer part is very good, and it also has other > extras such as an ACL editor, user/group management and an interface > for content package management. It is licensed under the MIT license, > so we're clear here. > > We also have an explorer under contrib/explorers/resourceeditor, but > it's still under contrib and though I like the approach it takes to > designing and composing the frontend, my impression is that it's not > yet ready to be moved to the main build and included in the launchpad. > Of course, feel free to disagree :-) > > So my proposals would be: > > 1) Remove the "old" explorer from the launchpad > 2) Move the "old" explorer to the attic > 3) Include composum in the launchpad > > Thoughts? > > Thanks, > > Robert > > > [1]: https://github.com/ist-dresden/composum
