While you're in ant, automate your project assets also. Setup a main
workspace asset repo, pull files from there.
Another good trick, if you have multiple projects that work together, use
ant to create a main output folder and compile files there.
On Dec 9, 2013 4:17 AM, "Stephan Plath" <flex-...@gmx.net> wrote:
> The current version of the Ant html-wrapper task doesn't supports to use
> external files. Instead it only uses its embedded template resources
>
> - /history
> - history.css
> - history.js
> - historyFrame.html
> - expressInstall.swf
> - index.template.html
> - swfobject.js
>
> I added a "wrapperFile" parameter to the HtmlWrapperTask, so I can use a
> project specific HTML wrapper file. That's fine for me and is working
> faultless.
>
> The question is now: Would it be more reasonable to parameterize the
> entire directory ("templateDir") instead of only doing it for the HTML
> template? Or should it be possible to use both - either "templateDir" or
> "wrapperFile"?
>
> Thanks, Stephan
>
