I also think I discovered why the copy-flex-resources doesn't copy the HTML wrapper. Because it seems to make sense to put those files in the WAR module itself.
https://docs.sonatype.org/display/FLEXMOJOS/Html+Wrapper+Mojo I understand the reasoning, but in my case, I have the HTML wrapper fairly tightly coupled to the SWF and want them to stay together. It also keeps Flash Builder 4 happy as well. Therefore, I'll probably go with the Assembly/Overlay approach. On Sep 16, 7:02 pm, David Vree <[email protected]> wrote: > I just got the answer to one of my main questions. Maven assemblies > are automatically attached to the project and get picked up when a > deploy happens. > > First question on the FAQ: > > http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#deploy > > On Sep 16, 5:32 pm, David Vree <[email protected]> wrote: > > > I have read in previous posts that folks here use the maven assembly > > plugin to create a zip of their flex artifacts and then use the Maven > > WAR overlay plugin to merge it into a WAR module. > > > Does anyone have examples of how to configure Maven to do that? One > > question I have is how to deploy the zip file SNAPSHOT back into > > Nexus. Should the Flex module be packaged as a zip instead of a swf? > > Or do I need to create another Maven module, just for creation the zip > > assembly (I hope not)? > > > Alternatively, is the copy-flex-resources goal configurable enough to > > do all of this? It doesn't look like it would copy the HTML wrapper, > > fonts, images, etc. -- 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/
