I got again the same timeout, so no option for me build project by ant [1]. I will try Maven.
[1] https://paste.apache.org/6UPt pt., 16 lis 2018 o 09:28 Greg Dove <greg.d...@gmail.com> napisał(a): > I had that issue when I first set up again on my new machine last month. At > the time I manually installed the swcs in my local .m2 > > If I recall correctly I also looked at the MavenTestAdapter to try to > figure out what was wrong at the time. I think if it has one thing defined > and not another it was sending js actionscript to test on swf and giving an > error saying the the Document class was not Sprite (or something similar). > I figured it was just me at the time, and I think it went away after I have > the air/playerglobal swcs installed in .m2 > > I today's build I got the 'super-download' sequence that took ages, and > maven put all that stuff there, and also did prompt me for licence > acceptance. > It offered a setting for the future: > -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted= > > Followed by a pregenerated hash representing the machine I am now using. > > So I guess it would be possible to use that in the future, but I imagine > that now they are in my local .m2 cache, I will not need to anyway. > > Don't know if there's anything helpful there, hope it might be.... > > > > > On Fri, Nov 16, 2018 at 8:30 PM Alex Harui <aha...@adobe.com.invalid> > wrote: > > > I looked at MavenTestAdapter. It looks like it uses environment > variables > > for FLASHPLAYER_DEBUGGER, but it is expecting to find playerglobal as an > > artifact in the local maven repo. > > > > I put a link to the files I think you need on private@. I can't put it > > on dev@ because Adobe wants folks to accept licensing terms first. I'm > > assuming you've already accepted those terms bringing down Adobe bits for > > Ant or Flex. If users need to get around this then we'll spend more time > > figuring out why it isn't working for some folks. I seem to recall that > > some more recent version of Maven was needed to launch the Mavenizer > > automatically, but I can't find information on what version. IIRC, older > > versions of Maven can build all of Royale but can't automate the Adobe > > downloads. > > > > HTH, > > -Alex > > > > On 11/15/18, 10:41 PM, "Harbs" <harbs.li...@gmail.com> wrote: > > > > There are the env variables I’m using for all my builds: > > > > #!/bin/sh > > > > export ROYALE_COMPILER_REPO=/Apache/royale-compiler > > export FLEX_SDK_HOME=/FlexSDK/4.14.1 > > export AIR_HOME=/Apache/frameworks/AIRSDK_Compiler > > export PLAYERGLOBAL_HOME=/Apache/frameworks/libs/player > > export FLASHPLAYER_DEBUGGER=/Apache/frameworks/Flash\ Player\ > > Debugger.app/Contents/MacOS/Flash\ Player\ Debugger > > export ROYALE_HOME=/Apache/royale-asjs > > > > The Ant build seems to succeed. I thought Maven does not use > > environment variables? > > > > Either way, I think I can vote for this RC. The fact that Maven is > > failing is nothing new on my end… ;-) > > > > Harbs > > > > > On Nov 16, 2018, at 6:21 AM, Alex Harui <aha...@adobe.com.INVALID> > > wrote: > > > > > > It appears that there is something mixed up with your environment > > variables. > > > > > > The tests check for PLAYERGLOBAL_HOME, AIR_HOME, and > > FLASHPLAYER_DEBUGGER. I think all 3 have to be set or none have to be > > set. If some are set, it can confuse the tests. If all 3 are set, the > > tests should use playerglobal/airglobal and generate a SWF and run it in > > the debugger player. If none are set, the tests should use js.swc to > > generate a swf, but the swf is not run (since it wouldn't work without > > playerglobal). Instead, it is swfdump'd and the output is compared > against > > a prior swfdump. > > > > > > The output shows that js.swc is being used in the compile, but the > > swf is being run in the debugger player. > > > > > > HTH, > > > -Alex > > > > > > On 11/15/18, 4:59 PM, "Harbs" <harbs.li...@gmail.com> wrote: > > > > > > > > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FyBNf&data=02%7C01%7Caharui%40adobe.com%7C7931243fa0004c78011308d64b8e89f6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779472910908290&sdata=EzNAtqfkryWkRDjATNbf6rxN1TfudGCWR6qW5uOeIlQ%3D&reserved=0 > > > > > >> On Nov 16, 2018, at 2:27 AM, Alex Harui <aha...@adobe.com.INVALID > > > > wrote: > > >> > > >> Look in compiler/target/failsafe-reports and see what tests > > failed. I have to step away from my computer for about 3 hours. > > >> > > >> -Alex > > >> > > >> On 11/15/18, 4:18 PM, "Harbs" <harbs.li...@gmail.com> wrote: > > >> > > >> The ant build passed, but the Maven build failed: > > >> > > >> [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (analyze) > @ > > compiler --- > > >> [WARNING] Used undeclared dependencies found: > > >> [WARNING] org.antlr:antlr-runtime:jar:3.3:compile > > >> [WARNING] antlr:antlr:jar:2.7.7:compile > > >> [WARNING] Unused declared dependencies found: > > >> [WARNING] de.jflex:jflex:jar:1.6.0:compile > > >> [WARNING] org.antlr:antlr:jar:3.3:compile > > >> [WARNING] net.sourceforge.jburg:jburg:jar:1.10.3:compile > > >> [WARNING] > > org.apache.royale.compiler:compiler-jburg-types:jar:1.0.0:compile > > >> [WARNING] > > org.apache.royale.compiler:compiler-externc:jar:0.9.4:compile > > >> [INFO] > > >> [INFO] --- maven-failsafe-plugin:2.18.1:verify (default) @ > > compiler --- > > >> [INFO] Failsafe report directory: > > > /Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports > > >> [INFO] > > ------------------------------------------------------------------------ > > >> [INFO] Reactor Summary: > > >> [INFO] > > >> [INFO] Apache Royale: Compiler: Parent .................... > > SUCCESS [ 4.354 s] > > >> [INFO] Apache Royale: Compiler: Compiler-Common ........... > > SUCCESS [ 8.928 s] > > >> [INFO] Apache Royale: Compiler: Test Utils ................ > > SUCCESS [ 0.945 s] > > >> [INFO] Apache Royale: Compiler: Externc ................... > > SUCCESS [ 16.463 s] > > >> [INFO] Apache Royale: Compiler: Compiler .................. > > FAILURE [05:27 min] > > >> [INFO] Apache Royale: Compiler: Compiler-JX ............... > > SKIPPED > > >> [INFO] Apache Royale: Compiler: SWFUtils .................. > > SKIPPED > > >> [INFO] Apache Royale: Compiler: Debugger .................. > > SKIPPED > > >> [INFO] Apache Royale: Compiler: OEM Layer ................. > > SKIPPED > > >> [INFO] Apache Royale: Royale Ant Tasks .................... > > SKIPPED > > >> [INFO] Apache Royale: Royale Maven Plugin ................. > > SKIPPED > > >> [INFO] > > ------------------------------------------------------------------------ > > >> [INFO] BUILD FAILURE > > >> [INFO] > > ------------------------------------------------------------------------ > > >> [INFO] Total time: 05:58 min > > >> [INFO] Finished at: 2018-11-16T02:06:07+02:00 > > >> [INFO] Final Memory: 85M/1443M > > >> [INFO] > > ------------------------------------------------------------------------ > > >> [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-failsafe-plugin:2.18.1:verify (default) on > > project compiler: There are test failures. > > >> [ERROR] > > >> [ERROR] Please refer to > > > /Apache/approve/apache-royale-0.9.4-maven-src/royale-compiler/compiler/target/failsafe-reports > > for the individual test results. > > >> [ERROR] -> [Help 1] > > >> [ERROR] > > >> [ERROR] To see the full stack trace of the errors, re-run Maven > > with the -e switch. > > >> [ERROR] Re-run Maven using the -X switch to enable full debug > > logging. > > >> [ERROR] > > >> [ERROR] For more information about the errors and possible > > solutions, please read the following articles: > > >> [ERROR] [Help 1] > > > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoFailureException&data=02%7C01%7Caharui%40adobe.com%7C7931243fa0004c78011308d64b8e89f6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779472910908290&sdata=Ixuu6s8OjVIJJryypYCqwzpbQeL53NP7B2gJqVPlgEQ%3D&reserved=0 > > >> [ERROR] > > >> [ERROR] After correcting the problems, you can resume the build > > with the command > > >> [ERROR] mvn <goals> -rf :compiler > > >> > > >> BUILD FAILED > > >> /Apache/approve/ApproveRoyale.xml:775: The following error > > occurred while executing this line: > > >> /Apache/approve/ApproveRoyale.xml:786: exec returned: 1 > > >> > > >> Total time: 47 minutes 57 seconds > > >>> On Nov 16, 2018, at 12:48 AM, Alex Harui > <aha...@adobe.com.INVALID> > > wrote: > > >>> > > >>> It's also part of the ApprovalScript so if run it on this RC you > > can get some early info. > > >>> > > >>> -Alex > > >>> > > >>> On 11/15/18, 2:44 PM, "Harbs" <harbs.li...@gmail.com> wrote: > > >>> > > >>> It’s been a while and I don’t remember off-hand. > > >>> > > >>> I’ll probably take a stab at being RM in a few weeks and I > > imagine I’ll need to figure it out then… ;-) > > >>> > > >>> Harbs > > >>> > > >>>> On Nov 16, 2018, at 12:32 AM, Alex Harui > <aha...@adobe.com.INVALID> > > wrote: > > >>>> > > >>>> What errors do you get with Maven? > > >>> > > >>> > > >>> > > >> > > >> > > >> > > > > > > > > > > > > > > > > > > -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki <https://www.patreon.com/piotrzarzycki>*
