While these are similar concerns, they are different - the symlink stuff (yes, I use the shorter name) creates a new tree based on an existing one and this can be overwritten/changed. The merging approach merges two (or more resources) into a single one - again using a new sub tree.
Not quiet the same - but we might be able to share code / functionality Carsten 2013/9/27 Julian Sedding <[email protected]> > Hi Betrand > > Agreed. I took a quick glimpse at the code for SLING-2986. My > impression is, that the two contributions should be largely > complementary. > > The focus of SLING-1778 is currently about "mounting" existing > resource (sub-)trees to arbitrary locations in the resource tree. The > merging aspect is currently on per-node granularity (IIRC). In > SLING-2986, the merging aspect seems to have been the main focus (e.g. > sling:hideProperties etc.). > > Regards > Julian > > On Fri, Sep 27, 2013 at 9:40 AM, Bertrand Delacretaz > <[email protected]> wrote: > > Hi, > > > > With SLING-1778 and SLING-2986 we have two contributions that allow > > for partial merging/shadowing of resources. > > > > I haven't looked at the code in detail yet but it looks like a single > > extension should cover both use cases. > > > > IIUC, both are about about taking into account another resource B when > > looking at resource A, and using B as a default tree for A, optionally > > overridable. > > > > WDYT? > > > > (let's discuss the name of that feature in a separate thread once we > > agree on how to tackle it) > > > > -Bertrand > -- Carsten Ziegeler [email protected]
