Hudson, MXMLC and Embedding Assets
19th July, 2010 – 4:28 pmQuick post to help out anyone in the same headscratching situation that I just found myself in. I was in the process of getting our Flash build up and running on Hudson when I fell foul of the following error:
[java] /foo/diablo-flash/workspace/adoption_ingame/src/com/mindcandy/diablo/adoption_ingame/controller/DropDownConfigManager.as(17): col: 4: Error: unable to resolve ‘dropDownConfig.xml’ for transcoding
[java]
[java] [Embed(source="dropDownConfig.xml", mimeType="application/octet-stream")]
[java]
[java] [Embed(source="dropDownConfig.xml", mimeType="application/octet-stream")]
Strange, I thought to myself, the file is definitnely there:
host:/foo/diablo-flash/workspace/adoption_ingame/src# ls -l
total 100
drwxr-xr-x 4 tomcat6 tomcat6 4096 2010-07-19 15:47 com
-rw-r–r– 1 tomcat6 tomcat6 12205 2010-07-19 15:47 dropdownConfig.xml
total 100
drwxr-xr-x 4 tomcat6 tomcat6 4096 2010-07-19 15:47 com
-rw-r–r– 1 tomcat6 tomcat6 12205 2010-07-19 15:47 dropdownConfig.xml
And then the answer struck me – the casing is different – dropDownConfig.xml in the Embed vs. dropdownConfig.xml on disc, sure enough bringing these two back into sync fixed the issue and my build proceeded as planned with Hudson.
I wondered why I had never come across this problem during day-to-day builds and then I remember that Mac OS ships with Case Insensitive filesystem by default…