[jira] Commented: (FOR-1099) forrestbot "getsrc.svn" workstage assumes that "project.content-dir" contains all the content

["David Crossley (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FOR-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626478#action_12626478 ] 

David Crossley commented on FOR-1099:
-------------------------------------

I am not sure if the use of "recursive=false" for the top-level source directory was just for efficiency reasons or for some other reason. Anyway in r689754 i changed it to do "recursive=true" and not check out the "project.content-dir" separately.


> forrestbot "getsrc.svn" workstage assumes that "project.content-dir" contains all the content
> ---------------------------------------------------------------------------------------------
>
>                 Key: FOR-1099
>                 URL: https://issues.apache.org/jira/browse/FOR-1099
>             Project: Forrest
>          Issue Type: Bug
>          Components: Tool: Forrestbot
>            Reporter: David Crossley
>
> The "getsrc.svn" forrestbot workstage assumes that "project.content-dir" contains all the content, i.e. src/documentation, src/documentation/content, src/documentation/content/xdocs, src/documentation/resources, src/documentation/conf, etc.
> However, some projects split up the default site directory structure and re-define it in their forrest.properties file. Our projects docs in $FORREST_HOME/site-author is one such case. Therefore our site-author/conf and site-author/resources directories are missing when forrestbot does the svncheckout of the sources.
> Also because we define "project.content-dir=." then the "svncheckout" does not do it. I presume that is because it has already done a checkout here using "recursive=false".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.