Ok, so I've been racking my brain over getting a Flex 4 app we've written using beta 2 working with 4.0.0.13875. It uses a combination of halo and spark components and I've been able to resolve all compilation errors except for having the Halo and Spark themes being used together at compilation. Please note, I've updated the halo namespace to the mx namespace as well as migrated all spark components that have changed from beta2.
I've tried the following permutations with FlexMojos 3.6 to no avail: --------------------------------------------------------------------------------------------------------- Tried: Deploying a new framework-configs-4.0.0.13875.zip to my local nexus repo with both the Halo and Spark themes in their appropriate folders and updating the flex-config.xml file to also use the halo.swc as a theme. I also tried commenting out all themes, as done in previous SDK releases of the flex-config.xml file, with the same results as given below. Result: The changes to the flex-config.xml are ignored by the compile- swf/swc goals and only the spark.css file is listed as the theme to use to the compiler. I receive compilation errors for unknown components in the mx namespace due to the lack of the halo.swc file being present as a theme. --------------------------------------------------------------------------------------------------------- Tried: Deploying halo.swc and spark.css as artifacts in local nexus repo and including them as dependencies with the theme scope. Result: Only the halo.swc artifact is used as a theme by the compile- swf/swc goals although the spark.css artifact is downloaded by dependency management, just never referenced during compilation. I receive a successful build with warnings that particular styles don't exist for numerous spark components. These styles are in the spark.css theme which is not being included, and the spark styles are not applied. --------------------------------------------------------------------------------------------------------- Tried: Using the updated framework-configs-4.0.0.13875.zip from the above example, I listed the halo and spark themes as themes under the config section for the plugin. Result: The compile-swf/swc goals look in my src/main/resources folder for files named "themes/Spark/spark.css" and "themes/Halo/halo.swc" instead of in the appropriate folder under target from the exploded framework-configs.zip file. --------------------------------------------------------------------------------------------------------- After trying the above I ram out of ideas. I noticed in the source for AbstractFlexCompilerMojo there is a case to include only the Spark theme if no other themes are declared in the POM, which explains some of the behavior I saw in my first trials. So here are my questions: - What is the recommended way of working with multiple themes in Flex4 using FM? - If we're to use dependencies in the theme scope, can we have a way to use css artifacts since these are valid theme artifacts in Flex 4? - If the framework-configs.zip is going to be distributed with the spark theme bundled, can you distribute all the default themes that comes with the SDK and allow us to select which to use? - Any suggestions on how to solve the immediate need of devs using halo and spark with FM 3.6? Any help is appreciated as I expect the same problem will crop us with the 4.0 final release as it uses an identical flex-config.xml which I'm guessing may help dictate how the SDK is deployed. Thanks at the very least for reading this far :) -Brian -- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos http://flexmojos.sonatype.org/ To unsubscribe from this group, send email to flex-mojos+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
