In the compiler.tests/results folder, there should be a TEST-as.ASKeywordTests.xml file. It might have more info.
At some point, my file contains: Generating test: Compiling test: -external-library-path=/Users/aharui/adobe/flashplayer/11.1/playerglobal.sw c -library-path= -namespace=http://ns.adobe.com/mxml/2009,/Users/aharui/ApacheFlex4.14.1/fra meworks/mxml-2009-manifest.xml /Users/aharui/falcon/apache-flex-falconjx-0.5.0-src/compiler.tests/temp/ASK eywordTests9060700658635002989.as 839 bytes written to /Users/aharui/falcon/apache-flex-falconjx-0.5.0-src/compiler.tests/temp/ASK eywordTests9060700658635002989.swf in 0.973 seconds Executing test: [/Users/aharui/adobe/flashplayer/11.1/Flash Player Debugger.app/Contents/MacOS/Flash Player Debugger, /Users/aharui/falcon/apache-flex-falconjx-0.5.0-src/compiler.tests/temp/ASK eywordTests9060700658635002989.swf] Generating test: .. I’m wondering if you got to executing test and the Flash Player Debugger part. That’s another environment variable. -Alex On 11/13/15, 4:25 PM, "Josh Tynjala" <joshtynj...@gmail.com> wrote: >Yes, it exists. I can see the 10 SWF files in that directory, and as you >can see, there are no compiler errors in the output. > >- Josh > >On Fri, Nov 13, 2015 at 4:02 PM, Alex Harui <aha...@adobe.com> wrote: > >> This line looks suspicious: >> >>-external-library-path=/Users/joshtynjala/Development/Flex/sdks/AIRSDK/AI >>R1 >> 6.0.0.292/frameworks/libs/player/16.0/playerglobal.swc >> >> >> Does that file actually exist? >> >> -Alex >> >> On 11/13/15, 3:07 PM, "Josh Tynjala" <joshtynj...@gmail.com> wrote: >> >> >I don't have time to debug the properties stuff, so I just gave up and >>set >> >real environment variables. Unfortunately, now it's failing on some of >>the >> >tests, but there's no explanation why. I remember hearing that it >>helps to >> >add the folder to the trusted locations for Flash Player, but that >>made no >> >difference. Here's the output from the last test before the build >>fails: >> > >> >Generating test: >> >Compiling test: >> >>>-external-library-path=/Users/joshtynjala/Development/Flex/sdks/AIRSDK/A >>>IR >> >16.0.0.292/frameworks/libs/player/16.0/playerglobal.swc >> >-library-path= -namespace= >> > >> >>http://ns.adobe.com/mxml/2009,/Users/joshtynjala/Desktop/apache-flex-falc >>o >> >>>njx-0.5.0-src/apache-flex-falconjx-0.5.0-src/compiler/generated/dist/sdk >>>/f >> >rameworks/mxml-2009-manifest.xml >> >>>/Users/joshtynjala/Desktop/apache-flex-falconjx-0.5.0-src/apache-flex-fa >>>lc >> >onjx-0.5.0-src/compiler.tests/temp/ASKeywordTests1508068553086257.as >> > >> > >> >741 bytes written to >> >>>/Users/joshtynjala/Desktop/apache-flex-falconjx-0.5.0-src/apache-flex-fa >>>lc >> >onjx-0.5.0-src/compiler.tests/temp/ASKeywordTests1508068553086257.swf >> >in 0.094 seconds >> >Tests run: 10, Failures: 10, Errors: 0, Skipped: 0, Time elapsed: 1.897 >> >sec >> > >> >BUILD FAILED >> >>>/Users/joshtynjala/Desktop/apache-flex-falconjx-0.5.0-src/ApproveFalcon. >>>xm >> >l:606: >> >The following error occurred while executing this line: >> >>>/Users/joshtynjala/Desktop/apache-flex-falconjx-0.5.0-src/apache-flex-fa >>>lc >> >onjx-0.5.0-src/build.xml:82: >> >The following error occurred while executing this line: >> >>>/Users/joshtynjala/Desktop/apache-flex-falconjx-0.5.0-src/apache-flex-fa >>>lc >> >onjx-0.5.0-src/compiler.tests/build.xml:175: >> >Tests failed >> > >> >On Fri, Nov 13, 2015 at 1:11 PM, Alex Harui <aha...@adobe.com> wrote: >> > >> >> >> >> >> >> On 11/13/15, 12:25 PM, "Josh Tynjala" <joshtynj...@gmail.com> wrote: >> >> >> >> >I try to avoid setting real environment variables since I find it >>more >> >> >convenient to use the properties files to remember all of the values >> >>for >> >> >later. For instance, I added approvefalcon.properties to set >> >>env.ANT_HOME. >> >> >However, it looks like the values from approvefalcon.properties >>don't >> >>get >> >> >inherited by other Ant scripts started by ApproveFalcon.xml, so I >> >>guess I >> >> >need to set real environment variables this time. >> >> >> >> Ant does pass properties around although we might be using different >> >> property names in some scripts. But I think the real issue is that >>Ant >> >>is >> >> calling various tools and the tools can’t pick up Ant properties. If >> >>you >> >> provide more detail on which environment variables are problematic, >>we >> >>can >> >> discuss ways to deal with that. >> >> >> >> -Alex >> >> >> >> >> >>
