So I'm currently comparing the Maven and the Ant distributions and looking for differences.
I do have some questions: - the "framework" directory contains a log of tupples: xyz-config-template.xml and xyz-config.xml: Where does the xyz-config.xml get generated from the template in the ANT build? (I assume it generates them from the templates as part of the build)... could we possibly omit the "templates"? It seems as if they are only needed to generate the configs for a given set of configured properties. If that's the case, we don't need them in the distribution. - I noticed the externs seem to have completely different names (in js/libs) (royale-typedefs-js.swc in Maven and js.swc in Ant) ... unfortunately the case seems to be sort of random: js for the js extern, but GCL for the gcl one) - I noticed in the maven version the tag is called "swf-external-library-path" and in the Ant version it's "external-library-path". Same with swf-libary-path, which is called "library-path" in the Ant version. - The Ant version seems to be missing a number of manifests which the Maven version has: - manifests/svg-manifest-graphics.xml - manifests/html-manifest.xml - manifests/mdl-manifest.xml - manifests/express-manifest.xml - manifests/fa-manifest.xml - manifests/jewel-manifest.xml - manifests/crux-manifest.xml - manifests/icons-manifest.xml - The Maven version was missing an entry in "theme" which points to <filename>themes/Basic/src/basic.css</filename> in the Ant version - In the most xyz-config.xml files the library path references the JS version instead of the SWF version of Languages lib. - The root element of the flex-config.xml was named "roayale-config" in the Maven distribution and "flex-config" in the Ant distribution and it contained a reference to the mxml-2009-manifest.xml. Also did the Ant version contain a lot more implicit imports as well as a fxg-base-class element - The Maven version of the royale-config.xml adds a path entry to the library-path and js-library-path while the Ant version adds each file manually. So far the changes I found ... I updated the distribution in the "features/distribution-allignment" branch. But I guess I'll keep working on this and try to get the maven distribution to have the same directory structure as the Ant one (but excluding all the unnecessary stuff). Chris -----Ursprüngliche Nachricht----- Von: Christofer Dutz <christofer.d...@c-ware.de> Gesendet: Sonntag, 28. Februar 2021 12:28 An: dev@royale.apache.org Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned Ok ... regarding the Array problem ... I have found the "Array.as" file in "compiler-externc" and "royale-typedefs/js" ... both are identical ... I'm not quite sure which one is used (I'm a bit rusty regarding how all of these externs and stuff work together) I did check and the royale-config.xml lists the mxml-2009-manifest.xml (in both the non-swf as well as the with-swf version) so not quite sure why adding that to the configuration changes anything. Chris -----Ursprüngliche Nachricht----- Von: Christofer Dutz <christofer.d...@c-ware.de> Gesendet: Sonntag, 28. Februar 2021 12:08 An: dev@royale.apache.org Betreff: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned Hi all, so thankfully Carlos re-sent me this link: flex-sdk/README_integration_with_Adobe_FlashBuilder.txt at master * apache/flex-sdk (github.com)<https://github.com/apache/flex-sdk/blob/master/ide/flashbuilder/README_integration_with_Adobe_FlashBuilder.txt> So it seems as if we don't have a ide/flashbuilder/flashbuilder-config.xml with a "express-install-swf" element in it (we don't have the entire file) ... do we need this? Besides that, it seems all is setup as expected. Will continue looking into other things that could be wrong. Chris