Hi, We've upgraded to use the 3.3 flex-mojos, but we're curious on best practices regarding project structure when using the flex-mojos in a java-backed application. Our project is structured as follows:
\ |- flex-shell module (generates the main swf and contains the assets folder) |- web module (has all of the non-flex web assets) ... other modules We are thinking of merging the two modules: the flex shell module and the web module into one, however we're unsure if this follows best practices. How do most people structure their projects? Currently, we have to do custom packaging of the assets in the flex shell module via an assembly and then pull that in via the dependency plugin. We're trying to avoid doing this as it creates complications when using the release plugin. Any and all input would be most welcome. Best Regards, Allan --~--~---------~--~----~------------~-------~--~----~ 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?hl=en?hl=en http://blog.flex-mojos.info/ -~----------~----~----~----~------~----~------~--~---
