[ https://issues.apache.org/jira/browse/SLING-7314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Peltier updated SLING-7314: ----------------------------------- Fix Version/s: pipes 2.0.0 > 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 > Assignee: Nicolas Peltier > Fix For: pipes 2.0.0 > > > 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)