| commit | d8ad58fce79279062bb3dd6b06e6a48e6164d7c0 | [log] [tgz] |
|---|---|---|
| author | Robert Munteanu <rombert@apache.org> | Tue Sep 19 22:27:13 2023 +0200 |
| committer | Robert Munteanu <robert.munteanu@gmail.com> | Wed Sep 20 00:13:11 2023 +0200 |
| tree | 6f546245cb8fcb987521c05b94379f3e5f7acc9d | |
| parent | 928a42af7935c56a016210f17f04572a9e3d8714 [diff] |
SLING-12028 - Content Deployment Extension tests fail on Windows Use a File.separator instead of hardcoding '/' . The assumption of the content extension is that generated plans will pe processed on the same operating system, so we don't care too much about now about cross-platform compatiblity, i.e. run the extension on Windows and then deploy on Linux.
This module is part of the Apache Sling project.
This module extends the Sling Featuremodel Launcher with content package capabilities. The format of the extension is described in Extension Content-Packages.
To influence the package installation order the following format must be used
"content-packages:ARTIFACTS|required":[
"id":"org.apache.sling.myapp:my-content-package:zip:1.0.0"
"start-order": 1
]
The default start order is the maximum integer value (i.e. the package is processed after all packages with an explicit start-order).
All content-packages from the model are registered (externally) in a FSPackageRegistry and scheduled for installation with execution plans (given via OSGi configuration) which automatically get executed during repository start by ExecutionPlanRepoInitializer