I saw this in the instructions: "You can test the source package by building it, then pointing to it from the source package of the FlexJS release candidate and building the examples in the FlexJS package."
Is there a FlexJS release candidate active? Is there a link to that? Thanks, Om On Fri, Nov 13, 2015 at 12:35 PM, OmPrakash Muppirala <bigosma...@gmail.com> wrote: > On Fri, Nov 13, 2015 at 12:25 PM, Alex Harui <aha...@adobe.com> wrote: > >> Hmm. Do you have the 11.1 playerglobal in frameworks\libs\player? >> >> > That was it. I copied over 11.1 and the build is successful. I will > change my vote. > > Thanks, > Om > > >> On 11/13/15, 12:05 PM, "omup...@gmail.com on behalf of OmPrakash >> Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote: >> >> >Here are the test failues: >> > >> ><snip> >> >fail-with-message: >> > >> >main: >> > >> >compile.unit.tests: >> > [mkdir] Created dir: >> >C:\temp\falcon0.5_release_testing\apache-flex-falconjx- >> >0.5.0-src\compiler.tests\classes >> > [javac] Compiling 67 source files to >> >C:\temp\falcon0.5_release_testing\apach >> >e-flex-falconjx-0.5.0-src\compiler.tests\classes >> > >> >unit.tests: >> > [mkdir] Created dir: >> >C:\temp\falcon0.5_release_testing\apache-flex-falconjx- >> >0.5.0-src\compiler.tests\results >> > [mkdir] Created dir: >> >C:\temp\falcon0.5_release_testing\apache-flex-falconjx- >> >0.5.0-src\compiler.tests\temp >> > [junit] unittest.properties not found >> > [junit] environment property - FLEX_HOME = C:\p\flexroot\git\flex-sdk >> > [junit] environment property - PLAYERGLOBAL_HOME = C:\Program >> >Files\Adobe\Ad >> >obe Flash Builder 4.7 (64 Bit)\sdks\4.14.1\frameworks\libs\player >> > [junit] environment property - PLAYERGLOBAL_VERSION = 11.1 >> > [junit] environment property - TLF_HOME = C:\p\flexroot\git\flex-tlf >> > [junit] environment property - AIR_HOME = C:\Program >> Files\Adobe\Adobe >> >Flash >> > Builder 4.7 (64 Bit)\sdks\4.14.1 >> > [junit] environment property - FLASHPLAYER_DEBUGGER = >> >C:\p\flexroot\flash_pl >> >ayer_debugger\flashplayer_17_sa_debug.exe >> > [junit] Running >> >org.apache.flex.compiler.internal.css.CSSArrayPropertyValueT >> >ests >> > [junit] >> >C:\temp\falcon0.5_release_testing\apache-flex-falconjx-0.5.0-src\com >> >piler.tests\temp\CSSArrayPropertyValueTests2981414201157739905.mxml(0): >> >This tag >> > could not be resolved to an ActionScript class. It will be ignored. >> > [junit] >> >C:\temp\falcon0.5_release_testing\apache-flex-falconjx-0.5.0-src\com >> >piler.tests\temp\CSSArrayPropertyValueTests4030022834236315034.mxml(0): >> >This tag >> > could not be resolved to an ActionScript class. It will be ignored. >> > [junit] Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time >> >elapsed: >> >0.72 >> >6 sec >> > >> >BUILD FAILED >> >> >C:\temp\falcon0.5_release_testing\apache-flex-falconjx-0.5.0-src\build.xml >> >:82: >> >T >> >he following error occurred while executing this line: >> >> >C:\temp\falcon0.5_release_testing\apache-flex-falconjx-0.5.0-src\compiler. >> >tests\ >> >build.xml:103: Tests failed >> > >> >Total time: 1 minute 8 seconds >> > >> >On Fri, Nov 13, 2015 at 11:44 AM, Alex Harui <aha...@adobe.com> wrote: >> > >> >> >> >> On 11/13/15, 11:13 AM, "Josh Tynjala" <joshtynj...@gmail.com> wrote: >> >> >> >> >I get permission denied errors trying to run the ApproveFalcon.xml >> >>script. >> >> >It appears that it can't write to /opt/local/bin/lib. lib doesn't >> >>exist in >> >> >/opt/local/bin actually. However, I can manually create that folder >> >>(OSX >> >> >asks me for my password), and then I can manually download each of the >> >> >files and copy them there (again, after entering my password). >> >> > >> >> >Anyway, I can get beyond this point manually, but I thought I'd >> mention >> >> >it, >> >> >in case you weren't aware. I didn't see any mention of running with >> >>sudo >> >> >in >> >> >the instructions, so I assume that's not what I'm expected to do. >> >> > >> >> >> >> Yeah, these approval scripts aren’t guaranteed to work smoothly on the >> >> wide variety of configurations of developer machines. I figured most >> >> folks had ANT_HOME pointing to a writeable set of Ant folders. I think >> >> you are pointing to some default ant launchers. Feel free to make >> >> adjustments to the scripts. >> >> >> >> -Alex >> >> >> >> >> >> >
