sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-8113) Set statusfilepath of package-init to registryHome via content-extension
Date Fri, 16 Nov 2018 13:52:00 GMT

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

ASF GitHub Bot commented on SLING-8113:
---------------------------------------

DominikSuess opened a new pull request #10: SLING-8113 - defining file in registryhome to
capture executionplan s…
URL: https://github.com/apache/sling-org-apache-sling-feature-extension-content/pull/10
 
 
   …tatus.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Set statusfilepath of package-init to registryHome via content-extension
> ------------------------------------------------------------------------
>
>                 Key: SLING-8113
>                 URL: https://issues.apache.org/jira/browse/SLING-8113
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Dominik Süß
>            Assignee: Dominik Süß
>            Priority: Major
>
> The statusfile of packageinit by default is persisted in the bundledata repository to
be  by default agnostic of the filesystem structures. Anyhow in case of usage along with content-extension
the registry home is already declared and is in contrast to the framework not supposed to
be rebuilt and therfore a more reliable location to store. As the content-extension already
generates the configuration for this service this is an easy addition to persist the statusfile
in the packageregistries home directory.



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

Mime
View raw message