[
https://issues.apache.org/jira/browse/FOR-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730230#action_12730230
]
Brian M Dube commented on FOR-1175:
-----------------------------------
rsync is a great solution, but it is manual. Don't count on Ant to handle this
for you because there is no Java implementation of rsync. The incredible tool
you mention will help show that Java efforts on the rsync front have fallen
short.
> when building static site, copy skin files only if they have been modified
> since the last static site build
> -----------------------------------------------------------------------------------------------------------
>
> Key: FOR-1175
> URL: https://issues.apache.org/jira/browse/FOR-1175
> Project: Forrest
> Issue Type: Improvement
> Components: Launch 'forrest'
> Affects Versions: 0.9-dev
> Reporter: Brolin Empey
> Priority: Minor
>
> Years ago, I asked about this issue on the user mailing list:
> <http://article.gmane.org/gmane.text.xml.forrest.user/4391/match=skin+directory+copied+unconditionally+static+site+build>
> AFAIK, nothing has changed since then. I want to report the issue here so it
> does not get forgotten.
> Anyway:
> When I rebuild my static site, the "skin" directory seems to be copied
> unconditionally to the build/site/ directory. This means that, because the
> local files have been rewritten and consequently have newer modification
> times than the remote files, skin/ is uploaded each time I use lftp's reverse
> mirror function to publish changes to my public Web site, even if nothing in
> the skin has changed.
> The Ant target that copies the non-generated content to build/site/ should be
> changed to copy files (including skin files) only if the source file has
> changed. Maybe rsync could be used to copy non-generated content.
> If no one fixes this issue, I may use oDesk to hire someone to fix the issue.
> I have already had success with using oDesk to hire Michal Sciubidlo to fix
> Mozilla.org bug 269728. I have hired Michal again to fix Mozilla.org bug
> 178506.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
