Hi Nigel,
are you using the namespace: xmlns:s="library://ns.adobe.com/flex/spark" at least that's the one I'm using and FM and IntelliJ both work nicely with SolidColor. >From your post it seems that you are using the old Flex namespaces. I think >these have been introduced with Adobe Flex 4.0 Regarding the target-player. Are you targeting Flash Player 7.0? If yes, I would ask you to use the version 7.0 of the playerglobal artifact. I cleaned up the configuration of FM a little cause there were far to many knobs and levers which you could actually only use to screw things up ;-) But I just had a look. You will be having trouble with this as we don't have anything below 10.2 supported. If it is a requirement for you to target the 7.0 of flashplayer, you will have to provide the matching playerglobal manually. If it still doesn't work, please feel free to come back and I'll see what I can do for you. Chris ________________________________ Von: Nigel Magnay <[email protected]> Gesendet: Donnerstag, 28. Mai 2015 16:09 An: [email protected] Betreff: FM7.1.0 and odd compilation error. I'm trying to upgrade our app to a more modern version of FM and Flex. I'm getting weird errors on a library project, like this: /Users/magnayn/dev/realtimehealth/realtime-workspace/realtime/flex-modules/realtime-flex-controls-spark/src/main/flex/net/realtimehealth/realtime/command/dialog/observations/ObservationGridItemRenderer.mxml(76): Error: Could not resolve <s:SolidColor> to a component implementation. <s:SolidColor id="background" alpha="0.2"/> I'm building with FM7.1.0-SNAPSHOT and the 4.11.1 sdk (though I have seen the above on other SDKs, I think it's an issue with the move to 7.x) It compiles fine in FB, so I'm resorting to looking at the configuration XML generated. The prominent things I notice are: The FB version has a populated <namespaces> section, the FM does not. E.g: <namespaces> <!-- compiler.namespaces.namespace: Specify a URI to associate with a manifest of components for use as MXML elements--> <namespace> <uri>http://ns.adobe.com/mxml/2009</uri> <manifest>mxml-2009-manifest.xml</manifest> </namespace> Secondly, all attempts to persuade FM to have <target-player>7.0.0</> (by the targetPlayer config section) seem to have failed, and target-player insists to remain 11.1 Thirdly the ordering in the external-library-path section seems to be different from the POM in one way (I explicitly list all library dependencies) in that the playerglobal is the last listed, not the first (not sure if this is significant). I've attached the outputs from config and our POM. Any hints gratefully received..
