[jira] [Commented] (INFRA-5534) extpaths.txt content should not lead to error when publishing if the dirs don't exist yet

["#asfinfra IRC Bot (JIRA)" <ji...@apache.org>]

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

#asfinfra IRC Bot commented on INFRA-5534:
------------------------------------------

<danielsh> Nope.  If the dirs don't exist, omit them from extpaths.txt.  Anything else would be a _silent_ failure mode, we don't want that.

                
> extpaths.txt content should not lead to error when publishing if the dirs don't exist yet
> -----------------------------------------------------------------------------------------
>
>                 Key: INFRA-5534
>                 URL: https://issues.apache.org/jira/browse/INFRA-5534
>             Project: Infrastructure
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: CMS
>            Reporter: Emmanuel Lecharny
>
> Ok, let me explain better...
> When I work on the MINA wite using one local repository, I have the 'content' directory containing :
> ...
> mina-project
> asyncweb-project
> ...
> (see http://svn.apache.org/repos/asf/mina/site/trunk/content/)
> When I look at the staging svn, I get :
> ...
> mina-project
> asyncweb-project
> ...
> (see https://svn.apache.org/repos/infra/websites/staging/mina/trunk/content/)
> But in the production svn I have :
> ...
> mina
> asyncweb
> ...
> (see https://svn.apache.org/repos/infra/websites/production/mina/content/)
> so when I try to use the bookmarkelt to edit the site, it shows mina instead of mean-project.
> I'm a bit stuck here : how do I publish the site and make the trunk and staging being pushed to production ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira