Good question. Piotr ran into this with the release. There are some suggestions in the discuss thread you can try.
What should happen at that point is that the Flash Player Projector Debugger player (also known as the standalone debugger) should launch and run some tests and then exit. So if you are not seeing a new window appear at that point it probably means that using rundll32 to launch the standalone debugger as the default handler for a .swf file is not working and you will need to configure your system for that. I thought that the recent Flash Projector Debugger installers did register .swf, but maybe not. As suggested in the release discuss thread you can try clicking on a SWF in your file explorer and see if the Projector Debugger launches. HTH, -Alex From: Serkan Taş <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Thursday, November 29, 2018 at 6:02 AM To: "[email protected]" <[email protected]> Subject: Re: build is broken : royale-asjs, mxroyale, sparkroyale Hi, What may be the reason for the error below ? Thanks, Serkan [flexunit] Executing 'rundll32' with arguments: [flexunit] 'url.dll,FileProtocolHandler' [flexunit] 'D:\dev\royale-emulation-works\github\royale-asjs\frameworks\projects\Basic\src\test\royale\FlexUnitRoyaleApplication.swf' [flexunit] [flexunit] The ' characters around the executable and arguments are [flexunit] not part of the command. [flexunit] [flexunit] Waiting for client connection ... [flexunit] [flexunit] Stopping server ... [flexunit] End of test data reached, sending acknowledgement to player ... [flexunit] Closing client connection ... [flexunit] Closing server on port [1024] ... BUILD FAILED D:\dev\royale-emulation-works\github\royale-asjs\build.xml:648: The following error occurred while executing this line: D:\dev\royale-emulation-works\github\royale-asjs\frameworks\build.xml:117: The following error occurred while executing this line: D:\dev\royale-emulation-works\github\royale-asjs\frameworks\build.xml:290: The following error occurred while executing this line: D:\dev\royale-emulation-works\github\royale-asjs\frameworks\projects\Basic\build.xml:61: The following error occurred while executing this line: D:\dev\royale-emulation-works\github\royale-asjs\frameworks\projects\Basic\src\test\royale\build.xml:142: java.util.concurrent.ExecutionException: Socket timeout waiting for flexunit report at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at org.flexunit.ant.tasks.TestRun.run(Unknown Source) at org.flexunit.ant.tasks.FlexUnitTask.execute(Unknown Source) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99) at org.apache.tools.ant.Task.perform(Task.java:350) at org.apache.tools.ant.Target.execute(Target.java:449) at org.apache.tools.ant.Target.performTasks(Target.java:470) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1388) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:36) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:437) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99) at org.apache.tools.ant.Task.perform(Task.java:350) at org.apache.tools.ant.Target.execute(Target.java:449) at org.apache.tools.ant.Target.performTasks(Target.java:470) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1388) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:36) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:437) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99) at org.apache.tools.ant.Task.perform(Task.java:350) at org.apache.tools.ant.Target.execute(Target.java:449) at org.apache.tools.ant.Target.performTasks(Target.java:470) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1388) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:36) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:437) at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99) at org.apache.tools.ant.Task.perform(Task.java:350) at org.apache.tools.ant.Target.execute(Target.java:449) at org.apache.tools.ant.Target.performTasks(Target.java:470) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1388) at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:36) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:437) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99) at org.apache.tools.ant.Task.perform(Task.java:350) at org.apache.tools.ant.Target.execute(Target.java:449) at org.apache.tools.ant.Target.performTasks(Target.java:470) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1388) at org.apache.tools.ant.Project.executeTarget(Project.java:1361) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.Main.runBuild(Main.java:834) at org.apache.tools.ant.Main.startAnt(Main.java:223) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101) Caused by: Socket timeout waiting for flexunit report at org.flexunit.ant.FlexUnitSocketServer.start(Unknown Source) at org.flexunit.ant.FlexUnitSocketThread.call(Unknown Source) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.net.SocketTimeoutException: Accept timed out at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method) at java.net.DualStackPlainSocketImpl.socketAccept(DualStackPlainSocketImpl.java:135) at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:199) at java.net.ServerSocket.implAccept(ServerSocket.java:545) at java.net.ServerSocket.accept(ServerSocket.java:513) at org.flexunit.ant.FlexUnitSocketServer.openClientSocket(Unknown Source) ... 6 more Total time: 9 minutes 29 seconds PS D:\dev\royale-emulation-works\github> 28.11.2018 09:31 tarihinde Alex Harui yazdı: Hi Serkan, The nightly build from http://apacheroyaleci.westus2.cloudapp.azure.com:8080<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080&data=02%7C01%7Caharui%40adobe.com%7C66123f39e1a54f68068b08d6560350c0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636790969609029974&sdata=yPXo3bHMkSBjX7s4YZqTzJNGG70tmWwIUixL2zqbL%2B0%3D&reserved=0> uses Ant The Maven nightly builds end up in the snapshot repo eventually. When you run Maven locally, by default it puts the jars in your local Maven repo, but the folder structure and names conform to Maven and are therefore not easily accessed via Ant. This is why I recommend that you pick a workflow that matches ours, so we don't have to spend cycles remembering your configuration is different or that it could be a reason you get different results than we do. Yes, it is probably possible to write a script that transforms the Maven artifacts to Ant, but I really don't want to spend the time figuring it out. By having you use one of the recommended workflows, you help us prove it works or find problems with it that we can improve. If you want to be a committer, it is highly recommended to get all 3 repos as siblings and learn how to build them and your project with either all-Ant or all-Maven. And that should be the most efficient workflow as you don't have to wait for nightly builds to complete. Thanks, -Alex On 11/27/18, 10:23 PM, "[email protected]"<mailto:[email protected]> <[email protected]><mailto:[email protected]> wrote: Hi Alex, I know tha batch file does not change but the jar inside. I was expecting that the batch file points to the latest jar generated in somewhere in one of three repos. Let me make it clear. I am happy with building framework with maven and building my project with ant. I understand that you advise me to choose all-maven or or-ant but i do not think it is neccessary, spesifically for my own project. I just need to know the place of the compiler-jar in the repo after building all three repositories with maven locally rather than donwloading the nigtly builds. Simply, as a summary i would like to know how can i generate nightly build on my local environment ?:) if yes, then it solves all my problems, if no than it is better to wait for the nightly build to be available with latest commits. Any advice appreciated. Thanks, Serkan Alinti Alex Harui <[email protected]><mailto:[email protected]> > I don’t think mxmlc.bat has changed. > > I think you are using some unusual workflow, using Maven to build > SWC and then referencing them from the command-line instead of using > Maven to build the app. IMO, it would be better for you to choose > Maven or not-Maven (Ant and command-line) so you are using one of > our supported workflows, and then we will have a better idea of how > to answer questions like this. > > My 2 cents, > -Alex > > From: Serkan Taş <[email protected]><mailto:[email protected]> > Reply-To: "[email protected]"<mailto:[email protected]> <[email protected]><mailto:[email protected]> > Date: Tuesday, November 27, 2018 at 1:34 PM > To: "[email protected]"<mailto:[email protected]> <[email protected]><mailto:[email protected]> > Subject: Re: build is broken : royale-asjs, mxroyale, sparkroyale > > Hi Alex, > > running mvn sequentially for royale-compiler, royale-typedefs-, > royale-asjs builds are fixed. > > For the latest downloaded release i was using > apache-royale-0.9.5-bin-js-swf\royale-asjs\js\bin\mxmlc.bat for build. > > Which file should i use from repos ? > > Thanks, > Serkan > 27.11.2018 23:58 tarihinde Alex Harui yazdı: > I should really have written: “the latest development version”. > The latest released version will be publicly available. > > The CI server got stuck somehow. We’ll see if the next build works. > Looks like it takes an hour or so on the CI server. Building them > yourself should be faster. > > -Alex > > From: Alex Harui <[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > Reply-To: "[email protected]"<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > <[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > Date: Tuesday, November 27, 2018 at 12:42 PM > To: "[email protected]"<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > <[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > Subject: Re: build is broken : royale-asjs, mxroyale, sparkroyale > > The latest version is not guaranteed to have publicly available > builds, so you have to build them yourself. It is to your advantage > to be able to build them yourself in order to pick up latest changes. > > -Alex > > From: Serkan Taş > <[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > Reply-To: "[email protected]"<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > <[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > Date: Tuesday, November 27, 2018 at 12:38 PM > To: "[email protected]"<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > <[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > Subject: Re: build is broken : royale-asjs, mxroyale, sparkroyale > > > No, royale-asjs also failed, but i did not build the other repositories. > > I am going to follow your advises but, until now, i did not require > any other projects (royale-compiler, royale-typedefs) to build, just > mxroyale and sparkroyale sequentially maven build worked for me, > just for your attention. > > Here are the builds i used : > > MX > set MAVEN_OPTS=-Dfile.encoding=UTF-8 -Duser.country=EN -Duser.language=en > (cd > D:\dev\royale-emulation-works\github\royale-asjs\frameworks\projects\MXRoyale && mvn -DskipTests -Drat.skip=true clean > install) > > SPARK > set MAVEN_OPTS=-Dfile.encoding=UTF-8 -Duser.country=EN -Duser.language=en > (cd > D:\dev\royale-emulation-works\github\royale-asjs\frameworks\projects\SparkRoyale && mvn -DskipTests -Drat.skip=true clean > install) > > Thanks, > Serkan > 27.11.2018 23:17 tarihinde Alex Harui yazdı: > Did the full build of royale-asjs succeed? MXRoyale will not build > until you have built all of its dependencies. > > If you are using Maven, you will need to sync up all 3 repos > (royale-compiler, royale-typedefs-, royale-asjs). > > In each repo in the order above, use “mvn clean install”. > > -Alex > > From: Serkan Taş > <[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > Reply-To: "[email protected]"<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > <[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > Date: Tuesday, November 27, 2018 at 12:13 PM > To: "[email protected]"<mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > <[email protected]><mailto:[email protected]><mailto:[email protected]><mailto:[email protected]> > Subject: build is broken : royale-asjs, mxroyale, sparkroyale > > Hi, > > After version upgrade, i having build issues. MXRoyale, SparkRoyale > and royale-asjs maven build are all broken. > > Here is the output for MXRoyale : > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Fopen%3Fid%3D1jfRezjjJTcVDCt84hkS19WVXGKB5eXX4&data=02%7C01%7Caharui%40adobe.com%7C049b592d7ee84e4e6be808d654fa0d15%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636789830276843297&sdata=0WgHptuI%2BKbRt2jlVkGUwyf9fRUNu3f7icivq1AIeDo%3D&reserved=0<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Fopen%3Fid%3D1jfRezjjJTcVDCt84hkS19WVXGKB5eXX4&data=02%7C01%7Caharui%40adobe.com%7C66123f39e1a54f68068b08d6560350c0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636790969609040001&sdata=dxv%2BdPXYqF6Mv3toQTqa%2Fli8HZeUY%2F7ybvuq%2F670uRc%3D&reserved=0><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Fopen%3Fid%3D1jfRezjjJTcVDCt84hkS19WVXGKB5eXX4&data=02%7C01%7Caharui%40adobe.com%7C049b592d7ee84e4e6be808d654fa0d15%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636789830276843297&sdata=0WgHptuI%2BKbRt2jlVkGUwyf9fRUNu3f7icivq1AIeDo%3D&reserved=0><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Fopen%3Fid%3D1jfRezjjJTcVDCt84hkS19WVXGKB5eXX4&data=02%7C01%7Caharui%40adobe.com%7C66123f39e1a54f68068b08d6560350c0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636790969609040001&sdata=dxv%2BdPXYqF6Mv3toQTqa%2Fli8HZeUY%2F7ybvuq%2F670uRc%3D&reserved=0> > > Any help appreciated. > > Thanks, > Serkan -- Serkan Taş Mobil : +90 532 250 07 71 Likya Bilgi Teknolojileri ve İletişim Hiz. Ltd. Şti. https://na01.safelinks.protection.outlook.com/?url=www.likyateknoloji.com&data=02%7C01%7Caharui%40adobe.com%7C049b592d7ee84e4e6be808d654fa0d15%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636789830276843297&sdata=ozSjP90Sq6txTya%2BfHxqT0vpPGh2u%2Bm3jRp%2BosS4aO4%3D&reserved=0<https://na01.safelinks.protection.outlook.com/?url=www.likyateknoloji.com&data=02%7C01%7Caharui%40adobe.com%7C66123f39e1a54f68068b08d6560350c0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636790969609049988&sdata=StlNHgRf%2BPylJXOVB7doMlFyJHZbiwUBxRdqlBFt7YM%3D&reserved=0> -------------------------------------- Bu elektronik posta ve onunla iletilen bütün dosyalar gizlidir. Sadece yukarıda isimleri belirtilen kişiler arasında özel haberleşme amacını taşımaktadır. Size yanlışlıkla ulaşmışsa bu elektonik postanın içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve kullanmanız kesinlikle yasaktır. Lütfen mesajı geri gönderiniz ve sisteminizden siliniz. Likya Bilgi Teknolojileri ve İletişim Hiz. Ltd. Şti. bu mesajın içeriği ile ilgili olarak hiç bir hukuksal sorumluluğu kabul etmez. This electronic mail and any files transmitted with it are intended for the private use of the persons named above. If you received this message in error, forwarding, copying or use of any of the information is strictly prohibited. Please immediately notify the sender and delete it from your system. Likya Bilgi Teknolojileri ve İletişim Hiz. Ltd. Şti. does not accept legal responsibility for the contents of this message. --------------------------------------
