On Thu, Dec 24, 2009 at 6:35 AM, Christophe Herreman <[email protected]> wrote: > is there any specific reason why you made it work like that? > > Without knowing anything about the FM internals and objectively speaking, I > think that it should follow Flex SDK docs/guidelines as much as possible. On > top of that, it is obviously very cumbersome to have to list and maintain > these classes manually for big libraries like ours.
Velo can address the reasons better, but some things I hope will help clarify. FM uses the Flex Java compiler API and not the command line compc compiler directly. The docs for that for building libraries show the include sources option first. We've run into discrepancies between the docs for the compiler API and the command line before. Both compc and the Java API use the same internal classes eventually, but how they set them up is different. Don't ask me why, makes no sense to me (probably developed by separate teams). The compc docs on manifests and namespaces seem confusing and vague to me. Also, Flex Builder does lots of extra setup work for you. FM has to approximate that work without any guidelines or documentation. The Flex compiler doesn't always fit into the Maven world, and when they conflict, Velo generally goes with Maven conventions. I'm still a little confused as to exactly what's failing and working for you. Manifest files are specifically for listing which files you want, but you seemed frustrated that it only included the files listed in the Manifest. If you don't want to maintain your own manifest, then FM has a manifest goal to create one for you with include/exclude patterns. It's entirely possible there's a bug in FM, or a bug in the Java compiler API as well. Either others don't use namespaces much, or they're not chiming in on what worked for them, so you might just be treading some new territory. When I get a minute, I'll play around with your sample project and see if I can understand what isn't working. 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/
