sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-8523) Duplicate OSGI configs after upgrade
Date Fri, 21 Jun 2019 13:00:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869450#comment-16869450
] 

Carsten Ziegeler commented on SLING-8523:
-----------------------------------------

[~ashokpanghal] Thanks for the patch. A couple of comments:
- it would be good to have some unit tests verifying that the cases you're experiencing are
handled
- detecting a factory configuration by looking for a dash in the ID is good. I think the ID
could be further down used in that case to get the pieces. The part before the dash is definitely
the factory id; it then depends on what is after the dash and how we can derive the PID from
it. For this the test cases would be helpful to see how the value of the ID exactly looks

> Duplicate OSGI configs after upgrade
> ------------------------------------
>
>                 Key: SLING-8523
>                 URL: https://issues.apache.org/jira/browse/SLING-8523
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>            Reporter: Ashok Kumar
>            Priority: Critical
>         Attachments: image-2019-06-20-15-29-56-200.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> upgrade is resulting in duplicate factory configurations (configuration with .PID versus
~PID format) files which affect the configs related functionality. It happens for odd cases
where alias comes as null.
> Linked issue - SLING-7786



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message