Databases
StackOverflow2013
Postsdbo
POWhy doesn't ${locale} resolve in my <compc> Ant task?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy doesn't ${locale} resolve in my <compc> Ant task?
    text
    copied!<p>I've seen a number of examples, <a href="http://bit.ly/9zQoxv" rel="nofollow noreferrer">e.g. here</a>, where people are including locale resource bundles by referencing the locale attribute in the element. For some reason this doesn't work for me. Here's what I have for the task:</p> <pre><code>&lt;compc output="${deploy.dir}/myfrmwrk.swc" locale="en_US"&gt; &lt;source-path path-element="${basedir}/src/main/flex"/&gt; &lt;include-sources dir="${basedir}/src/main/flex" includes="*" /&gt; &lt;include-libraries file="${basedir}/libs"/&gt; &lt;compiler.external-library-path dir="${FLEX_HOME}/frameworks/libs/player/9" append="true"&gt; &lt;include name="playerglobal.swc"/&gt; &lt;/compiler.external-library-path&gt; &lt;compiler.library-path dir="${FLEX_HOME}/frameworks" append="true"&gt; &lt;include name="libs"/&gt; &lt;include name="locale/${locale}"/&gt; &lt;/compiler.library-path&gt; &lt;load-config filename="${basedir}/fb3config.xml" /&gt; &lt;/compc&gt; </code></pre> <p>This fails with a bunch of errors of the form:</p> <pre><code>[compc] Error: could not find source for resource bundle ... </code></pre> <p>I can make it build with this one change:</p> <pre><code>&lt;include name="locale/en_US"/&gt; </code></pre> <p>The configuration file generated by Flex Builder 3 actually renders this as "locale/{locale}" (notice the $ is missing). I've tried that as well with the same (failing) results.</p> <p>For now, I'm doing OK directly injecting en_US as we won't be doing localization bundles for quite some time, but I will eventually need to get this working. Also, it bugs me that I can't make it work the way that it SHOULD work!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload