On Fri, Oct 31, 2008 at 4:06 AM, Marvin Froeder <[EMAIL PROTECTED]> wrote: > If you put your sources on src/main/flex and your assets on > src/main/resources, flex-mojos will handle this situation and make your > sources to compile. But I can't do the same workaround on flex-compiler > invoked by asdoc tool, so is a hard choice. Or you generate Asdoc, or you > keep your assets organized.
We put all of our embedded assets in src/main/flex/images with our source files. We put runtime-loaded assets in src/main/resources. Right now we only have 1 or 2 assets that are both embedded and runtime, so we just copy those to both folders. We did this because the default behavior of the resources plugin is to copy your src/main/resources into your target directory, and we didn't see the need to copy embedded resources there. So I'm not sure what the right answer is, but that has worked for us, including asdoc generation. But Velo, are you saying that the asdoc tool does not support multiple source paths? Or that it just doesn't resolve embedded assets from any source path but the first/default? Logan --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
