Hi Alex, so I commented out my magic feature and what should I say ... it still seems to be working. I am no longer getting these error messages where the compiler was complaining not to find some of the components. I guess this was related to some of the Framework projects not having "namespace" declarations. I found this out yesterday and added them. So I guess my problems were related to that. So I'll remove that code (even if I liked the output) ... no wait ... I'll just omit that from automated executions. I guess having a goal to dump something like that could be useful to track down problems.
Chris ________________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Mittwoch, 18. Mai 2016 18:32:10 An: dev@flex.apache.org Betreff: Re: AW: AW: [DISCUSS] Handling of namespaces and xml On 5/18/16, 1:58 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Hi Alex, > >I just had a look at the content of the catalog.xml and I agree actually >the information should be available automatically without packing >anything in the SWC. >How much work would it be to make the compiler use this? I am currently >working on the compilation of the examples using Maven and I manually had >to add a manifest.xml file listing all components that were referenced by >MXML files in the examples. > >I guess that there is currently none here that would probably be wanting >to change the compiler to support this, so as a workaround I'll implement >something that generates manifests on the fly by inspecting the >classpath. But I'll make it super-easy to remove. I looked into this a bit more, and it appears that the compiler already uses catalog.xml and the -manifest.xml files are not needed when building apps, only when making the SWC. Can you verify this on your end? I removed all the <namespace> tags from a flex-config.xml and compiled the FlexJSStore example and it worked. I definitely see code in Falcon that reads the catalog.xml as well. Maybe some IDE is counting on the manifest.xml files, but it sure looks to me right now that a Maven build shouldn't need <namespace> tags. I did see that <namespace> tags are supported by MXMLC as well as COMPC, so I'm still puzzling over why that is. Maybe it is so you can add other classes to the MXML mapping that the original SWC developer did not do. So maybe this is already done. Let me know what you find out. -Alex
