On 12/17/15, 2:29 AM, "Mihai Chira" <mihai.ch...@gmail.com> wrote:
>> It appears that flex-sdk_test uses the flex-flexunit build on the CI >> server. Does that mean the flex-flexunit build is not configured to >> produce the right artifacts for Flex customers. If so, that should >> probably get fixed. > >flex-flexunit does produce both >flexunit-4.3.0-20140410-flex_4.12.0.swc and >flexunit-4.3.0-20140410-as3_4.12.0.swc, and we need to use the first >one. I don't know where to check which one is used. > >Isn't flex-sdk_test simply using the test target of build.xml? That >one ends up using flexunit-tests.xml, which uses the >flexUnitTasks.tasks ant task. So that's why I thought we need to >replace >flex-flexunit\FlexUnit4AntTasks\test\sandbox\libs\flexunit-core-flex-4.1.0 >.x-sdky.y.y.y.swc >with one of the above. It appears that flex-sdk_test uses the "test" target in the main flex-sdk build.xml. I did notice in the console output [1] that it appears to be using both flexunit-4.3.0-20140410-as3_4.12.0.swc and flexunit-4.3.0-20140410-flex_4.12.0.swc on the library path in that order. I don't know if that is correct or not. Do they have conflicting definitions? Also note that the compiler shouldn't care as much about the order in the library path as the compile time for the definitions in the SWCs. So if class Foo was compiled into the as3 SWC and then later into the flex SWC, the definition in the flex SWC should always win regardless of order. Maybe the SWCs were built in a different order on your computer. -Alex [1] http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_test/433/console
