Works like a charm. I use: asconfigc --debug=true asconfigc --debug=true —watch
and that works beautifully. It takes a bit longer to run the debug script, but it works after a clean and watches just fine. > On Apr 25, 2022, at 1:11 PM, Harbs <harbs.li...@gmail.com> wrote: > > Looks like 1.6 supports it: > https://github.com/BowlerHatLLC/asconfigc/commit/a3209fd88793e66e10059de128431e096fb80e34 > > Correct? > >> On Apr 25, 2022, at 1:06 PM, Harbs <harbs.li...@gmail.com> wrote: >> >> Do you have a way yet to specify -watch to asconfic without including the >> -watch option in the asconfig.json file? >> >> I’d like to add watch to my debug scripts, but I need it to work after clean >> too. >> >>> On Apr 14, 2022, at 7:55 PM, Josh Tynjala <joshtynj...@bowlerhat.dev> wrote: >>> >>> Not sure. I'd need to investigate whether there's any additional >>> post-processing like that. Even if I were to roll back partially to the >>> faster process, that may just re-introduce bugs that we haven't discovered >>> yet. >>> >>> Another thing I can look into is finding a way to wait for the compilation >>> units to finish their work automatically as part of the thread pooling that >>> the compiler uses. Currently, I'm forcing them to finish immediately, one >>> by one, which might actually make the process slower because it may be less >>> parallel. I don't know for sure. >>> >>> -- >>> Josh Tynjala >>> Bowler Hat LLC <https://bowlerhat.dev> >>> >>> >>> On Wed, Apr 13, 2022 at 3:06 PM Harbs <harbs.li...@gmail.com> wrote: >>> >>>> Is there any way to skip the binding piece for files that don’t require it? >>>> >>>>> On Apr 13, 2022, at 10:54 PM, Josh Tynjala <joshtynj...@bowlerhat.dev> >>>> wrote: >>>>> >>>>> Congratulations, Harbs! >>>>> >>>>> My original implementation of --watch was significantly faster. However, >>>>> after I fixed the bug with binding, it got noticeably slower. It seems >>>> that >>>>> some important binding stuff is handled in the getABCBytesRequest() (and >>>>> yes, that's even for JS), so it's not a simple matter of converting the >>>>> simple AST to JS, like I had hoped. >>>>> >>>>> -- >>>>> Josh Tynjala >>>>> Bowler Hat LLC <https://bowlerhat.dev> >>>>> >>>>> >>>>> On Wed, Apr 13, 2022 at 6:30 AM Harbs <harbs.li...@gmail.com> wrote: >>>>> >>>>>> I just tried this. I have a very good reason for not trying earlier this >>>>>> week. I became a grandfather Monday night! :-) >>>>>> >>>>>> It work, but it seems like CSS files are not copied when using `-watch` >>>> in >>>>>> asconfig.json in VS Code. After a clean, the only way I got it to copy >>>> the >>>>>> files was to first remove the watch option and then add it back. >>>>>> >>>>>> I’m not getting the time improvements I was expecting. Subsequent >>>>>> re-compiles are taking between 1/3 and 1/4 the original time. I would >>>> have >>>>>> expected much faster subsequent compile times: >>>>>> >>>>>> The project 'PortedPrintUI' has been successfully compiled. >>>>>> 12.486944484 seconds >>>>>> Watching for file changes in target JSRoyale... >>>>>> File change detected. Recompiling JSRoyale... >>>>>> The project 'PortedPrintUI' has been successfully compiled. >>>>>> 3.371615253 seconds >>>>>> Watching for file changes in target JSRoyale... >>>>>> File change detected. Recompiling JSRoyale... >>>>>> The project 'PortedPrintUI' has been successfully compiled. >>>>>> 2.631352102 seconds >>>>>> Watching for file changes in target JSRoyale... >>>>>> File change detected. Recompiling JSRoyale... >>>>>> The project 'PortedPrintUI' has been successfully compiled. >>>>>> 3.120785055 seconds >>>>>> Watching for file changes in target JSRoyale... >>>>>> File change detected. Recompiling JSRoyale... >>>>>> The project 'PortedPrintUI' has been successfully compiled. >>>>>> 2.664617476 seconds >>>>>> Watching for file changes in target JSRoyale... >>>>>> File change detected. Recompiling JSRoyale... >>>>>> The project 'PortedPrintUI' has been successfully compiled. >>>>>> 4.043423201 seconds >>>>>> >>>>>>> On Apr 10, 2022, at 4:19 AM, Maria Jose Esteve <mjest...@iest.com> >>>>>> wrote: >>>>>>> >>>>>>> With maven, same results as Hugo, the installation phase does not >>>>>> perform or does not finish correctly, for example, the copy of >>>> resources. >>>>>>> I am not familiar with the phases but I ask you.... couldn't it be that >>>>>> after the compilation phase no other phase is executed because the >>>> process >>>>>> does not continue? >>>>>>> >>>>>>> Watching for file changes in target JSRoyale... >>>>>>> >>>>>>> Hiedra >>>>>>> >>>>>>> -----Mensaje original----- >>>>>>> De: Maria Jose Esteve <mjest...@iest.com> >>>>>>> Enviado el: sábado, 9 de abril de 2022 14:23 >>>>>>> Para: dev@royale.apache.org >>>>>>> Asunto: RE: New --watch compiler option >>>>>>> >>>>>>> Something similar happens with maven. I haven't set up the response >>>>>> email yet because my main project is a bit complex and I have too many >>>>>> anomalies and this afternoon I wanted to test it with the >>>> royale-commuinity >>>>>> project which is simpler, although it also has a separate library and >>>>>> application. >>>>>>> It doesn't seem to perform the "copy and rename" step correctly. >>>>>>> In my case it does copy the resources (I have not checked if it copies >>>>>> them all yet) but it does not allow me to launch my main page >>>> "index.aspx" >>>>>> (rename index.html to index.aspx). >>>>>>> >>>>>>> Maybe both anomalies are related. I'll know more when I switch >>>> projects. >>>>>>> >>>>>>> Translated with www.DeepL.com/Translator (free version) >>>>>>> >>>>>>> Hiedra >>>>>>> >>>>>>> -----Mensaje original----- >>>>>>> De: Hugo Ferreira <hferreira...@gmail.com> Enviado el: sábado, 9 de >>>>>> abril de 2022 3:26 >>>>>>> Para: Apache Royale Development <dev@royale.apache.org> >>>>>>> Asunto: Re: New --watch compiler option >>>>>>> >>>>>>> Hi Josh, >>>>>>> >>>>>>> I have found another bug: >>>>>>> >>>>>>> I have the following structure: >>>>>>> src+ >>>>>>> - pt / ... >>>>>>> - resources+ >>>>>>> - images+ >>>>>>> - libs+ >>>>>>> - themes+ >>>>>>> - index-template.html >>>>>>> - styles-dark.css >>>>>>> - styles.css >>>>>>> - styles.less >>>>>>> App.mxml >>>>>>> asconfig.json >>>>>>> >>>>>>> If I clean/delete the bin folder and then build, the resources files >>>>>> (index....html, styles*.css) are not copied and also the content of >>>> themes >>>>>> folder (css files). >>>>>>> >>>>>>> However If I remove the -watch (temporary disable this feature) and >>>>>> build, the files are copied again. >>>>>>> >>>>>>> Hugo Ferreira <hferreira...@gmail.com> escreveu no dia sexta, >>>> 8/04/2022 >>>>>>> à(s) 17:02: >>>>>>> >>>>>>>> Thank you. >>>>>>>> You saved me and the Royale community countless hours of build - >>>>>>>> "wait" - test. >>>>>>>> You removed the "wait" from the equation :) >>>>>>>> >>>>>>>> Josh Tynjala <joshtynj...@bowlerhat.dev> escreveu no dia sexta, >>>>>>>> 8/04/2022 >>>>>>>> à(s) 17:00: >>>>>>>> >>>>>>>>> Thanks, Hugo. That'll be really helpful! >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Josh Tynjala >>>>>>>>> Bowler Hat LLC <https://bowlerhat.dev> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Apr 7, 2022 at 4:40 PM Hugo Ferreira <hferreira...@gmail.com >>>>> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi Josh, >>>>>>>>>> >>>>>>>>>> I just did a few tests and worked flawless in all cases. >>>>>>>>>> >>>>>>>>>> From now on, I will let the -watch parameter activated and let's >>>>>>>>>> see >>>>>>>>> how it >>>>>>>>>> behave on the next few days. >>>>>>>>>> >>>>>>>>>> Thank you for this great improvement. >>>>>>>>>> >>>>>>>>>> Maria Jose Esteve <mjest...@iest.com> escreveu no dia sexta, >>>>>>>>>> 8/04/2022 >>>>>>>>>> à(s) >>>>>>>>>> 00:32: >>>>>>>>>> >>>>>>>>>>> Hi Josh, thx >>>>>>>>>>> I will compile the sdk and come back here with the results. >>>>>>>>>>> >>>>>>>>>>> Hiedra >>>>>>>>>>> >>>>>>>>>>> -----Mensaje original----- >>>>>>>>>>> De: Josh Tynjala <joshtynj...@bowlerhat.dev> Enviado el: jueves, >>>>>>>>>>> 7 de abril de 2022 23:57 >>>>>>>>>>> Para: dev@royale.apache.org >>>>>>>>>>> Asunto: Re: New --watch compiler option >>>>>>>>>>> >>>>>>>>>>> My latest commit to royale-maven-plugin should allow you to add >>>>>>>>> --watch >>>>>>>>>> in >>>>>>>>>>> <additionalCompilerOptions> in your pom.xml. Maven will no longer >>>>>>>>>>> exit >>>>>>>>>> with >>>>>>>>>>> an error when using --watch. It will keep running indefinitely >>>>>>>>>>> until >>>>>>>>> you >>>>>>>>>>> kill the process manually with Ctrl+C. >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Josh Tynjala >>>>>>>>>>> Bowler Hat LLC <https://bowlerhat.dev> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Fri, Apr 1, 2022 at 5:11 AM Maria Jose Esteve >>>>>>>>>>> <mjest...@iest.com> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Does not work with me, other error: >>>>>>>>>>>> >>>>>>>>>>>> The project 'App' has been successfully compiled. >>>>>>>>>>>> [INFO] >>>>>>>>>>>> >>>>>>>>> --------------------------------------------------------------------- >>>>>>>>> - >>>>>>>>>>>> -- [INFO] Reactor Summary for W+Web! 1.0.0-SNAPSHOT: >>>>>>>>>>>> [INFO] >>>>>>>>>>>> [INFO] W+Web! ............................................. >>>>>>>>>>>> SUCCESS >>>>>>>>> [ >>>>>>>>>>>> 0.289 s] >>>>>>>>>>>> [INFO] Royale App And Modules ............................. >>>>>>>>>>>> SUCCESS >>>>>>>>> [ >>>>>>>>>>>> 0.046 s] >>>>>>>>>>>> [INFO] Royale Application ................................. >>>>>>>>>>>> FAILURE >>>>>>>>> [ >>>>>>>>>>>> 57.866 s] >>>>>>>>>>>> [INFO] Royale Libs ........................................ >>>>>>>>>>>> SKIPPED [INFO] >>>>>>>>>>>> >>>>>>>>> --------------------------------------------------------------------- >>>>>>>>> - >>>>>>>>>>>> -- >>>>>>>>>>>> [INFO] BUILD FAILURE >>>>>>>>>>>> [INFO] >>>>>>>>>>>> >>>>>>>>> --------------------------------------------------------------------- >>>>>>>>> - >>>>>>>>>>>> -- >>>>>>>>>>>> [INFO] Total time: 01:00 min >>>>>>>>>>>> [INFO] Finished at: 2022-04-01T14:06:24+02:00 [INFO] >>>>>>>>>>>> >>>>>>>>> --------------------------------------------------------------------- >>>>>>>>> - >>>>>>>>>>>> -- >>>>>>>>>>>> [ERROR] Failed to execute goal >>>>>>>>>>>> >>>>>>>>> org.apache.royale.compiler:royale-maven-plugin:0.9.10-SNAPSHOT:compil >>>>>>>>> e >>>>>>>>>>>> -app >>>>>>>>>>>> (default-compile-app) on project royalelogin: There were errors >>>>>>>>> during >>>>>>>>>>>> the build. Got return code 1000 -> [Help 1] >>>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed >>>>>>>>>>>> to execute goal >>>>>>>>>>>> >>>>>>>>> org.apache.royale.compiler:royale-maven-plugin:0.9.10-SNAPSHOT:compil >>>>>>>>> e >>>>>>>>>>>> -app >>>>>>>>>>>> (default-compile-app) on project royalelogin: There were errors >>>>>>>>> during >>>>>>>>>>>> the build. Got return code 1000 >>>>>>>>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>>>>>>>>>>> (MojoExecutor.java:215) >>>>>>>>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>>>>>>>>>>> (MojoExecutor.java:156) >>>>>>>>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>>>>>>>>>>> (MojoExecutor.java:148) >>>>>>>>>>>> at >>>>>>>>>>>> >>>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje >>>>>>>>> c >>>>>>>>>>>> t >>>>>>>>>>>> (LifecycleModuleBuilder.java:117) >>>>>>>>>>>> at >>>>>>>>>>>> >>>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje >>>>>>>>> c >>>>>>>>>>>> t >>>>>>>>>>>> (LifecycleModuleBuilder.java:81) >>>>>>>>>>>> at >>>>>>>>>>>> >>>>>>>>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThre >>>>>>>>> a >>>>>>>>>>>> dedBuilder.build >>>>>>>>>>>> (SingleThreadedBuilder.java:56) >>>>>>>>>>>> at >>>>>>>>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute >>>>>>>>>>>> (LifecycleStarter.java:128) >>>>>>>>>>>> at org.apache.maven.DefaultMaven.doExecute >>>>>>>>> (DefaultMaven.java:305) >>>>>>>>>>>> at org.apache.maven.DefaultMaven.doExecute >>>>>>>>> (DefaultMaven.java:192) >>>>>>>>>>>> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) >>>>>>>>>>>> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) >>>>>>>>>>>> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) >>>>>>>>>>>> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) >>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) >>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke >>>>>>>>>>>> (NativeMethodAccessorImpl.java:62) >>>>>>>>>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke >>>>>>>>>>>> (DelegatingMethodAccessorImpl.java:43) >>>>>>>>>>>> at java.lang.reflect.Method.invoke (Method.java:498) >>>>>>>>>>>> at >>>>>>>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhance >>>>>>>>>>>> d >>>>>>>>>>>> (Launcher.java:282) >>>>>>>>>>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch >>>>>>>>>>>> (Launcher.java:225) >>>>>>>>>>>> at >>>>>>>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitC >>>>>>>>>>>> ode >>>>>>>>>>>> (Launcher.java:406) >>>>>>>>>>>> at org.codehaus.plexus.classworlds.launcher.Launcher.main >>>>>>>>>>>> (Launcher.java:347) >>>>>>>>>>>> Caused by: org.apache.maven.plugin.MojoExecutionException: >>>>>>>>>>>> There >>>>>>>>> were >>>>>>>>>>>> errors during the build. Got return code 1000 >>>>>>>>>>>> at org.apache.royale.maven.BaseMojo.handleExitCode >>>>>>>>>>> (BaseMojo.java:390) >>>>>>>>>>>> at org.apache.royale.maven.BaseMojo.execute (BaseMojo.java:384) >>>>>>>>>>>> at org.apache.royale.maven.CompileAppMojo.execute >>>>>>>>>>>> (CompileAppMojo.java:112) >>>>>>>>>>>> at >>>>>>>>>>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo >>>>>>>>>>>> (DefaultBuildPluginManager.java:137) >>>>>>>>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>>>>>>>>>>> (MojoExecutor.java:210) >>>>>>>>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>>>>>>>>>>> (MojoExecutor.java:156) >>>>>>>>>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>>>>>>>>>>> (MojoExecutor.java:148) >>>>>>>>>>>> at >>>>>>>>>>>> >>>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje >>>>>>>>> c >>>>>>>>>>>> t >>>>>>>>>>>> (LifecycleModuleBuilder.java:117) >>>>>>>>>>>> at >>>>>>>>>>>> >>>>>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje >>>>>>>>> c >>>>>>>>>>>> t >>>>>>>>>>>> (LifecycleModuleBuilder.java:81) >>>>>>>>>>>> at >>>>>>>>>>>> >>>>>>>>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThre >>>>>>>>> a >>>>>>>>>>>> dedBuilder.build >>>>>>>>>>>> (SingleThreadedBuilder.java:56) >>>>>>>>>>>> at >>>>>>>>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute >>>>>>>>>>>> (LifecycleStarter.java:128) >>>>>>>>>>>> at org.apache.maven.DefaultMaven.doExecute >>>>>>>>> (DefaultMaven.java:305) >>>>>>>>>>>> at org.apache.maven.DefaultMaven.doExecute >>>>>>>>> (DefaultMaven.java:192) >>>>>>>>>>>> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) >>>>>>>>>>>> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) >>>>>>>>>>>> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) >>>>>>>>>>>> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) >>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) >>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke >>>>>>>>>>>> (NativeMethodAccessorImpl.java:62) >>>>>>>>>>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke >>>>>>>>>>>> (DelegatingMethodAccessorImpl.java:43) >>>>>>>>>>>> at java.lang.reflect.Method.invoke (Method.java:498) >>>>>>>>>>>> at >>>>>>>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhance >>>>>>>>>>>> d >>>>>>>>>>>> (Launcher.java:282) >>>>>>>>>>>> at org.codehaus.plexus.classworlds.launcher.Launcher.launch >>>>>>>>>>>> (Launcher.java:225) >>>>>>>>>>>> at >>>>>>>>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitC >>>>>>>>>>>> ode >>>>>>>>>>>> (Launcher.java:406) >>>>>>>>>>>> at org.codehaus.plexus.classworlds.launcher.Launcher.main >>>>>>>>>>>> (Launcher.java:347) >>>>>>>>>>>> [ERROR] >>>>>>>>>>>> [ERROR] >>>>>>>>>>>> [ERROR] For more information about the errors and possible >>>>>>>>> solutions, >>>>>>>>>>>> please read the following articles: >>>>>>>>>>>> [ERROR] [Help 1] >>>>>>>>>>>> >>>>>>>>> >>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionExcepti >>>>>>>>> o >>>>>>>>>>>> n >>>>>>>>>>>> [ERROR] >>>>>>>>>>>> [ERROR] After correcting the problems, you can resume the build >>>>>>>>>>>> with the command >>>>>>>>>>>> [ERROR] mvn <args> -rf :royalelogin >>>>>>>>>>>> Watching for file changes in target JSRoyale... >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Hiedra >>>>>>>>>>>> >>>>>>>>>>>> -----Mensaje original----- >>>>>>>>>>>> De: Maria Jose Esteve <mjest...@iest.com> Enviado el: viernes, >>>>>>>>>>>> 1 de abril de 2022 12:08 >>>>>>>>>>>> Para: dev@royale.apache.org >>>>>>>>>>>> Asunto: RE: New --watch compiler option >>>>>>>>>>>> >>>>>>>>>>>> Forget you, I compiled the SDK last night but not this morning.... >>>>>>>>>>>> Sorry for the noise. I'll compile and come back here with the >>>>>>>>> results. >>>>>>>>>>>> >>>>>>>>>>>> Hiedra >>>>>>>>>>>> >>>>>>>>>>>> -----Mensaje original----- >>>>>>>>>>>> De: Maria Jose Esteve <mjest...@iest.com> Enviado el: viernes, >>>>>>>>>>>> 1 de abril de 2022 11:38 >>>>>>>>>>>> Para: dev@royale.apache.org >>>>>>>>>>>> Asunto: RE: New --watch compiler option >>>>>>>>>>>> >>>>>>>>>>>> This is great, let's try it and debug it.... >>>>>>>>>>>> - I added it in the "<additionalCompilerOptions>" section of >>>>>>>>>>>> the pom.xml of the application and I get the message: >>>>>>>>>>>> >>>>>>>>>>>> Error: configuration variable 'debug' must be true if >>>>>>>>>>>> configuration variable 'watch' is true. >>>>>>>>>>>> >>>>>>>>>>>> - I activate debug, in the library and in the application and I >>>>>>>>>>>> get the error " Got return code 1000": >>>>>>>>>>>> >>>>>>>>>>>> [INFO] --- royale-maven-plugin:0.9.10-SNAPSHOT:compile-app >>>>>>>>>>>> (default-compile-app) @ royalelogin --- [INFO] Executing MXMLC >>>>>>>>>>>> in >>>>>>>>> tool >>>>>>>>>>>> group Royale with args: >>>>>>>>>>>> >>>>>>>>> [-load-config=D:\Develop_Royale\Projects\WinPlusWebSuite\royaleapp\ro >>>>>>>>> y >>>>>>>>>>>> alelogin\target\compile-app-config.xml, >>>>>>>>>>>> -js-default-initializers=true, -source-map=true, --watch, >>>>>>>>>>>> -js-dynamic-access-unknown-members=true, >>>>>>>>>>>> >>>>>>>>> -keep-as3-metadata+=Inject,Dispatcher,EventHandler,Event,PostConstruc >>>>>>>>> -keep-as3-metadata+t >>>>>>>>>>>> >>>>>>>>> -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transie >>>>>>>>> -keep-as3-metadata+n >>>>>>>>>>>> -keep-as3-metadata+t, >>>>>>>>>>>> -keep-code-with-metadata=Inject, -show-binding-warnings=false, >>>>>>>>>>>> -export-public-symbols=false, >>>>>>>>> -prevent-rename-protected-symbols=false, >>>>>>>>>>>> -prevent-rename-internal-symbols=false, >>>>>>>>>>>> >>>>>>>>> -js-output=D:\Develop_Royale\Projects\WinPlusWebSuite\royaleapp\royal >>>>>>>>> e >>>>>>>>>>>> login\target\javascript, >>>>>>>>>>>> -compiler.targets=JSRoyale, >>>>>>>>>>>> >>>>>>>>> D:\Develop_Royale\Projects\WinPlusWebSuite\royaleapp\royalelogin\src\ >>>>>>>>> m >>>>>>>>>>>> ain\royale\App.mxml] The project 'App' has been successfully >>>>>>>>> compiled. >>>>>>>>>>>> [INFO] >>>>>>>>>>>> >>>>>>>>> --------------------------------------------------------------------- >>>>>>>>> - >>>>>>>>>>>> -- [INFO] Reactor Summary for W+Web! 1.0.0-SNAPSHOT: >>>>>>>>>>>> [INFO] >>>>>>>>>>>> [INFO] W+Web! ............................................. >>>>>>>>>>>> SUCCESS >>>>>>>>> [ >>>>>>>>>>>> 0.098 s] [INFO] Royale Libs >>>> ........................................ >>>>>>>>>>>> SUCCESS [ 0.038 s] [INFO] Royale Libs Custom Theme >>>>>>>>>>>> ........................... SUCCESS [ 3.488 s] [INFO] Royale >>>>>>>>>>>> Lib Component ECharts ....................... SUCCESS [ 2.868 >>>>>>>>>>>> s] [INFO] Royale Libs Arq .................................... >>>>>>>>>>>> SUCCESS [ >>>>>>>>> 2.025 >>>>>>>>>>>> s] [INFO] Royale Libs Commons ................................ >>>>>>>>> SUCCESS >>>>>>>>>>>> [ 2.853 s] Watching for file changes in target JSRoyale... >>>>>>>>>>>> [INFO] Royale Libs DTO .................................... >>>>>>>>>>>> SUCCESS >>>>>>>>> [ >>>>>>>>>>>> 2.513 s] [INFO] Royale Libs Shell >>>> .................................. >>>>>>>>>>>> SUCCESS [ 1.680 s] [INFO] Royale Libs Components >>>>>>>>>>>> ............................. SUCCESS [ 10.894 s] [INFO] Royale >>>>>>>>>>>> Libs Jscalendar ............................. SUCCESS [ 12.008 >>>>>>>>>>>> s] [INFO] Royale Lib Component InspireTree ................... >>>>>>>>>>>> SUCCESS [ >>>>>>>>> 10.880 >>>>>>>>>>>> s] [INFO] Royale Lib Component Mobiscroll .................... >>>>>>>>> SUCCESS >>>>>>>>>>>> [ 1.715 s] [INFO] Royale Libs Security >>>>>>>>>>>> ............................... SUCCESS [ >>>>>>>>>>>> 1.984 s] [INFO] Royale Libs ConfigSystem >>>> ........................... >>>>>>>>>>>> SUCCESS [ 1.949 s] [INFO] Royale Libs Personal >>>>>>>>>>>> ............................... SUCCESS [ 1.927 s] [INFO] >>>>>>>>>>>> Royale >>>>>>>>> Libs >>>>>>>>>>>> Horarios ............................... SUCCESS [ 1.819 s] >>>>>>>>>>>> [INFO] Royale Libs Perfiles Horarios ...................... >>>>>>>>>>>> SUCCESS [ >>>>>>>>> 1.805 >>>>>>>>>>>> s] [INFO] Royale Libs Fichajes ............................... >>>>>>>>> SUCCESS >>>>>>>>>>>> [ 1.720 s] [INFO] Royale Libs Config >>>>>>>>>>>> ................................. SUCCESS [ >>>>>>>>>>>> 1.714 s] [INFO] Royale App And Modules >>>> ............................. >>>>>>>>>>>> SUCCESS [ 0.008 s] [INFO] Royale Application >>>>>>>>>>>> ................................. FAILURE [ 18.214 s] [INFO] >>>>>>>>>>>> >>>>>>>>> --------------------------------------------------------------------- >>>>>>>>> - >>>>>>>>>>>> -- >>>>>>>>>>>> [INFO] BUILD FAILURE >>>>>>>>>>>> [INFO] >>>>>>>>>>>> >>>>>>>>> --------------------------------------------------------------------- >>>>>>>>> - >>>>>>>>>>>> -- >>>>>>>>>>>> [INFO] Total time: 01:23 min >>>>>>>>>>>> [INFO] Finished at: 2022-04-01T10:14:25+02:00 [INFO] >>>>>>>>>>>> >>>>>>>>> --------------------------------------------------------------------- >>>>>>>>> - >>>>>>>>>>>> -- >>>>>>>>>>>> [ERROR] Failed to execute goal >>>>>>>>>>>> >>>>>>>>> org.apache.royale.compiler:royale-maven-plugin:0.9.10-SNAPSHOT:compil >>>>>>>>> e >>>>>>>>>>>> -app >>>>>>>>>>>> (default-compile-app) on project royalelogin: There were errors >>>>>>>>> during >>>>>>>>>>>> the build. Got return code 1000 -> [Help 1] >>>>>>>>>>>> >>>>>>>>>>>> If I launch the compilation with the detailed debugging, -e -X, >>>>>>>>>>>> to file [1]. It shows: >>>>>>>>>>>> >>>>>>>>>>>> Exception in thread "Thread-3" Exception in thread "Thread-3" >>>>>>>>>>>> java.lang.NoClassDefFoundError: >>>>>>>>>>>> org/apache/royale/compiler/internal/watcher/WatchThread$1 >>>>>>>>>>>> at >>>>>>>>>>>> >>>>>>>>> org.apache.royale.compiler.internal.watcher.WatchThread.watchPath(Wat >>>>>>>>> c >>>>>>>>>>>> hThread.java:262) >>>>>>>>>>>> >>>>>>>>>>>> at >>>>>>>>>>>> >>>>>>>>> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThre >>>>>>>>> a >>>>>>>>>>>> d.java:130) Caused by: java.lang.ClassNotFoundException: >>>>>>>>>>>> org.apache.royale.compiler.internal.watcher.WatchThread$1 >>>>>>>>>>>> at >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass( >>>>>>>>> SelfFirstStrategy.java:50) >>>>>>>>>>>> at >>>>>>>>>>>> >>>>>>>>> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadCl >>>>>>>>> a >>>>>>>>>>>> ss(ClassRealm.java:271) >>>>>>>>>>>> >>>>>>>>>>>> at >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm >>>>>>>>> .java:247) >>>>>>>>>>>> at >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm >>>>>>>>> .java:239) >>>>>>>>>>>> ... 2 more >>>>>>>>>>>> >>>>>>>>>>>> [1] >>>>>>>>>>>> >>>>>>>>> >>>> https://drive.google.com/file/d/18CC4_6XQ4YwJujTyBLwqpkg5q6oTfXvy/vie >>>>>>>>> w >>>>>>>>>>>> ?usp=sharing >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Hiedra >>>>>>>>>>>> >>>>>>>>>>>> -----Mensaje original----- >>>>>>>>>>>> De: Josh Tynjala <joshtynj...@bowlerhat.dev> Enviado el: >>>>>>>>>>>> jueves, >>>>>>>>> 31 de >>>>>>>>>>>> marzo de 2022 23:49 >>>>>>>>>>>> Para: dev@royale.apache.org; romanisi...@yahoo.com >>>>>>>>>>>> Asunto: Re: New --watch compiler option >>>>>>>>>>>> >>>>>>>>>>>> It should be in 0.9.10-SNAPSHOT (or will be when the next Maven >>>>>>>>>>>> nightly build completes). To use this option with Maven, I >>>>>>>>>>>> assume >>>>>>>>> that >>>>>>>>>>>> you can add --watch to the section of your pom.xml where you >>>>>>>>>>>> can specify additional compiler options. I'm not familiar >>>>>>>>>>>> enough with >>>>>>>>> the >>>>>>>>>>>> Maven plugin to tell you exactly where that is. >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Josh Tynjala >>>>>>>>>>>> Bowler Hat LLC <https://bowlerhat.dev> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Mar 31, 2022 at 2:42 PM romanisi...@yahoo.com.INVALID >>>>>>>>>>>> <romanisi...@yahoo.com.invalid> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> This is a nice feature. Is it part of the new 0.9.9 release ? >>>>>>>>>>>>> Or Which snapshot version ? >>>>>>>>>>>>> >>>>>>>>>>>>> Also just to clarify usage. I use maven so will the usage be >>>>>>>>>>>>> as follows mvn clean watch install ? >>>>>>>>>>>>> How can I use it in a royale maven project ? >>>>>>>>>>>>> >>>>>>>>>>>>> Sent from Yahoo Mail on Android >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, 31 Mar 2022 at 22:34, Josh Tynjala< >>>>>>>>>> joshtynj...@bowlerhat.dev >>>>>>>>>>>> >>>>>>>>>>>>> wrote: Hi all, >>>>>>>>>>>>> >>>>>>>>>>>>> I just pushed a commit to royale-compiler that adds a new >>>>>>>>>>>>> --watch compiler option. What this new option does is keep >>>>>>>>>>>>> the compiler running after it's done, watching the >>>>>>>>>>>>> source-path folders for any changes to .as and .mxml files. >>>>>>>>>>>>> When changes are detected, it will automatically re-compile >>>>>>>>>>>>> your project. Best of all, it's an incremental re-compile, so it >>>>>> will be significantly faster. >>>>>>>>>>>>> >>>>>>>>>>>>> For projects targeting JS, all you need to do is refresh your >>>>>>>>>>>>> browser after the re-compile completes. You can even use a >>>>>>>>>>>>> tool >>>>>>>>> that >>>>>>>>>>>>> does this automatically, if you prefer. >>>>>>>>>>>>> >>>>>>>>>>>>> After a quick search on Google, I found the "reload" npm >>>>>>>>>>>>> package, and I can confirm that it can automatically reload a >>>>>>>>>>>>> Royale app after >>>>>>>>>>>> recompilation. >>>>>>>>>>>>> Here is the command that I used in a terminal at the root of >>>>>>>>>>>>> my project >>>>>>>>>>>>> folder: >>>>>>>>>>>>> >>>>>>>>>>>>> npx reload -d bin/js-debug -b >>>>>>>>>>>>> >>>>>>>>>>>>> This starts a local HTTP server in the directory >>>>>>>>>>>>> bin/js-debug, and it launches the app in a browser. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>> https://www.npmjs.com/package/reload#user-content-using-reload-as-a- >>>>>>>>>>>>> co >>>>>>>>>>>>> mmand-line-application >>>>>>>>>>>>> >>>>>>>>>>>>> The new --watch compiler option works with SWF too. However, >>>>>>>>>>>>> I'm >>>>>>>>> not >>>>>>>>>>>>> aware of any automatic reloading tools for this, so you'll >>>>>>>>>>>>> just >>>>>>>>> need >>>>>>>>>>>>> to close and relaunch manually. >>>>>>>>>>>>> >>>>>>>>>>>>> Please give it a try, and let me know if you run into any issues. >>>>>>>>>>>>> I'd like to see how well it works with some bigger projects! >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Josh Tynjala >>>>>>>>>>>>> Bowler Hat LLC <https://bowlerhat.dev> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>> >>>> >> >
