My Google-foo is off today, since I can't find anything relevant on this
subject:

Let's say I have a project based on Sling 11 (provisioning files, not
features). Version 1 contains artifact1, artifact2, and artifact3.
Version 2 contains artifact1, artifact3, and artifact4. All these
artifacts have some Sling-Initial-Content that should be installed in
the repository. Additionally, v1 of artifact3 has some nodes that are no
longer present in v2. Right now, when upgrading between v1 and v2:

- artifact2 is still present, although it is not declared in the v2
provisioning file
- old nodes present in v1 of artifact3 are still present

Any suggestions for how to get artifact2 removed automatically during
the upgrade?

Any suggestions for getting stale nodes removed from artifact3 during
the upgrade? I know that by putting all content in a node that should be
removed and reinstalled (overwrite:=true in the Sling-Initial-Content
entry), but the path where the nodes need to be installed in is shared
with other artifacts, so removing the whole parent node is not an easy
option.

Thank you,
Sergiu

Reply via email to