On 9/22/15, 8:19 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Hi, > > >So I got a lot further in my efforts to adjust Flexmojos to support >FlexJS (Even if I thought I already did). > >I added a new artifical artifact >"org.apache.flex.flexjs.framework:framework:pom and zipped the xml files >in the framework directory. I even added all "project/*/*-manifest.xml" >files. Now I'm getting the following message from the compiler: > > >Could not find file for class: org.apache.flex.core.ILayoutParent > >When looking around, I could find that there is such a file located in >flex-asjs/frameworks/js/FlexJS/libs/org/apache/flex/core/ILayoutParent.js > >So what is located in these directories? I thought all the js is packaged >in with the swcs? But this doesn't seem to be the case. How does this >directory fit into the big picture? All JS is currently copied into js/FlexJS/libs because files found there override what is found in the SWCs. This allows folks to monkey-patch what is in the SWCs. Regarding ILayoutParent, a recent check-in renamed it so maybe something isn't fully in sync. > >Chris > >PS: >- Is there a reason for the "project/*/*-manifest.xml" files not having a >standardized name? Most are called basic-manifest.xml but it seems the >only similarity is that they are all ending on "-manifest.xml" There are different manifests for different component sets. FlexJS allows for swapping in different component sets. Like replacing the basic component set with a set that leverages JQueryUI components or the Flat/Bootstrap components. >- Is there a reason for not bundling the manifest in the swc files? >Currently referencing them from the flex-config.xml and packaging parts >of the artifacts inside another doesn't really look clean to me. > I agree it is messy. I don’t think FB knows how to unbundle them from a SWC. But if that isn’t true, we can certainly head in that direction. HTH, -Alex
