You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2014/09/09 11:56:28 UTC

[jira] [Commented] (SLING-3828) Hardcoded creation of SegmentNodeStoreService config makes it impossible to remove this configuration

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

Stefan Seifert commented on SLING-3828:
---------------------------------------

in this rev. these lines from {{launchpad/builder/pom.xml}} were removed:
{code:xml}
        <!-- trick maven-launchpad-plugin into not copying any configs -->
        <empty.config.directory>${project.build.directory}/NOCONFIGS</empty.config.directory>
{code}

why? because of this on every build an empty directory named (literally)
{noformat}${empty.config.directory}{noformat}
is created.

the line was added by betrant in context of SLING-3155 (rev. Revision: 1533101). if it is no longer required the corresponding {{maven-antrun-plugin}} should be removed as well.

> Hardcoded creation of SegmentNodeStoreService config makes it impossible to remove this configuration
> -----------------------------------------------------------------------------------------------------
>
>                 Key: SLING-3828
>                 URL: https://issues.apache.org/jira/browse/SLING-3828
>             Project: Sling
>          Issue Type: Bug
>          Components: Oak
>            Reporter: David Bosschaert
>            Assignee: Carsten Ziegeler
>             Fix For: Launchpad Builder 7, JCR Oak Server 1.0.0
>
>         Attachments: oak-server.diff
>
>
> The Activator in org.apache.sling.jcr.oak.server always creates a configuration item with PID org.apache.jackrabbit.oak.plugins.segment.SegmentNodeStoreService if it isn't there. This means that if you delete this configuration, it will reappear on restart.
> In some cases this configuration is undesirable, for example when running with Mongo. Therefore it should be possible to delete it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)