- Read through Visibility 4 document. Need to talk with Phil on next steps.
- Took a look at the assets directory issue (b/c it was driving me bonkers). I think it may have something to do with how Maven and Flex interpret their directory structure.
viztales
Dimension reduction, State, Orientation, and Speed
viztales 
You know, that would make sense. Does a Maven Air app still put all its files in the Target directory? That’s where it gets it’s structure for war files…
Yes and no. It does on Windows, but I noticed that on my mac it leaves all of the files in the original directory and only creates the actual Air app file in the target (along with an air directory that contains the descriptor.xml file, a classes directory and I have a surefire-reports directory).
I did find a blog where someone had basically went through the pains of breaking down the Maven-Flex integration. It appears that in order to create the correct directory structure needed for the Air app, the directory structure used by Maven and Flex need to met halfway. Additionally, this guy broke down the POM files into the main POM with several child POMs so that the correct directories could be created. It made me curious about AirFileImageApp and what else could be done to create the correct directories.