We have a large, multi-module, application being compiled by flexmojos (great work by the way!) and we use the link-report & load-externs features of the compiler to reduce file sizes on our SWFs that are loaded by parent SWFs. This features works fine when using the 'install' maven goal, but it does not work when using the 'compile' goal. To be very specific... it does not work with the compile goal unless you happen to have run 'install' already and the XML link- report file has already been installed to the local Maven repo.
Example: 1. Imagine a multi-module project with two children: moduleA and moduleB, where moduleB depends on moduleA 2. The poms have been setup so that moduleA runs 'link-report' to produce the XML link-report file which is then used by moduleB using the 'load-externs' option 3. Clean out .m2/repository/myapp 4. Run 'mvn clean compile' 5. Build fails on moduleB because it can't find the link-report XML (Maven spits out the usual instructions for how to install it to your local repo) 6. Now run 'mvn clean install' 7. Build suceeds because on the install phase on moduleA the link report XML was install to your local Maven repo and moduleB was able to use it Hopefully this is clear because I know link-report/load-externs is not an often used feature. I believe flexmojos used to have a similar problem with SWCs (with multi-module projects) as it tried to look for them in the repo first, and not in the working folder of the project --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
