Robert Munteanu created SLING-12773:
---------------------------------------
Summary: JCR Packageinit should always install SNAPSHOT packages
Key: SLING-12773
URL: https://issues.apache.org/jira/browse/SLING-12773
Project: Sling
Issue Type: Improvement
Components: JCR
Reporter: Robert Munteanu
The
[ExecutionPlanRepoInitializer|https://github.com/apache/sling-org-apache-sling-jcr-packageinit/blob/master/src/main/java/org/apache/sling/jcr/packageinit/impl/ExecutionPlanRepoInitializer.java]
iterates through the defined executions plans and checks that based on
checksums that the packages were not previously installed (
https://github.com/apache/sling-org-apache-sling-jcr-packageinit/blob/2421b2b4af64d2cef34c35b5c070c266e58f6abb/src/main/java/org/apache/sling/jcr/packageinit/impl/ExecutionPlanRepoInitializer.java#L118-L121
).
The hashes are based on the hashCode of the string format of the ExecutionPlan
- see how the configuration gets built at
https://github.com/apache/sling-org-apache-sling-feature-extension-content/blob/520387ec3ebcb519e08e4504ff56d5c4cd533fd4/src/main/java/org/apache/sling/feature/extension/content/ContentHandler.java#L117-L122
.
This has the unfortunate side effect of not reinstalling SNAPSHOT content
packages, which happens quite often during development.
I think the package init component should check the execution plan and, if a
SNAPSHOT version is found, always consider it for execution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
