infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-13644) path added to extpaths.txt still taken into account in publish diffs
Date Mon, 13 Mar 2017 04:12:04 GMT

     [ https://issues.apache.org/jira/browse/INFRA-13644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Lambertus updated INFRA-13644:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

>From the documentation https://www.apache.org/dev/cmsref.html#extpaths it suggests that
'components' will be persisted even when deleted from the site source tree. I wonder if the
path needs to be 'content/components' in extpaths.txt for this to work, based on the diff
output?



> path added to extpaths.txt still taken into account in publish diffs
> --------------------------------------------------------------------
>
>                 Key: INFRA-13644
>                 URL: https://issues.apache.org/jira/browse/INFRA-13644
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: CMS
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>         Attachments: diffs.txt
>
>
> An extpaths.txt file was added to the Sling content source tree [1] recently.
> The site diffs shown on the site publishing page [2] now report the deletion of lots
of files under that path, which makes it hard to understand what actually changed.
> Do we have something wrong in our site setup, or is that a CMS bug? And in the latter
case is there another way to get reliable diffs before publishing changes?
> [1] https://svn.apache.org/repos/asf/sling/site/trunk/content/extpaths.txt
> [2] https://cms.apache.org/sling/publish?diff=1



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message