You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (Jira)" <ji...@apache.org> on 2020/01/21 12:15:00 UTC
[jira] [Resolved] (SLING-9015) RepositoryInitializerFactory fails
with non-null but empty references or scripts
[ https://issues.apache.org/jira/browse/SLING-9015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved SLING-9015.
----------------------------------------
Resolution: Fixed
Fixed at commit [d07f175296|https://github.com/apache/sling-org-apache-sling-jcr-repoinit/commit/d07f175296127c8448aaf930385baf9cdbeada4c], also added integration tests for the {{RepositoryInitializerFactory}}.
> RepositoryInitializerFactory fails with non-null but empty references or scripts
> --------------------------------------------------------------------------------
>
> Key: SLING-9015
> URL: https://issues.apache.org/jira/browse/SLING-9015
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
> Affects Versions: Repoinit JCR 1.1.16
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: Repoinit JCR 1.1.18
>
>
> By default, the OSGi webconsole will provide an empty but non-null "references" or "scripts" value if entering only the other value, which breaks the checks in {{RepositoryInitializerFactory.processRepository()}}
> Not a big problem but confusing when using that feature from the webconsole.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)