sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Honwai Wong (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SLING-7314) Dry run not working
Date Thu, 14 Dec 2017 16:21:00 GMT
Honwai Wong created SLING-7314:
----------------------------------

             Summary: Dry run not working
                 Key: SLING-7314
                 URL: https://issues.apache.org/jira/browse/SLING-7314
             Project: Sling
          Issue Type: Bug
          Components: Extensions
    Affects Versions: pipes 1.1.0
            Reporter: Honwai Wong


I worked with [~npeltier] to define a pipe to perform content migration, see below for an
example of this pipe:
{code}
def plumber = getService("org.apache.sling.pipes.Plumber");

plumber.newPipe(resourceResolver)
    .echo('/content/foo/bar').name('startPath')
    .mv('${path.startPath.replace("/bar", "/xyz")}')
    .parent().name('parentContent')
    .mkdir('${path.parentContent}/bar').with('nodeType', 'nt:unstructured').name('targetResource')
    .write('sling:resourceType', 'test/components/somecomponent')
    .echo('${path.parentContent}/xyz')
    .mv('${path.targetResource}/xyz')
    .runWith("dryRun", "true");
{code}

However, the {{dryRun}} argument is not taken into account, the changes are actually persisted
in the repository.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message