H5BP 构建脚本 - 依赖项
我是 ant 新手，但我的期望是 h5bp 中的构建脚本将使用上次修改的信息来确保它仅在需要时生成新文件。这种情况不会发生 - 一切似乎都在每次调用 ant build 时运行。有什么办法可以防止这种情况发生吗？这是 h5bp 构建脚本的设计特征吗？
当我需要时，我将 project.xml 扩展为 ftp 到我的服务器（也复制到我的开发服务器），我发现这非常有用。然而，由于要从 publish 文件夹复制的图像具有新日期，即使未更改，它们每次都会通过 ftp 上传，这很慢且不必要。 FWIW 我正在 Windows 7 上运行它（上传到 Linux/Apache 服务器）。
查看 build.xml 文件，我看到大量覆盖设置 - 大多数为“no”，还有一些为“yes” “，所以我猜已经做出了一些有意识的决定。感谢理解原因。
感谢您的任何建议。
谢谢
Abo
PS 除此之外，构建脚本非常棒！
I'm an ant novice but my expectation is that the build script in h5bp would use last modified info to ensure that it only generated new files when it needed to. This does not happen - everything seems to run on every invocation of ant build . Is there a way I can prevent this? Is it a design feature of the h5bp build script?
I've extended project.xml to ftp to my server when I need to (and also to copy to my development server) which I find really useful. However since the images to be copied from the publish folder have new dates, even though unchanged, they are all ftp'd up each time which is slow and unnecessary. FWIW I'm running this on Windows 7 (uploading to a Linux/Apache server).
Looking through the build.xml file, I see plenty of overwrite settings - most to "no" and a few to "yes", so I guess some conscious decisions have been made. Appreciate understanding why.
Grateful for any suggestions.
Thanks
Abo
PS Apart from this, the build script is just great!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
所以，我想我可以回答我自己的一些问题。
每次构建时都会删除发布（和中间）目录，因此始终会重新生成发布的图像文件。
有人知道是否有原因导致 img 目录不能保留在发布和中间目录中吗？
谢谢
So, I think I can answer some of my own question.
The publish (and intermediate) directories are deleted on each build, so the published image files are always regenerated.
Anyone know if there's a reason that the img directory cannot be left in publish and intermediate?
Thanks
每次您构建一个版本时，IT 都会从源生成一个新版本。保留旧图像只会产生大量不必要的文件。
也许您可以在第一次通过 FTP 传输图像文件时设置一个标志，然后除非特别要求，否则不要上传图像？
IT generates a new build from the source each time you build one. Leaving old images would just result in lot of unnecessary files.
Perhaps you could set a flag when the image files are FTPed for the first time, and then on not upload the images unless specifically asked to do so?