[
https://issues.apache.org/jira/browse/SLING-12353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-12353:
------------------------------------
Description:
Consider the following scenario:
1. In feature A, the analyser-metadata extension is configured with:
{code}
{
"analyser-metadata:JSON|true":
{
"org.apache.sling:org.apache.sling.api:2.0.6" : {
"manifest": null,
"report": {
"error": false,
"warning": false
}
}
}
{code}
2. During aggregation, feature A is processed with the analyser-metadata
extension, resulting in feature B.
This will result in a the "report" key being retained but not the manifest.
3. At a later point, feature B is aggregated again, resulting in feature C.
During the aggregation process, the manifest will be cached because the
{{"manifest": null}} key was not preserved during the first aggregation. This
is unexpected and should be fixed.
> AnalyserMetadataHandler should record that manifest caching was skipped for
> subsequent runs
> -------------------------------------------------------------------------------------------
>
> Key: SLING-12353
> URL: https://issues.apache.org/jira/browse/SLING-12353
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model Analyser
> Reporter: Robert Munteanu
> Priority: Major
> Fix For: Feature Model Analyser 2.0.8
>
>
> Consider the following scenario:
> 1. In feature A, the analyser-metadata extension is configured with:
> {code}
> {
> "analyser-metadata:JSON|true":
> {
> "org.apache.sling:org.apache.sling.api:2.0.6" : {
> "manifest": null,
> "report": {
> "error": false,
> "warning": false
> }
> }
> }
> {code}
> 2. During aggregation, feature A is processed with the analyser-metadata
> extension, resulting in feature B.
> This will result in a the "report" key being retained but not the manifest.
> 3. At a later point, feature B is aggregated again, resulting in feature C.
> During the aggregation process, the manifest will be cached because the
> {{"manifest": null}} key was not preserved during the first aggregation. This
> is unexpected and should be fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
