You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Josh Tynjala <jo...@bowlerhat.dev> on 2022/03/31 21:34:07 UTC
New --watch compiler option
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-command-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>
Re: New --watch compiler option
Posted by Josh Tynjala <jo...@bowlerhat.dev>.
The Git commit is in the royale-compiler repo.
https://github.com/apache/royale-compiler/commit/42642e2089f7a21773c914828696ae6821605125
--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>
On Thu, Mar 31, 2022 at 2:42 PM Hugo Ferreira <hf...@gmail.com>
wrote:
> Uou. This is very cool.
> It's almost like hotreload and will increase produtivity.
> I spent a lot of time compiling.
>
> I just checked Royale git and I don't see your commit.
>
> Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia quinta,
> 31/03/2022
> à(s) 22:34:
>
> > 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-command-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>
> >
>
Re: New --watch compiler option
Posted by Hugo Ferreira <hf...@gmail.com>.
Uou. This is very cool.
It's almost like hotreload and will increase produtivity.
I spent a lot of time compiling.
I just checked Royale git and I don't see your commit.
Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia quinta, 31/03/2022
à(s) 22:34:
> 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-command-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>
>
Re: New --watch compiler option
Posted by Harbs <ha...@gmail.com>.
Thanks Josh for working on this!
I plan on testing this during the coming week.
I already use https://marketplace.visualstudio.com/items?itemName=ritwickdey.LiveServer
So, theoretically, my app should automatically update on save...
> On Apr 1, 2022, at 12:34 AM, Josh Tynjala <jo...@bowlerhat.dev> wrote:
>
> I just pushed a commit to royale-compiler that adds a new --watch compiler
> option.
Re: New --watch compiler option
Posted by Edward Stangler <es...@bradmark.com>.
It's magical.
It would be nice if it could continue to watch after a compile error on
the first (initial) compile (or provide an option for that behavior).
On a larger project, simple changes (multiple files at once) looking
good so far.
Would also be nice if at least one compile (fatal) error could be shown
by reload in the browser, like some other tools do.
On 3/31/2022 4:35 PM, Josh Tynjala 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-command-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>
>
Re: New --watch compiler option
Posted by Hugo Ferreira <hf...@gmail.com>.
Thank you.
You did a great job with this change.
It's a change with giant impact.
Be able to code and refresh on the browser it's one of the most productive
features from the last years.
No wonder Flutter got popular when present this feature and then many other
frameworks and IDE's is using this feature.
Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia sexta, 1/04/2022
à(s) 23:00:
> Thanks, Hugo. I'll investigate the issue with binding.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Fri, Apr 1, 2022 at 2:57 PM Hugo Ferreira <hf...@gmail.com>
> wrote:
>
> > Thank you Maria and thank you Josh.
> >
> > It's working now but for simple changes.
> >
> > The first test worked like a charm.
> >
> > Changing from:
> > <c:FormItem label="Code"
> >
> > To:
> > <c:FormItem label="Code 2"
> >
> > Refresh on the browser and I see the change like magic.
> >
> > However something more complex with a data binding and I get a messy
> > result.
> >
> > Changing from:
> > <models:Menu Text="{localeManager.localeStrings.MenuAdminCompany}"/>
> >
> > To:
> > <models:Menu Text="{localeManager.localeStrings.MenuAdminUsers}"/>
> >
> > The result is a messy result on the browser with 0 errors on the console
> (I
> > tested with other kind of data bindings and it's the same result).
> > Also if I change from a data binding to a fixed test, I got the same
> messy
> > results.
> >
> > <models:Menu Text="Test"/> => The same messing result on the browser and
> > the solution is to manually rebuild.
> >
> > Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta, 1/04/2022
> > à(s)
> > 22:14:
> >
> > > Hi Hugo,
> > > You can set it in the workspace file or from vsCode:
> > > - workspace file: (myproject.code-workspace)
> > > {
> > > "folders": [
> > > {
> > > "path": "projectXXXX"
> > > }
> > > ],
> > > "settings": {
> > > "as3mxml.sdk.framework":
> > > "d:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs",
> > > "as3mxml.sdk.editor":
> > > "D:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs"
> > > <------------------------------ HERE ****************
> > > }
> > > }
> > >
> > > - vsCode:
> > > - You can edit manually the file "settings.json" [1] (in
> Windows
> > > it is in C:\Users\hiedra\AppData\Roaming\Code\User\settings.json)
> > > - or from the IDE (File/Preferences/Settings) [2].
> > >
> > > [1]
> > >
> >
> https://drive.google.com/file/d/1SE-29sJc08tXV5-GMBabPJJWGRfyj4u0/view?usp=sharing
> > > [2]
> > >
> >
> https://drive.google.com/file/d/1nyC0JyHdD8441nEBks-mwIeElVs41tZQ/view?usp=sharing
> > >
> > > Hiedra
> > >
> > > -----Mensaje original-----
> > > De: Hugo Ferreira <hf...@gmail.com>
> > > Enviado el: viernes, 1 de abril de 2022 21:44
> > > Para: Apache Royale Development <de...@royale.apache.org>
> > > Asunto: Re: New --watch compiler option
> > >
> > > Where is the as3mxml.sdk.editor file ?
> > > I didn't find it (macOS)
> > >
> > >
> > > Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia sexta,
> > 1/04/2022
> > > à(s) 16:52:
> > >
> > > > If you're going to add -watch to asconfig.json, you'll also need to
> > > > update the as3mxml.sdk.editor setting in VSCode to the path of your
> > > > new Royale SDK. vscode-as3mxml bundles Royale 0.9.8, so it doesn't
> > > > know anything about -watch, but as3mxml.sdk.editor lets it use a
> > > > custom SDK for code intelligence purposes.
> > > >
> > > > In a future update, vscode-as3mxml will have a built-in watch task so
> > > > that you won't need to modify asconfig.json. I have it working in a
> > > > branch right now.
> > > >
> > > > --
> > > > Josh Tynjala
> > > > Bowler Hat LLC <https://bowlerhat.dev>
> > > >
> > > >
> > > > On Fri, Apr 1, 2022 at 3:48 AM Hugo Ferreira <hferreira.80@gmail.com
> >
> > > > wrote:
> > > >
> > > > > Does not work with me:
> > > > >
> > > > > asconfig.json:
> > > > > {
> > > > > "config": "royale",
> > > > > "copySourcePathAssets": true,
> > > > > "compilerOptions": {
> > > > > "debug": false,
> > > > > "targets": ["JSRoyale"],
> > > > > "source-map": true,
> > > > > "html-template": "src/resources/index-template.html",
> > > > > "js-library-path": [
> > > > > "${royalelib}/js/libs/MXRoyaleJS.swc"
> > > > > ]
> > > > > },
> > > > > "additionalOptions": "-watch -remove-circulars
> > > > > -js-output-optimization=skipAsCoercions
> > > > >
> -compiler.exclude-defaults-css-files=MXRoyale-0.9.10-js.swc:defaults
> > > > > .css
> > > > > -keep-as3-metadata+=Transient",
> > > > > "files":
> > > > > [
> > > > > "src/App.mxml"
> > > > > ]
> > > > > }
> > > > >
> > > > > VS Code - Problems:
> > > > > unknown configuration variable 'watch'.
> > > > >
> > > > >
> > > > > Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta,
> > > > > 1/04/2022
> > > > > à(s)
> > > > > 11:08:
> > > > >
> > > > > > 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 <mj...@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\roy
> > > > 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,PostConstruct
> > > >
> -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transien
> > > > -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\royale
> > > > 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:compile
> > > > -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(Watc
> > > > hThread.java:262)
> > > > > >
> > > > > > at
> > > > > >
> > > > >
> > > >
> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThrea
> > > > d.java:130)
> > > > > > Caused by: java.lang.ClassNotFoundException:
> > > > > > org.apache.royale.compiler.internal.watcher.WatchThread$1
> > > > > > at
> > > > > >
> > > > >
> > > >
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(S
> > > > elfFirstStrategy.java:50)
> > > > > > at
> > > > > >
> > > > >
> > > >
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadCla
> > > > 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/view
> > > > ?usp=sharing
> > > > > >
> > > > > >
> > > > > > Hiedra
> > > > > >
> > > > > > -----Mensaje original-----
> > > > > > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves,
> > > > > > 31 de marzo de 2022 23:49
> > > > > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> > > > > > <ro...@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<
> > > > joshtynjala@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>
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
RE: New --watch compiler option
Posted by Yishay Weiss <yi...@hotmail.com>.
Yup, fixed DataBindingExample, and can confirm <additionalCompilerOptions>--watch</additionalCompilerOptions> works.
From: Josh Tynjala<ma...@bowlerhat.dev>
Sent: Friday, April 8, 2022 1:07 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: New --watch compiler option
Hugo and Yishay,
My latest compiler commits should fix the issue with broken binding after
file changes. Please give it another try, and let me know if you
encounter any other problems.
--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>
On Sat, Apr 2, 2022 at 2:03 AM Yishay Weiss <yi...@hotmail.com> wrote:
> Thanks for doing this, could make a huge difference for our client.
>
> I can confirm DataBindingExample does not work well with this option.
>
> Changing MyInitivalView:139 to
>
> <js:RadioButton id="radio1"
> text="Price222" value="Ask" groupName="group1"
> change="radioChanged(event)"/>
>
> Creates the following stack trace after refresh
>
> ArraySelectionModel.js:184 Uncaught TypeError: Cannot read properties of
> undefined (reading 'length')
> at
> org.apache.royale.html.beads.models.ArraySelectionModel.set__selectedItem
> (ArraySelectionModel.js:184:109)
> at org.apache.royale.html.DropDownList.set__selectedItem
> (DropDownList.js:138:27)
> at MyInitialView.MyInitialView_initControls (MyInitialView.js:386:26)
> at MyInitialView.$EH_10_0 (MyInitialView.js:472:8)
> at
> MyInitialView.org.apache.royale.events.EventDispatcher.fireListeners
> (EventDispatcher.js:102:23)
> at Function.goog.events.EventTarget.dispatchEventInternal_
> (eventtarget.js:382:26)
> at
> MyInitialView.org.apache.royale.events.EventDispatcher.dispatchEvent
> (EventDispatcher.js:77:37)
> at MyInitialView.org.apache.royale.core.ElementWrapper.dispatchEvent
> (ElementWrapper.js:223:76)
> at Object.org.apache.royale.utils.sendEvent (sendEvent.js:27:21)
> at MyInitialView.org.apache.royale.core.View.addedToParent
> (View.js:64:29)
>
> From: Josh Tynjala<ma...@bowlerhat.dev>
> Sent: Saturday, April 2, 2022 1:00 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: New --watch compiler option
>
> Thanks, Hugo. I'll investigate the issue with binding.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Fri, Apr 1, 2022 at 2:57 PM Hugo Ferreira <hf...@gmail.com>
> wrote:
>
> > Thank you Maria and thank you Josh.
> >
> > It's working now but for simple changes.
> >
> > The first test worked like a charm.
> >
> > Changing from:
> > <c:FormItem label="Code"
> >
> > To:
> > <c:FormItem label="Code 2"
> >
> > Refresh on the browser and I see the change like magic.
> >
> > However something more complex with a data binding and I get a messy
> > result.
> >
> > Changing from:
> > <models:Menu Text="{localeManager.localeStrings.MenuAdminCompany}"/>
> >
> > To:
> > <models:Menu Text="{localeManager.localeStrings.MenuAdminUsers}"/>
> >
> > The result is a messy result on the browser with 0 errors on the console
> (I
> > tested with other kind of data bindings and it's the same result).
> > Also if I change from a data binding to a fixed test, I got the same
> messy
> > results.
> >
> > <models:Menu Text="Test"/> => The same messing result on the browser and
> > the solution is to manually rebuild.
> >
> > Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta, 1/04/2022
> > à(s)
> > 22:14:
> >
> > > Hi Hugo,
> > > You can set it in the workspace file or from vsCode:
> > > - workspace file: (myproject.code-workspace)
> > > {
> > > "folders": [
> > > {
> > > "path": "projectXXXX"
> > > }
> > > ],
> > > "settings": {
> > > "as3mxml.sdk.framework":
> > > "d:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs",
> > > "as3mxml.sdk.editor":
> > > "D:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs"
> > > <------------------------------ HERE ****************
> > > }
> > > }
> > >
> > > - vsCode:
> > > - You can edit manually the file "settings.json" [1] (in
> Windows
> > > it is in C:\Users\hiedra\AppData\Roaming\Code\User\settings.json)
> > > - or from the IDE (File/Preferences/Settings) [2].
> > >
> > > [1]
> > >
> >
> https://drive.google.com/file/d/1SE-29sJc08tXV5-GMBabPJJWGRfyj4u0/view?usp=sharing
> > > [2]
> > >
> >
> https://drive.google.com/file/d/1nyC0JyHdD8441nEBks-mwIeElVs41tZQ/view?usp=sharing
> > >
> > > Hiedra
> > >
> > > -----Mensaje original-----
> > > De: Hugo Ferreira <hf...@gmail.com>
> > > Enviado el: viernes, 1 de abril de 2022 21:44
> > > Para: Apache Royale Development <de...@royale.apache.org>
> > > Asunto: Re: New --watch compiler option
> > >
> > > Where is the as3mxml.sdk.editor file ?
> > > I didn't find it (macOS)
> > >
> > >
> > > Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia sexta,
> > 1/04/2022
> > > à(s) 16:52:
> > >
> > > > If you're going to add -watch to asconfig.json, you'll also need to
> > > > update the as3mxml.sdk.editor setting in VSCode to the path of your
> > > > new Royale SDK. vscode-as3mxml bundles Royale 0.9.8, so it doesn't
> > > > know anything about -watch, but as3mxml.sdk.editor lets it use a
> > > > custom SDK for code intelligence purposes.
> > > >
> > > > In a future update, vscode-as3mxml will have a built-in watch task so
> > > > that you won't need to modify asconfig.json. I have it working in a
> > > > branch right now.
> > > >
> > > > --
> > > > Josh Tynjala
> > > > Bowler Hat LLC <https://bowlerhat.dev>
> > > >
> > > >
> > > > On Fri, Apr 1, 2022 at 3:48 AM Hugo Ferreira <hferreira.80@gmail.com
> >
> > > > wrote:
> > > >
> > > > > Does not work with me:
> > > > >
> > > > > asconfig.json:
> > > > > {
> > > > > "config": "royale",
> > > > > "copySourcePathAssets": true,
> > > > > "compilerOptions": {
> > > > > "debug": false,
> > > > > "targets": ["JSRoyale"],
> > > > > "source-map": true,
> > > > > "html-template": "src/resources/index-template.html",
> > > > > "js-library-path": [
> > > > > "${royalelib}/js/libs/MXRoyaleJS.swc"
> > > > > ]
> > > > > },
> > > > > "additionalOptions": "-watch -remove-circulars
> > > > > -js-output-optimization=skipAsCoercions
> > > > >
> -compiler.exclude-defaults-css-files=MXRoyale-0.9.10-js.swc:defaults
> > > > > .css
> > > > > -keep-as3-metadata+=Transient",
> > > > > "files":
> > > > > [
> > > > > "src/App.mxml"
> > > > > ]
> > > > > }
> > > > >
> > > > > VS Code - Problems:
> > > > > unknown configuration variable 'watch'.
> > > > >
> > > > >
> > > > > Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta,
> > > > > 1/04/2022
> > > > > à(s)
> > > > > 11:08:
> > > > >
> > > > > > 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 <mj...@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\roy
> > > > 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,PostConstruct
> > > >
> -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transien
> > > > -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\royale
> > > > 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:compile
> > > > -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(Watc
> > > > hThread.java:262)
> > > > > >
> > > > > > at
> > > > > >
> > > > >
> > > >
> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThrea
> > > > d.java:130)
> > > > > > Caused by: java.lang.ClassNotFoundException:
> > > > > > org.apache.royale.compiler.internal.watcher.WatchThread$1
> > > > > > at
> > > > > >
> > > > >
> > > >
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(S
> > > > elfFirstStrategy.java:50)
> > > > > > at
> > > > > >
> > > > >
> > > >
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadCla
> > > > 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/view
> > > > ?usp=sharing
> > > > > >
> > > > > >
> > > > > > Hiedra
> > > > > >
> > > > > > -----Mensaje original-----
> > > > > > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves,
> > > > > > 31 de marzo de 2022 23:49
> > > > > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> > > > > > <ro...@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<
> > > > joshtynjala@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>
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
Re: New --watch compiler option
Posted by Hugo Ferreira <hf...@gmail.com>.
Hi Josh,
Great :D !
I will test now.
Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia quinta, 7/04/2022
à(s) 23:07:
> Hugo and Yishay,
>
> My latest compiler commits should fix the issue with broken binding after
> file changes. Please give it another try, and let me know if you
> encounter any other problems.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Sat, Apr 2, 2022 at 2:03 AM Yishay Weiss <yi...@hotmail.com>
> wrote:
>
> > Thanks for doing this, could make a huge difference for our client.
> >
> > I can confirm DataBindingExample does not work well with this option.
> >
> > Changing MyInitivalView:139 to
> >
> > <js:RadioButton id="radio1"
> > text="Price222" value="Ask" groupName="group1"
> > change="radioChanged(event)"/>
> >
> > Creates the following stack trace after refresh
> >
> > ArraySelectionModel.js:184 Uncaught TypeError: Cannot read properties of
> > undefined (reading 'length')
> > at
> > org.apache.royale.html.beads.models.ArraySelectionModel.set__selectedItem
> > (ArraySelectionModel.js:184:109)
> > at org.apache.royale.html.DropDownList.set__selectedItem
> > (DropDownList.js:138:27)
> > at MyInitialView.MyInitialView_initControls (MyInitialView.js:386:26)
> > at MyInitialView.$EH_10_0 (MyInitialView.js:472:8)
> > at
> > MyInitialView.org.apache.royale.events.EventDispatcher.fireListeners
> > (EventDispatcher.js:102:23)
> > at Function.goog.events.EventTarget.dispatchEventInternal_
> > (eventtarget.js:382:26)
> > at
> > MyInitialView.org.apache.royale.events.EventDispatcher.dispatchEvent
> > (EventDispatcher.js:77:37)
> > at MyInitialView.org.apache.royale.core.ElementWrapper.dispatchEvent
> > (ElementWrapper.js:223:76)
> > at Object.org.apache.royale.utils.sendEvent (sendEvent.js:27:21)
> > at MyInitialView.org.apache.royale.core.View.addedToParent
> > (View.js:64:29)
> >
> > From: Josh Tynjala<ma...@bowlerhat.dev>
> > Sent: Saturday, April 2, 2022 1:00 AM
> > To: dev@royale.apache.org<ma...@royale.apache.org>
> > Subject: Re: New --watch compiler option
> >
> > Thanks, Hugo. I'll investigate the issue with binding.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Fri, Apr 1, 2022 at 2:57 PM Hugo Ferreira <hf...@gmail.com>
> > wrote:
> >
> > > Thank you Maria and thank you Josh.
> > >
> > > It's working now but for simple changes.
> > >
> > > The first test worked like a charm.
> > >
> > > Changing from:
> > > <c:FormItem label="Code"
> > >
> > > To:
> > > <c:FormItem label="Code 2"
> > >
> > > Refresh on the browser and I see the change like magic.
> > >
> > > However something more complex with a data binding and I get a messy
> > > result.
> > >
> > > Changing from:
> > > <models:Menu Text="{localeManager.localeStrings.MenuAdminCompany}"/>
> > >
> > > To:
> > > <models:Menu Text="{localeManager.localeStrings.MenuAdminUsers}"/>
> > >
> > > The result is a messy result on the browser with 0 errors on the
> console
> > (I
> > > tested with other kind of data bindings and it's the same result).
> > > Also if I change from a data binding to a fixed test, I got the same
> > messy
> > > results.
> > >
> > > <models:Menu Text="Test"/> => The same messing result on the browser
> and
> > > the solution is to manually rebuild.
> > >
> > > Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta, 1/04/2022
> > > à(s)
> > > 22:14:
> > >
> > > > Hi Hugo,
> > > > You can set it in the workspace file or from vsCode:
> > > > - workspace file: (myproject.code-workspace)
> > > > {
> > > > "folders": [
> > > > {
> > > > "path": "projectXXXX"
> > > > }
> > > > ],
> > > > "settings": {
> > > > "as3mxml.sdk.framework":
> > > > "d:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs",
> > > > "as3mxml.sdk.editor":
> > > > "D:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs"
> > > > <------------------------------ HERE ****************
> > > > }
> > > > }
> > > >
> > > > - vsCode:
> > > > - You can edit manually the file "settings.json" [1] (in
> > Windows
> > > > it is in C:\Users\hiedra\AppData\Roaming\Code\User\settings.json)
> > > > - or from the IDE (File/Preferences/Settings) [2].
> > > >
> > > > [1]
> > > >
> > >
> >
> https://drive.google.com/file/d/1SE-29sJc08tXV5-GMBabPJJWGRfyj4u0/view?usp=sharing
> > > > [2]
> > > >
> > >
> >
> https://drive.google.com/file/d/1nyC0JyHdD8441nEBks-mwIeElVs41tZQ/view?usp=sharing
> > > >
> > > > Hiedra
> > > >
> > > > -----Mensaje original-----
> > > > De: Hugo Ferreira <hf...@gmail.com>
> > > > Enviado el: viernes, 1 de abril de 2022 21:44
> > > > Para: Apache Royale Development <de...@royale.apache.org>
> > > > Asunto: Re: New --watch compiler option
> > > >
> > > > Where is the as3mxml.sdk.editor file ?
> > > > I didn't find it (macOS)
> > > >
> > > >
> > > > Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia sexta,
> > > 1/04/2022
> > > > à(s) 16:52:
> > > >
> > > > > If you're going to add -watch to asconfig.json, you'll also need to
> > > > > update the as3mxml.sdk.editor setting in VSCode to the path of your
> > > > > new Royale SDK. vscode-as3mxml bundles Royale 0.9.8, so it doesn't
> > > > > know anything about -watch, but as3mxml.sdk.editor lets it use a
> > > > > custom SDK for code intelligence purposes.
> > > > >
> > > > > In a future update, vscode-as3mxml will have a built-in watch task
> so
> > > > > that you won't need to modify asconfig.json. I have it working in a
> > > > > branch right now.
> > > > >
> > > > > --
> > > > > Josh Tynjala
> > > > > Bowler Hat LLC <https://bowlerhat.dev>
> > > > >
> > > > >
> > > > > On Fri, Apr 1, 2022 at 3:48 AM Hugo Ferreira <
> hferreira.80@gmail.com
> > >
> > > > > wrote:
> > > > >
> > > > > > Does not work with me:
> > > > > >
> > > > > > asconfig.json:
> > > > > > {
> > > > > > "config": "royale",
> > > > > > "copySourcePathAssets": true,
> > > > > > "compilerOptions": {
> > > > > > "debug": false,
> > > > > > "targets": ["JSRoyale"],
> > > > > > "source-map": true,
> > > > > > "html-template": "src/resources/index-template.html",
> > > > > > "js-library-path": [
> > > > > > "${royalelib}/js/libs/MXRoyaleJS.swc"
> > > > > > ]
> > > > > > },
> > > > > > "additionalOptions": "-watch -remove-circulars
> > > > > > -js-output-optimization=skipAsCoercions
> > > > > >
> > -compiler.exclude-defaults-css-files=MXRoyale-0.9.10-js.swc:defaults
> > > > > > .css
> > > > > > -keep-as3-metadata+=Transient",
> > > > > > "files":
> > > > > > [
> > > > > > "src/App.mxml"
> > > > > > ]
> > > > > > }
> > > > > >
> > > > > > VS Code - Problems:
> > > > > > unknown configuration variable 'watch'.
> > > > > >
> > > > > >
> > > > > > Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta,
> > > > > > 1/04/2022
> > > > > > à(s)
> > > > > > 11:08:
> > > > > >
> > > > > > > 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 <mj...@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\roy
> > > > > 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,PostConstruct
> > > > >
> > -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transien
> > > > > -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\royale
> > > > > 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:compile
> > > > > -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(Watc
> > > > > hThread.java:262)
> > > > > > >
> > > > > > > at
> > > > > > >
> > > > > >
> > > > >
> > org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThrea
> > > > > d.java:130)
> > > > > > > Caused by: java.lang.ClassNotFoundException:
> > > > > > > org.apache.royale.compiler.internal.watcher.WatchThread$1
> > > > > > > at
> > > > > > >
> > > > > >
> > > > >
> > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(S
> > > > > elfFirstStrategy.java:50)
> > > > > > > at
> > > > > > >
> > > > > >
> > > > >
> > org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadCla
> > > > > 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/view
> > > > > ?usp=sharing
> > > > > > >
> > > > > > >
> > > > > > > Hiedra
> > > > > > >
> > > > > > > -----Mensaje original-----
> > > > > > > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el:
> jueves,
> > > > > > > 31 de marzo de 2022 23:49
> > > > > > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> > > > > > > <ro...@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<
> > > > > joshtynjala@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>
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
>
Re: New --watch compiler option
Posted by Josh Tynjala <jo...@bowlerhat.dev>.
Hugo and Yishay,
My latest compiler commits should fix the issue with broken binding after
file changes. Please give it another try, and let me know if you
encounter any other problems.
--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>
On Sat, Apr 2, 2022 at 2:03 AM Yishay Weiss <yi...@hotmail.com> wrote:
> Thanks for doing this, could make a huge difference for our client.
>
> I can confirm DataBindingExample does not work well with this option.
>
> Changing MyInitivalView:139 to
>
> <js:RadioButton id="radio1"
> text="Price222" value="Ask" groupName="group1"
> change="radioChanged(event)"/>
>
> Creates the following stack trace after refresh
>
> ArraySelectionModel.js:184 Uncaught TypeError: Cannot read properties of
> undefined (reading 'length')
> at
> org.apache.royale.html.beads.models.ArraySelectionModel.set__selectedItem
> (ArraySelectionModel.js:184:109)
> at org.apache.royale.html.DropDownList.set__selectedItem
> (DropDownList.js:138:27)
> at MyInitialView.MyInitialView_initControls (MyInitialView.js:386:26)
> at MyInitialView.$EH_10_0 (MyInitialView.js:472:8)
> at
> MyInitialView.org.apache.royale.events.EventDispatcher.fireListeners
> (EventDispatcher.js:102:23)
> at Function.goog.events.EventTarget.dispatchEventInternal_
> (eventtarget.js:382:26)
> at
> MyInitialView.org.apache.royale.events.EventDispatcher.dispatchEvent
> (EventDispatcher.js:77:37)
> at MyInitialView.org.apache.royale.core.ElementWrapper.dispatchEvent
> (ElementWrapper.js:223:76)
> at Object.org.apache.royale.utils.sendEvent (sendEvent.js:27:21)
> at MyInitialView.org.apache.royale.core.View.addedToParent
> (View.js:64:29)
>
> From: Josh Tynjala<ma...@bowlerhat.dev>
> Sent: Saturday, April 2, 2022 1:00 AM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: New --watch compiler option
>
> Thanks, Hugo. I'll investigate the issue with binding.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Fri, Apr 1, 2022 at 2:57 PM Hugo Ferreira <hf...@gmail.com>
> wrote:
>
> > Thank you Maria and thank you Josh.
> >
> > It's working now but for simple changes.
> >
> > The first test worked like a charm.
> >
> > Changing from:
> > <c:FormItem label="Code"
> >
> > To:
> > <c:FormItem label="Code 2"
> >
> > Refresh on the browser and I see the change like magic.
> >
> > However something more complex with a data binding and I get a messy
> > result.
> >
> > Changing from:
> > <models:Menu Text="{localeManager.localeStrings.MenuAdminCompany}"/>
> >
> > To:
> > <models:Menu Text="{localeManager.localeStrings.MenuAdminUsers}"/>
> >
> > The result is a messy result on the browser with 0 errors on the console
> (I
> > tested with other kind of data bindings and it's the same result).
> > Also if I change from a data binding to a fixed test, I got the same
> messy
> > results.
> >
> > <models:Menu Text="Test"/> => The same messing result on the browser and
> > the solution is to manually rebuild.
> >
> > Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta, 1/04/2022
> > à(s)
> > 22:14:
> >
> > > Hi Hugo,
> > > You can set it in the workspace file or from vsCode:
> > > - workspace file: (myproject.code-workspace)
> > > {
> > > "folders": [
> > > {
> > > "path": "projectXXXX"
> > > }
> > > ],
> > > "settings": {
> > > "as3mxml.sdk.framework":
> > > "d:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs",
> > > "as3mxml.sdk.editor":
> > > "D:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs"
> > > <------------------------------ HERE ****************
> > > }
> > > }
> > >
> > > - vsCode:
> > > - You can edit manually the file "settings.json" [1] (in
> Windows
> > > it is in C:\Users\hiedra\AppData\Roaming\Code\User\settings.json)
> > > - or from the IDE (File/Preferences/Settings) [2].
> > >
> > > [1]
> > >
> >
> https://drive.google.com/file/d/1SE-29sJc08tXV5-GMBabPJJWGRfyj4u0/view?usp=sharing
> > > [2]
> > >
> >
> https://drive.google.com/file/d/1nyC0JyHdD8441nEBks-mwIeElVs41tZQ/view?usp=sharing
> > >
> > > Hiedra
> > >
> > > -----Mensaje original-----
> > > De: Hugo Ferreira <hf...@gmail.com>
> > > Enviado el: viernes, 1 de abril de 2022 21:44
> > > Para: Apache Royale Development <de...@royale.apache.org>
> > > Asunto: Re: New --watch compiler option
> > >
> > > Where is the as3mxml.sdk.editor file ?
> > > I didn't find it (macOS)
> > >
> > >
> > > Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia sexta,
> > 1/04/2022
> > > à(s) 16:52:
> > >
> > > > If you're going to add -watch to asconfig.json, you'll also need to
> > > > update the as3mxml.sdk.editor setting in VSCode to the path of your
> > > > new Royale SDK. vscode-as3mxml bundles Royale 0.9.8, so it doesn't
> > > > know anything about -watch, but as3mxml.sdk.editor lets it use a
> > > > custom SDK for code intelligence purposes.
> > > >
> > > > In a future update, vscode-as3mxml will have a built-in watch task so
> > > > that you won't need to modify asconfig.json. I have it working in a
> > > > branch right now.
> > > >
> > > > --
> > > > Josh Tynjala
> > > > Bowler Hat LLC <https://bowlerhat.dev>
> > > >
> > > >
> > > > On Fri, Apr 1, 2022 at 3:48 AM Hugo Ferreira <hferreira.80@gmail.com
> >
> > > > wrote:
> > > >
> > > > > Does not work with me:
> > > > >
> > > > > asconfig.json:
> > > > > {
> > > > > "config": "royale",
> > > > > "copySourcePathAssets": true,
> > > > > "compilerOptions": {
> > > > > "debug": false,
> > > > > "targets": ["JSRoyale"],
> > > > > "source-map": true,
> > > > > "html-template": "src/resources/index-template.html",
> > > > > "js-library-path": [
> > > > > "${royalelib}/js/libs/MXRoyaleJS.swc"
> > > > > ]
> > > > > },
> > > > > "additionalOptions": "-watch -remove-circulars
> > > > > -js-output-optimization=skipAsCoercions
> > > > >
> -compiler.exclude-defaults-css-files=MXRoyale-0.9.10-js.swc:defaults
> > > > > .css
> > > > > -keep-as3-metadata+=Transient",
> > > > > "files":
> > > > > [
> > > > > "src/App.mxml"
> > > > > ]
> > > > > }
> > > > >
> > > > > VS Code - Problems:
> > > > > unknown configuration variable 'watch'.
> > > > >
> > > > >
> > > > > Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta,
> > > > > 1/04/2022
> > > > > à(s)
> > > > > 11:08:
> > > > >
> > > > > > 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 <mj...@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\roy
> > > > 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,PostConstruct
> > > >
> -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transien
> > > > -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\royale
> > > > 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:compile
> > > > -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(Watc
> > > > hThread.java:262)
> > > > > >
> > > > > > at
> > > > > >
> > > > >
> > > >
> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThrea
> > > > d.java:130)
> > > > > > Caused by: java.lang.ClassNotFoundException:
> > > > > > org.apache.royale.compiler.internal.watcher.WatchThread$1
> > > > > > at
> > > > > >
> > > > >
> > > >
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(S
> > > > elfFirstStrategy.java:50)
> > > > > > at
> > > > > >
> > > > >
> > > >
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadCla
> > > > 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/view
> > > > ?usp=sharing
> > > > > >
> > > > > >
> > > > > > Hiedra
> > > > > >
> > > > > > -----Mensaje original-----
> > > > > > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves,
> > > > > > 31 de marzo de 2022 23:49
> > > > > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> > > > > > <ro...@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<
> > > > joshtynjala@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>
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
RE: New --watch compiler option
Posted by Yishay Weiss <yi...@hotmail.com>.
Thanks for doing this, could make a huge difference for our client.
I can confirm DataBindingExample does not work well with this option.
Changing MyInitivalView:139 to
<js:RadioButton id="radio1" text="Price222" value="Ask" groupName="group1" change="radioChanged(event)"/>
Creates the following stack trace after refresh
ArraySelectionModel.js:184 Uncaught TypeError: Cannot read properties of undefined (reading 'length')
at org.apache.royale.html.beads.models.ArraySelectionModel.set__selectedItem (ArraySelectionModel.js:184:109)
at org.apache.royale.html.DropDownList.set__selectedItem (DropDownList.js:138:27)
at MyInitialView.MyInitialView_initControls (MyInitialView.js:386:26)
at MyInitialView.$EH_10_0 (MyInitialView.js:472:8)
at MyInitialView.org.apache.royale.events.EventDispatcher.fireListeners (EventDispatcher.js:102:23)
at Function.goog.events.EventTarget.dispatchEventInternal_ (eventtarget.js:382:26)
at MyInitialView.org.apache.royale.events.EventDispatcher.dispatchEvent (EventDispatcher.js:77:37)
at MyInitialView.org.apache.royale.core.ElementWrapper.dispatchEvent (ElementWrapper.js:223:76)
at Object.org.apache.royale.utils.sendEvent (sendEvent.js:27:21)
at MyInitialView.org.apache.royale.core.View.addedToParent (View.js:64:29)
From: Josh Tynjala<ma...@bowlerhat.dev>
Sent: Saturday, April 2, 2022 1:00 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: New --watch compiler option
Thanks, Hugo. I'll investigate the issue with binding.
--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>
On Fri, Apr 1, 2022 at 2:57 PM Hugo Ferreira <hf...@gmail.com> wrote:
> Thank you Maria and thank you Josh.
>
> It's working now but for simple changes.
>
> The first test worked like a charm.
>
> Changing from:
> <c:FormItem label="Code"
>
> To:
> <c:FormItem label="Code 2"
>
> Refresh on the browser and I see the change like magic.
>
> However something more complex with a data binding and I get a messy
> result.
>
> Changing from:
> <models:Menu Text="{localeManager.localeStrings.MenuAdminCompany}"/>
>
> To:
> <models:Menu Text="{localeManager.localeStrings.MenuAdminUsers}"/>
>
> The result is a messy result on the browser with 0 errors on the console (I
> tested with other kind of data bindings and it's the same result).
> Also if I change from a data binding to a fixed test, I got the same messy
> results.
>
> <models:Menu Text="Test"/> => The same messing result on the browser and
> the solution is to manually rebuild.
>
> Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta, 1/04/2022
> à(s)
> 22:14:
>
> > Hi Hugo,
> > You can set it in the workspace file or from vsCode:
> > - workspace file: (myproject.code-workspace)
> > {
> > "folders": [
> > {
> > "path": "projectXXXX"
> > }
> > ],
> > "settings": {
> > "as3mxml.sdk.framework":
> > "d:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs",
> > "as3mxml.sdk.editor":
> > "D:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs"
> > <------------------------------ HERE ****************
> > }
> > }
> >
> > - vsCode:
> > - You can edit manually the file "settings.json" [1] (in Windows
> > it is in C:\Users\hiedra\AppData\Roaming\Code\User\settings.json)
> > - or from the IDE (File/Preferences/Settings) [2].
> >
> > [1]
> >
> https://drive.google.com/file/d/1SE-29sJc08tXV5-GMBabPJJWGRfyj4u0/view?usp=sharing
> > [2]
> >
> https://drive.google.com/file/d/1nyC0JyHdD8441nEBks-mwIeElVs41tZQ/view?usp=sharing
> >
> > Hiedra
> >
> > -----Mensaje original-----
> > De: Hugo Ferreira <hf...@gmail.com>
> > Enviado el: viernes, 1 de abril de 2022 21:44
> > Para: Apache Royale Development <de...@royale.apache.org>
> > Asunto: Re: New --watch compiler option
> >
> > Where is the as3mxml.sdk.editor file ?
> > I didn't find it (macOS)
> >
> >
> > Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia sexta,
> 1/04/2022
> > à(s) 16:52:
> >
> > > If you're going to add -watch to asconfig.json, you'll also need to
> > > update the as3mxml.sdk.editor setting in VSCode to the path of your
> > > new Royale SDK. vscode-as3mxml bundles Royale 0.9.8, so it doesn't
> > > know anything about -watch, but as3mxml.sdk.editor lets it use a
> > > custom SDK for code intelligence purposes.
> > >
> > > In a future update, vscode-as3mxml will have a built-in watch task so
> > > that you won't need to modify asconfig.json. I have it working in a
> > > branch right now.
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <https://bowlerhat.dev>
> > >
> > >
> > > On Fri, Apr 1, 2022 at 3:48 AM Hugo Ferreira <hf...@gmail.com>
> > > wrote:
> > >
> > > > Does not work with me:
> > > >
> > > > asconfig.json:
> > > > {
> > > > "config": "royale",
> > > > "copySourcePathAssets": true,
> > > > "compilerOptions": {
> > > > "debug": false,
> > > > "targets": ["JSRoyale"],
> > > > "source-map": true,
> > > > "html-template": "src/resources/index-template.html",
> > > > "js-library-path": [
> > > > "${royalelib}/js/libs/MXRoyaleJS.swc"
> > > > ]
> > > > },
> > > > "additionalOptions": "-watch -remove-circulars
> > > > -js-output-optimization=skipAsCoercions
> > > > -compiler.exclude-defaults-css-files=MXRoyale-0.9.10-js.swc:defaults
> > > > .css
> > > > -keep-as3-metadata+=Transient",
> > > > "files":
> > > > [
> > > > "src/App.mxml"
> > > > ]
> > > > }
> > > >
> > > > VS Code - Problems:
> > > > unknown configuration variable 'watch'.
> > > >
> > > >
> > > > Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta,
> > > > 1/04/2022
> > > > à(s)
> > > > 11:08:
> > > >
> > > > > 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 <mj...@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\roy
> > > 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,PostConstruct
> > > -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transien
> > > -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\royale
> > > 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:compile
> > > -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(Watc
> > > hThread.java:262)
> > > > >
> > > > > at
> > > > >
> > > >
> > > org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThrea
> > > d.java:130)
> > > > > Caused by: java.lang.ClassNotFoundException:
> > > > > org.apache.royale.compiler.internal.watcher.WatchThread$1
> > > > > at
> > > > >
> > > >
> > > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(S
> > > elfFirstStrategy.java:50)
> > > > > at
> > > > >
> > > >
> > > org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadCla
> > > 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/view
> > > ?usp=sharing
> > > > >
> > > > >
> > > > > Hiedra
> > > > >
> > > > > -----Mensaje original-----
> > > > > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves,
> > > > > 31 de marzo de 2022 23:49
> > > > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> > > > > <ro...@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<
> > > joshtynjala@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>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: New --watch compiler option
Posted by Josh Tynjala <jo...@bowlerhat.dev>.
Thanks, Hugo. I'll investigate the issue with binding.
--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>
On Fri, Apr 1, 2022 at 2:57 PM Hugo Ferreira <hf...@gmail.com> wrote:
> Thank you Maria and thank you Josh.
>
> It's working now but for simple changes.
>
> The first test worked like a charm.
>
> Changing from:
> <c:FormItem label="Code"
>
> To:
> <c:FormItem label="Code 2"
>
> Refresh on the browser and I see the change like magic.
>
> However something more complex with a data binding and I get a messy
> result.
>
> Changing from:
> <models:Menu Text="{localeManager.localeStrings.MenuAdminCompany}"/>
>
> To:
> <models:Menu Text="{localeManager.localeStrings.MenuAdminUsers}"/>
>
> The result is a messy result on the browser with 0 errors on the console (I
> tested with other kind of data bindings and it's the same result).
> Also if I change from a data binding to a fixed test, I got the same messy
> results.
>
> <models:Menu Text="Test"/> => The same messing result on the browser and
> the solution is to manually rebuild.
>
> Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta, 1/04/2022
> à(s)
> 22:14:
>
> > Hi Hugo,
> > You can set it in the workspace file or from vsCode:
> > - workspace file: (myproject.code-workspace)
> > {
> > "folders": [
> > {
> > "path": "projectXXXX"
> > }
> > ],
> > "settings": {
> > "as3mxml.sdk.framework":
> > "d:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs",
> > "as3mxml.sdk.editor":
> > "D:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs"
> > <------------------------------ HERE ****************
> > }
> > }
> >
> > - vsCode:
> > - You can edit manually the file "settings.json" [1] (in Windows
> > it is in C:\Users\hiedra\AppData\Roaming\Code\User\settings.json)
> > - or from the IDE (File/Preferences/Settings) [2].
> >
> > [1]
> >
> https://drive.google.com/file/d/1SE-29sJc08tXV5-GMBabPJJWGRfyj4u0/view?usp=sharing
> > [2]
> >
> https://drive.google.com/file/d/1nyC0JyHdD8441nEBks-mwIeElVs41tZQ/view?usp=sharing
> >
> > Hiedra
> >
> > -----Mensaje original-----
> > De: Hugo Ferreira <hf...@gmail.com>
> > Enviado el: viernes, 1 de abril de 2022 21:44
> > Para: Apache Royale Development <de...@royale.apache.org>
> > Asunto: Re: New --watch compiler option
> >
> > Where is the as3mxml.sdk.editor file ?
> > I didn't find it (macOS)
> >
> >
> > Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia sexta,
> 1/04/2022
> > à(s) 16:52:
> >
> > > If you're going to add -watch to asconfig.json, you'll also need to
> > > update the as3mxml.sdk.editor setting in VSCode to the path of your
> > > new Royale SDK. vscode-as3mxml bundles Royale 0.9.8, so it doesn't
> > > know anything about -watch, but as3mxml.sdk.editor lets it use a
> > > custom SDK for code intelligence purposes.
> > >
> > > In a future update, vscode-as3mxml will have a built-in watch task so
> > > that you won't need to modify asconfig.json. I have it working in a
> > > branch right now.
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <https://bowlerhat.dev>
> > >
> > >
> > > On Fri, Apr 1, 2022 at 3:48 AM Hugo Ferreira <hf...@gmail.com>
> > > wrote:
> > >
> > > > Does not work with me:
> > > >
> > > > asconfig.json:
> > > > {
> > > > "config": "royale",
> > > > "copySourcePathAssets": true,
> > > > "compilerOptions": {
> > > > "debug": false,
> > > > "targets": ["JSRoyale"],
> > > > "source-map": true,
> > > > "html-template": "src/resources/index-template.html",
> > > > "js-library-path": [
> > > > "${royalelib}/js/libs/MXRoyaleJS.swc"
> > > > ]
> > > > },
> > > > "additionalOptions": "-watch -remove-circulars
> > > > -js-output-optimization=skipAsCoercions
> > > > -compiler.exclude-defaults-css-files=MXRoyale-0.9.10-js.swc:defaults
> > > > .css
> > > > -keep-as3-metadata+=Transient",
> > > > "files":
> > > > [
> > > > "src/App.mxml"
> > > > ]
> > > > }
> > > >
> > > > VS Code - Problems:
> > > > unknown configuration variable 'watch'.
> > > >
> > > >
> > > > Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta,
> > > > 1/04/2022
> > > > à(s)
> > > > 11:08:
> > > >
> > > > > 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 <mj...@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\roy
> > > 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,PostConstruct
> > > -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transien
> > > -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\royale
> > > 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:compile
> > > -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(Watc
> > > hThread.java:262)
> > > > >
> > > > > at
> > > > >
> > > >
> > > org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThrea
> > > d.java:130)
> > > > > Caused by: java.lang.ClassNotFoundException:
> > > > > org.apache.royale.compiler.internal.watcher.WatchThread$1
> > > > > at
> > > > >
> > > >
> > > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(S
> > > elfFirstStrategy.java:50)
> > > > > at
> > > > >
> > > >
> > > org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadCla
> > > 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/view
> > > ?usp=sharing
> > > > >
> > > > >
> > > > > Hiedra
> > > > >
> > > > > -----Mensaje original-----
> > > > > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves,
> > > > > 31 de marzo de 2022 23:49
> > > > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> > > > > <ro...@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<
> > > joshtynjala@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>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: New --watch compiler option
Posted by Hugo Ferreira <hf...@gmail.com>.
Thank you Maria and thank you Josh.
It's working now but for simple changes.
The first test worked like a charm.
Changing from:
<c:FormItem label="Code"
To:
<c:FormItem label="Code 2"
Refresh on the browser and I see the change like magic.
However something more complex with a data binding and I get a messy result.
Changing from:
<models:Menu Text="{localeManager.localeStrings.MenuAdminCompany}"/>
To:
<models:Menu Text="{localeManager.localeStrings.MenuAdminUsers}"/>
The result is a messy result on the browser with 0 errors on the console (I
tested with other kind of data bindings and it's the same result).
Also if I change from a data binding to a fixed test, I got the same messy
results.
<models:Menu Text="Test"/> => The same messing result on the browser and
the solution is to manually rebuild.
Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta, 1/04/2022 à(s)
22:14:
> Hi Hugo,
> You can set it in the workspace file or from vsCode:
> - workspace file: (myproject.code-workspace)
> {
> "folders": [
> {
> "path": "projectXXXX"
> }
> ],
> "settings": {
> "as3mxml.sdk.framework":
> "d:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs",
> "as3mxml.sdk.editor":
> "D:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs"
> <------------------------------ HERE ****************
> }
> }
>
> - vsCode:
> - You can edit manually the file "settings.json" [1] (in Windows
> it is in C:\Users\hiedra\AppData\Roaming\Code\User\settings.json)
> - or from the IDE (File/Preferences/Settings) [2].
>
> [1]
> https://drive.google.com/file/d/1SE-29sJc08tXV5-GMBabPJJWGRfyj4u0/view?usp=sharing
> [2]
> https://drive.google.com/file/d/1nyC0JyHdD8441nEBks-mwIeElVs41tZQ/view?usp=sharing
>
> Hiedra
>
> -----Mensaje original-----
> De: Hugo Ferreira <hf...@gmail.com>
> Enviado el: viernes, 1 de abril de 2022 21:44
> Para: Apache Royale Development <de...@royale.apache.org>
> Asunto: Re: New --watch compiler option
>
> Where is the as3mxml.sdk.editor file ?
> I didn't find it (macOS)
>
>
> Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia sexta, 1/04/2022
> à(s) 16:52:
>
> > If you're going to add -watch to asconfig.json, you'll also need to
> > update the as3mxml.sdk.editor setting in VSCode to the path of your
> > new Royale SDK. vscode-as3mxml bundles Royale 0.9.8, so it doesn't
> > know anything about -watch, but as3mxml.sdk.editor lets it use a
> > custom SDK for code intelligence purposes.
> >
> > In a future update, vscode-as3mxml will have a built-in watch task so
> > that you won't need to modify asconfig.json. I have it working in a
> > branch right now.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Fri, Apr 1, 2022 at 3:48 AM Hugo Ferreira <hf...@gmail.com>
> > wrote:
> >
> > > Does not work with me:
> > >
> > > asconfig.json:
> > > {
> > > "config": "royale",
> > > "copySourcePathAssets": true,
> > > "compilerOptions": {
> > > "debug": false,
> > > "targets": ["JSRoyale"],
> > > "source-map": true,
> > > "html-template": "src/resources/index-template.html",
> > > "js-library-path": [
> > > "${royalelib}/js/libs/MXRoyaleJS.swc"
> > > ]
> > > },
> > > "additionalOptions": "-watch -remove-circulars
> > > -js-output-optimization=skipAsCoercions
> > > -compiler.exclude-defaults-css-files=MXRoyale-0.9.10-js.swc:defaults
> > > .css
> > > -keep-as3-metadata+=Transient",
> > > "files":
> > > [
> > > "src/App.mxml"
> > > ]
> > > }
> > >
> > > VS Code - Problems:
> > > unknown configuration variable 'watch'.
> > >
> > >
> > > Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta,
> > > 1/04/2022
> > > à(s)
> > > 11:08:
> > >
> > > > 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 <mj...@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\roy
> > 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,PostConstruct
> > -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transien
> > -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\royale
> > 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:compile
> > -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(Watc
> > hThread.java:262)
> > > >
> > > > at
> > > >
> > >
> > org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThrea
> > d.java:130)
> > > > Caused by: java.lang.ClassNotFoundException:
> > > > org.apache.royale.compiler.internal.watcher.WatchThread$1
> > > > at
> > > >
> > >
> > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(S
> > elfFirstStrategy.java:50)
> > > > at
> > > >
> > >
> > org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadCla
> > 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/view
> > ?usp=sharing
> > > >
> > > >
> > > > Hiedra
> > > >
> > > > -----Mensaje original-----
> > > > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves,
> > > > 31 de marzo de 2022 23:49
> > > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> > > > <ro...@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<
> > joshtynjala@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>
> > > > >
> > > > >
> > > >
> > >
> >
>
RE: New --watch compiler option
Posted by Maria Jose Esteve <mj...@iest.com>.
Hi Hugo,
You can set it in the workspace file or from vsCode:
- workspace file: (myproject.code-workspace)
{
"folders": [
{
"path": "projectXXXX"
}
],
"settings": {
"as3mxml.sdk.framework": "d:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs",
"as3mxml.sdk.editor": "D:\\Develop_Royale\\Projects\\Royale-SDK\\royale-asjs" <------------------------------ HERE ****************
}
}
- vsCode:
- You can edit manually the file "settings.json" [1] (in Windows it is in C:\Users\hiedra\AppData\Roaming\Code\User\settings.json)
- or from the IDE (File/Preferences/Settings) [2].
[1] https://drive.google.com/file/d/1SE-29sJc08tXV5-GMBabPJJWGRfyj4u0/view?usp=sharing
[2] https://drive.google.com/file/d/1nyC0JyHdD8441nEBks-mwIeElVs41tZQ/view?usp=sharing
Hiedra
-----Mensaje original-----
De: Hugo Ferreira <hf...@gmail.com>
Enviado el: viernes, 1 de abril de 2022 21:44
Para: Apache Royale Development <de...@royale.apache.org>
Asunto: Re: New --watch compiler option
Where is the as3mxml.sdk.editor file ?
I didn't find it (macOS)
Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia sexta, 1/04/2022
à(s) 16:52:
> If you're going to add -watch to asconfig.json, you'll also need to
> update the as3mxml.sdk.editor setting in VSCode to the path of your
> new Royale SDK. vscode-as3mxml bundles Royale 0.9.8, so it doesn't
> know anything about -watch, but as3mxml.sdk.editor lets it use a
> custom SDK for code intelligence purposes.
>
> In a future update, vscode-as3mxml will have a built-in watch task so
> that you won't need to modify asconfig.json. I have it working in a
> branch right now.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Fri, Apr 1, 2022 at 3:48 AM Hugo Ferreira <hf...@gmail.com>
> wrote:
>
> > Does not work with me:
> >
> > asconfig.json:
> > {
> > "config": "royale",
> > "copySourcePathAssets": true,
> > "compilerOptions": {
> > "debug": false,
> > "targets": ["JSRoyale"],
> > "source-map": true,
> > "html-template": "src/resources/index-template.html",
> > "js-library-path": [
> > "${royalelib}/js/libs/MXRoyaleJS.swc"
> > ]
> > },
> > "additionalOptions": "-watch -remove-circulars
> > -js-output-optimization=skipAsCoercions
> > -compiler.exclude-defaults-css-files=MXRoyale-0.9.10-js.swc:defaults
> > .css
> > -keep-as3-metadata+=Transient",
> > "files":
> > [
> > "src/App.mxml"
> > ]
> > }
> >
> > VS Code - Problems:
> > unknown configuration variable 'watch'.
> >
> >
> > Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta,
> > 1/04/2022
> > à(s)
> > 11:08:
> >
> > > 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 <mj...@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\roy
> 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,PostConstruct
> -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transien
> -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\royale
> 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:compile
> -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(Watc
> hThread.java:262)
> > >
> > > at
> > >
> >
> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThrea
> d.java:130)
> > > Caused by: java.lang.ClassNotFoundException:
> > > org.apache.royale.compiler.internal.watcher.WatchThread$1
> > > at
> > >
> >
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(S
> elfFirstStrategy.java:50)
> > > at
> > >
> >
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadCla
> 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/view
> ?usp=sharing
> > >
> > >
> > > Hiedra
> > >
> > > -----Mensaje original-----
> > > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves,
> > > 31 de marzo de 2022 23:49
> > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> > > <ro...@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<
> joshtynjala@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>
> > > >
> > > >
> > >
> >
>
Re: New --watch compiler option
Posted by Hugo Ferreira <hf...@gmail.com>.
Where is the as3mxml.sdk.editor file ?
I didn't find it (macOS)
Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia sexta, 1/04/2022
à(s) 16:52:
> If you're going to add -watch to asconfig.json, you'll also need to update
> the as3mxml.sdk.editor setting in VSCode to the path of your new Royale
> SDK. vscode-as3mxml bundles Royale 0.9.8, so it doesn't know anything about
> -watch, but as3mxml.sdk.editor lets it use a custom SDK for code
> intelligence purposes.
>
> In a future update, vscode-as3mxml will have a built-in watch task so that
> you won't need to modify asconfig.json. I have it working in a branch right
> now.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Fri, Apr 1, 2022 at 3:48 AM Hugo Ferreira <hf...@gmail.com>
> wrote:
>
> > Does not work with me:
> >
> > asconfig.json:
> > {
> > "config": "royale",
> > "copySourcePathAssets": true,
> > "compilerOptions": {
> > "debug": false,
> > "targets": ["JSRoyale"],
> > "source-map": true,
> > "html-template": "src/resources/index-template.html",
> > "js-library-path": [
> > "${royalelib}/js/libs/MXRoyaleJS.swc"
> > ]
> > },
> > "additionalOptions": "-watch -remove-circulars
> > -js-output-optimization=skipAsCoercions
> > -compiler.exclude-defaults-css-files=MXRoyale-0.9.10-js.swc:defaults.css
> > -keep-as3-metadata+=Transient",
> > "files":
> > [
> > "src/App.mxml"
> > ]
> > }
> >
> > VS Code - Problems:
> > unknown configuration variable 'watch'.
> >
> >
> > Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta, 1/04/2022
> > à(s)
> > 11:08:
> >
> > > 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 <mj...@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\royalelogin\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,PostConstruct,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transient,
> > > -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\royalelogin\target\javascript,
> > > -compiler.targets=JSRoyale,
> > >
> >
> D:\Develop_Royale\Projects\WinPlusWebSuite\royaleapp\royalelogin\src\main\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:compile-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(WatchThread.java:262)
> > >
> > > at
> > >
> >
> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThread.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.unsynchronizedLoadClass(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/view?usp=sharing
> > >
> > >
> > > Hiedra
> > >
> > > -----Mensaje original-----
> > > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves, 31 de
> > > marzo de 2022 23:49
> > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> > > <ro...@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<
> joshtynjala@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>
> > > >
> > > >
> > >
> >
>
Re: New --watch compiler option
Posted by Josh Tynjala <jo...@bowlerhat.dev>.
If you're going to add -watch to asconfig.json, you'll also need to update
the as3mxml.sdk.editor setting in VSCode to the path of your new Royale
SDK. vscode-as3mxml bundles Royale 0.9.8, so it doesn't know anything about
-watch, but as3mxml.sdk.editor lets it use a custom SDK for code
intelligence purposes.
In a future update, vscode-as3mxml will have a built-in watch task so that
you won't need to modify asconfig.json. I have it working in a branch right
now.
--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>
On Fri, Apr 1, 2022 at 3:48 AM Hugo Ferreira <hf...@gmail.com> wrote:
> Does not work with me:
>
> asconfig.json:
> {
> "config": "royale",
> "copySourcePathAssets": true,
> "compilerOptions": {
> "debug": false,
> "targets": ["JSRoyale"],
> "source-map": true,
> "html-template": "src/resources/index-template.html",
> "js-library-path": [
> "${royalelib}/js/libs/MXRoyaleJS.swc"
> ]
> },
> "additionalOptions": "-watch -remove-circulars
> -js-output-optimization=skipAsCoercions
> -compiler.exclude-defaults-css-files=MXRoyale-0.9.10-js.swc:defaults.css
> -keep-as3-metadata+=Transient",
> "files":
> [
> "src/App.mxml"
> ]
> }
>
> VS Code - Problems:
> unknown configuration variable 'watch'.
>
>
> Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta, 1/04/2022
> à(s)
> 11:08:
>
> > 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 <mj...@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\royalelogin\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,PostConstruct,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transient,
> > -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\royalelogin\target\javascript,
> > -compiler.targets=JSRoyale,
> >
> D:\Develop_Royale\Projects\WinPlusWebSuite\royaleapp\royalelogin\src\main\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:compile-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(WatchThread.java:262)
> >
> > at
> >
> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThread.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.unsynchronizedLoadClass(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/view?usp=sharing
> >
> >
> > Hiedra
> >
> > -----Mensaje original-----
> > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves, 31 de
> > marzo de 2022 23:49
> > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> > <ro...@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<joshtynjala@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>
> > >
> > >
> >
>
Re: New --watch compiler option
Posted by Hugo Ferreira <hf...@gmail.com>.
Does not work with me:
asconfig.json:
{
"config": "royale",
"copySourcePathAssets": true,
"compilerOptions": {
"debug": false,
"targets": ["JSRoyale"],
"source-map": true,
"html-template": "src/resources/index-template.html",
"js-library-path": [
"${royalelib}/js/libs/MXRoyaleJS.swc"
]
},
"additionalOptions": "-watch -remove-circulars
-js-output-optimization=skipAsCoercions
-compiler.exclude-defaults-css-files=MXRoyale-0.9.10-js.swc:defaults.css
-keep-as3-metadata+=Transient",
"files":
[
"src/App.mxml"
]
}
VS Code - Problems:
unknown configuration variable 'watch'.
Maria Jose Esteve <mj...@iest.com> escreveu no dia sexta, 1/04/2022 à(s)
11:08:
> 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 <mj...@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\royalelogin\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,PostConstruct,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transient,
> -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\royalelogin\target\javascript,
> -compiler.targets=JSRoyale,
> D:\Develop_Royale\Projects\WinPlusWebSuite\royaleapp\royalelogin\src\main\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:compile-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(WatchThread.java:262)
>
> at
> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThread.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.unsynchronizedLoadClass(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/view?usp=sharing
>
>
> Hiedra
>
> -----Mensaje original-----
> De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves, 31 de
> marzo de 2022 23:49
> Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> <ro...@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<jo...@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>
> >
> >
>
Re: New --watch compiler option
Posted by Josh Tynjala <jo...@bowlerhat.dev>.
Hmmm... it looks like I will need to modify the Maven plugin to handle
the special return code for watch so that it doesn't exit.
--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>
On Fri, Apr 1, 2022 at 5:11 AM Maria Jose Esteve <mj...@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:compile-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:compile-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.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.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.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (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.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.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.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (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/MojoExecutionException
> [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 <mj...@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 <mj...@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\royalelogin\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,PostConstruct,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transient,
> -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\royalelogin\target\javascript,
> -compiler.targets=JSRoyale,
> D:\Develop_Royale\Projects\WinPlusWebSuite\royaleapp\royalelogin\src\main\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:compile-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(WatchThread.java:262)
>
> at
> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThread.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.unsynchronizedLoadClass(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/view?usp=sharing
>
>
> Hiedra
>
> -----Mensaje original-----
> De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves, 31 de
> marzo de 2022 23:49
> Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> <ro...@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<jo...@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>
> >
> >
>
Re: New --watch compiler option
Posted by Josh Tynjala <jo...@bowlerhat.dev>.
The Royale compiler does not copy asset files. They are usually copied by
whichever build tool that you are using. For instance, asconfigc has the
copySourcePathAssets field in asconfig.json, while Maven has its resources
plugin.
Looking at asconfigc, I see that I set it up to copy the source path assets
after the compiler completes, so if you use --watch, it will never get to
that step. I may need to tweak asconfigc to run some of the later steps
before compiling.
In the meantime, as most have discovered, a regular build without --watch,
followed by a build with --watch is a decent enough workaround for now.
--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>
On Fri, Apr 8, 2022 at 6:25 PM Hugo Ferreira <hf...@gmail.com> wrote:
> 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 <hf...@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 <jo...@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 <hf...@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 <mj...@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 <jo...@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 <mjesteve@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:compile
> >> > > > -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:compile
> >> > > > -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.buildProjec
> >> > > > t
> >> > > > (LifecycleModuleBuilder.java:117)
> >> > > > at
> >> > > >
> >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> >> > > > t
> >> > > > (LifecycleModuleBuilder.java:81)
> >> > > > at
> >> > > >
> >> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea
> >> > > > 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.launchEnhanced
> >> > > > (Launcher.java:282)
> >> > > > at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> >> > > > (Launcher.java:225)
> >> > > > at
> >> > > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> >> > > > (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.buildProjec
> >> > > > t
> >> > > > (LifecycleModuleBuilder.java:117)
> >> > > > at
> >> > > >
> >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> >> > > > t
> >> > > > (LifecycleModuleBuilder.java:81)
> >> > > > at
> >> > > >
> >> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea
> >> > > > 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.launchEnhanced
> >> > > > (Launcher.java:282)
> >> > > > at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> >> > > > (Launcher.java:225)
> >> > > > at
> >> > > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> >> > > > (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/MojoExecutionExceptio
> >> > > > 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 <mj...@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 <mj...@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\roy
> >> > > > 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,PostConstruct
> >> > > >
> >> -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transien
> >> > > > -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\royale
> >> > > > 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:compile
> >> > > > -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(Watc
> >> > > > hThread.java:262)
> >> > > >
> >> > > > at
> >> > > >
> >> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThrea
> >> > > > 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.unsynchronizedLoadCla
> >> > > > 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/view
> >> > > > ?usp=sharing
> >> > > >
> >> > > >
> >> > > > Hiedra
> >> > > >
> >> > > > -----Mensaje original-----
> >> > > > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves,
> >> 31 de
> >> > > > marzo de 2022 23:49
> >> > > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> >> > > > <ro...@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<
> >> > joshtynjala@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>
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
Re: New --watch compiler option
Posted by Harbs <ha...@gmail.com>.
Ah. Excellent!
I did not think to test that.
Great work! :-)
> On Apr 25, 2022, at 6:56 PM, Josh Tynjala <jo...@bowlerhat.dev> wrote:
>
> Additionally, the latest asconfigc update copies all source path assets to
> the output directory *before* compiling, instead of after, so you should
> not need to use the workaround of building once without --watch and then
> building again with --watch anymore.
Re: New --watch compiler option
Posted by Josh Tynjala <jo...@bowlerhat.dev>.
Yes, the new npm asconfigc update exposes its own --watch option now so
that you don't need to specify it in additionalOptions. This option will
eventually be used by vscode-as3mxml to expose a new compile debug task
that also watches (I currently have this in a vscode-as3mxml branch, and it
will be included in a future update).
Additionally, the latest asconfigc update copies all source path assets to
the output directory *before* compiling, instead of after, so you should
not need to use the workaround of building once without --watch and then
building again with --watch anymore.
--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>
On Mon, Apr 25, 2022 at 3:26 AM Harbs <ha...@gmail.com> wrote:
> 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 <ha...@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 <ha...@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 <jo...@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 <ha...@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 <
> joshtynjala@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 <ha...@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 <mj...@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 <mj...@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 <hf...@gmail.com> Enviado el: sábado, 9
> de
> >>>>>> abril de 2022 3:26
> >>>>>>> Para: Apache Royale Development <de...@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 <hf...@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 <jo...@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.80@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 <mj...@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 <jo...@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
> >>>>>>>>>>> <mj...@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 <mj...@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 <mj...@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 <jo...@bowlerhat.dev> Enviado el:
> >>>>>>>>>>>> jueves,
> >>>>>>>>> 31 de
> >>>>>>>>>>>> marzo de 2022 23:49
> >>>>>>>>>>>> Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> >>>>>>>>>>>> <ro...@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<
> >>>>>>>>>> joshtynjala@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>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>>
> >>
> >
>
>
Re: New --watch compiler option
Posted by Harbs <ha...@gmail.com>.
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 <ha...@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 <ha...@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 <jo...@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 <ha...@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 <jo...@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 <ha...@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 <mj...@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 <mj...@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 <hf...@gmail.com> Enviado el: sábado, 9 de
>>>>>> abril de 2022 3:26
>>>>>>> Para: Apache Royale Development <de...@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 <hf...@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 <jo...@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.80@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 <mj...@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 <jo...@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
>>>>>>>>>>> <mj...@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 <mj...@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 <mj...@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 <jo...@bowlerhat.dev> Enviado el:
>>>>>>>>>>>> jueves,
>>>>>>>>> 31 de
>>>>>>>>>>>> marzo de 2022 23:49
>>>>>>>>>>>> Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
>>>>>>>>>>>> <ro...@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<
>>>>>>>>>> joshtynjala@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>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>
>
Re: New --watch compiler option
Posted by Harbs <ha...@gmail.com>.
Looks like 1.6 supports it:
https://github.com/BowlerHatLLC/asconfigc/commit/a3209fd88793e66e10059de128431e096fb80e34
Correct?
> On Apr 25, 2022, at 1:06 PM, Harbs <ha...@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 <jo...@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 <ha...@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 <jo...@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 <ha...@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 <mj...@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 <mj...@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 <hf...@gmail.com> Enviado el: sábado, 9 de
>>>>> abril de 2022 3:26
>>>>>> Para: Apache Royale Development <de...@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 <hf...@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 <jo...@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.80@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 <mj...@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 <jo...@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
>>>>>>>>>> <mj...@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 <mj...@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 <mj...@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 <jo...@bowlerhat.dev> Enviado el:
>>>>>>>>>>> jueves,
>>>>>>>> 31 de
>>>>>>>>>>> marzo de 2022 23:49
>>>>>>>>>>> Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
>>>>>>>>>>> <ro...@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<
>>>>>>>>> joshtynjala@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>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>
>>>
>
Re: New --watch compiler option
Posted by Harbs <ha...@gmail.com>.
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 <jo...@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 <ha...@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 <jo...@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 <ha...@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 <mj...@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 <mj...@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 <hf...@gmail.com> Enviado el: sábado, 9 de
>>>> abril de 2022 3:26
>>>>> Para: Apache Royale Development <de...@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 <hf...@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 <jo...@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.80@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 <mj...@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 <jo...@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
>>>>>>>>> <mj...@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 <mj...@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 <mj...@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 <jo...@bowlerhat.dev> Enviado el:
>>>>>>>>>> jueves,
>>>>>>> 31 de
>>>>>>>>>> marzo de 2022 23:49
>>>>>>>>>> Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
>>>>>>>>>> <ro...@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<
>>>>>>>> joshtynjala@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>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>>>
>>
>>
Re: New --watch compiler option
Posted by Josh Tynjala <jo...@bowlerhat.dev>.
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 <ha...@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 <jo...@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 <ha...@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 <mj...@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 <mj...@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 <hf...@gmail.com> Enviado el: sábado, 9 de
> >> abril de 2022 3:26
> >>> Para: Apache Royale Development <de...@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 <hf...@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 <jo...@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.80@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 <mj...@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 <jo...@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
> >>>>>>> <mj...@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 <mj...@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 <mj...@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 <jo...@bowlerhat.dev> Enviado el:
> >>>>>>>> jueves,
> >>>>> 31 de
> >>>>>>>> marzo de 2022 23:49
> >>>>>>>> Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> >>>>>>>> <ro...@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<
> >>>>>> joshtynjala@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>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>
> >>
>
>
Re: New --watch compiler option
Posted by Harbs <ha...@gmail.com>.
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 <jo...@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 <ha...@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 <mj...@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 <mj...@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 <hf...@gmail.com> Enviado el: sábado, 9 de
>> abril de 2022 3:26
>>> Para: Apache Royale Development <de...@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 <hf...@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 <jo...@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 <hf...@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 <mj...@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 <jo...@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
>>>>>>> <mj...@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 <mj...@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 <mj...@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 <jo...@bowlerhat.dev> Enviado el:
>>>>>>>> jueves,
>>>>> 31 de
>>>>>>>> marzo de 2022 23:49
>>>>>>>> Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
>>>>>>>> <ro...@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<
>>>>>> joshtynjala@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>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>
>>
Re: New --watch compiler option
Posted by Josh Tynjala <jo...@bowlerhat.dev>.
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 <ha...@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 <mj...@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 <mj...@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 <hf...@gmail.com> Enviado el: sábado, 9 de
> abril de 2022 3:26
> > Para: Apache Royale Development <de...@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 <hf...@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 <jo...@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 <hf...@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 <mj...@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 <jo...@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
> >>>>> <mj...@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 <mj...@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 <mj...@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 <jo...@bowlerhat.dev> Enviado el:
> >>>>>> jueves,
> >>> 31 de
> >>>>>> marzo de 2022 23:49
> >>>>>> Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> >>>>>> <ro...@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<
> >>>> joshtynjala@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>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
>
>
Re: New --watch compiler option
Posted by Harbs <ha...@gmail.com>.
Oh. And LiveServer works very well.
I have this in my settings:
"liveServer.settings.root": "bin/js-debug"
> On Apr 13, 2022, at 4:29 PM, Harbs <ha...@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 <mj...@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 <mj...@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 <hf...@gmail.com> Enviado el: sábado, 9 de abril de 2022 3:26
>> Para: Apache Royale Development <de...@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 <hf...@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 <jo...@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 <hf...@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 <mj...@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 <jo...@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
>>>>>> <mj...@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 <mj...@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 <mj...@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 <jo...@bowlerhat.dev> Enviado el:
>>>>>>> jueves,
>>>> 31 de
>>>>>>> marzo de 2022 23:49
>>>>>>> Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
>>>>>>> <ro...@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<
>>>>> joshtynjala@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>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>
Re: New --watch compiler option
Posted by Harbs <ha...@gmail.com>.
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 <mj...@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 <mj...@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 <hf...@gmail.com> Enviado el: sábado, 9 de abril de 2022 3:26
> Para: Apache Royale Development <de...@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 <hf...@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 <jo...@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 <hf...@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 <mj...@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 <jo...@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
>>>>> <mj...@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 <mj...@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 <mj...@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 <jo...@bowlerhat.dev> Enviado el:
>>>>>> jueves,
>>> 31 de
>>>>>> marzo de 2022 23:49
>>>>>> Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
>>>>>> <ro...@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<
>>>> joshtynjala@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>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
RE: New --watch compiler option
Posted by Maria Jose Esteve <mj...@iest.com>.
For now, I compile without --watch a first time and the following compilations with --watch without "clean".
I will test with the library as well.
Thanks Josh.
Hiedra
-----Mensaje original-----
De: Josh Tynjala <jo...@bowlerhat.dev>
Enviado el: miércoles, 13 de abril de 2022 21:57
Para: dev@royale.apache.org
Asunto: Re: New --watch compiler option
I was really hoping that Maven handled resource copying during the process-resources phase, but if it happens during the install phase, what you describe makes sense. I made it so that the Royale maven plugin doesn't continue beyond the compile phase when --watch is used.
I wonder if I can create a new Mojo that hooks into the install phase and pauses there instead.
--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>
On Sat, Apr 9, 2022 at 6:20 PM Maria Jose Esteve <mj...@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 <mj...@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 <hf...@gmail.com> Enviado el: sábado, 9 de
> abril de 2022 3:26
> Para: Apache Royale Development <de...@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 <hf...@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 <jo...@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
> >> <hf...@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 <mj...@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 <jo...@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
> >> > > <mj...@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:comp
> >> il
> >> 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:comp
> >> il
> >> 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.buildPro
> >> je
> >> c
> >> > > > t
> >> > > > (LifecycleModuleBuilder.java:117)
> >> > > > at
> >> > > >
> >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildPro
> >> je
> >> c
> >> > > > t
> >> > > > (LifecycleModuleBuilder.java:81)
> >> > > > at
> >> > > >
> >> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleTh
> >> re
> >> 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.launchEnhan
> >> > > > ce
> >> > > > d
> >> > > > (Launcher.java:282)
> >> > > > at
> >> > > > org.codehaus.plexus.classworlds.launcher.Launcher.launch
> >> > > > (Launcher.java:225)
> >> > > > at
> >> > > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExi
> >> > > > tC
> >> > > > 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.buildPro
> >> je
> >> c
> >> > > > t
> >> > > > (LifecycleModuleBuilder.java:117)
> >> > > > at
> >> > > >
> >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildPro
> >> je
> >> c
> >> > > > t
> >> > > > (LifecycleModuleBuilder.java:81)
> >> > > > at
> >> > > >
> >> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleTh
> >> re
> >> 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.launchEnhan
> >> > > > ce
> >> > > > d
> >> > > > (Launcher.java:282)
> >> > > > at
> >> > > > org.codehaus.plexus.classworlds.launcher.Launcher.launch
> >> > > > (Launcher.java:225)
> >> > > > at
> >> > > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExi
> >> > > > tC
> >> > > > 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/MojoExecutionExcep
> >> ti
> >> 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 <mj...@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 <mj...@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,PostConstr
> >> -keep-as3-metadata+uc
> >> -keep-as3-metadata+t
> >> > > >
> >> -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Trans
> >> -keep-as3-metadata+ie
> >> -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\roy
> >> al
> >> e
> >> > > > login\target\javascript,
> >> > > > -compiler.targets=JSRoyale,
> >> > > >
> >> D:\Develop_Royale\Projects\WinPlusWebSuite\royaleapp\royalelogin\sr
> >> c\
> >> 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:comp
> >> il
> >> 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(W
> >> at
> >> c
> >> > > > hThread.java:262)
> >> > > >
> >> > > > at
> >> > > >
> >> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchTh
> >> re
> >> a
> >> > > > d.java:130) Caused by: java.lang.ClassNotFoundException:
> >> > > > org.apache.royale.compiler.internal.watcher.WatchThread$1
> >> > > > at
> >> > > >
> >> > >
> >> >
> >> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClas
> >> s(
> >> SelfFirstStrategy.java:50)
> >> > > > at
> >> > > >
> >> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoad
> >> Cl
> >> a
> >> > > > ss(ClassRealm.java:271)
> >> > > >
> >> > > > at
> >> > > >
> >> > >
> >> >
> >> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRea
> >> lm
> >> .java:247)
> >> > > > at
> >> > > >
> >> > >
> >> >
> >> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRea
> >> lm
> >> .java:239)
> >> > > > ... 2 more
> >> > > >
> >> > > > [1]
> >> > > >
> >> https://drive.google.com/file/d/18CC4_6XQ4YwJujTyBLwqpkg5q6oTfXvy/v
> >> ie
> >> w
> >> > > > ?usp=sharing
> >> > > >
> >> > > >
> >> > > > Hiedra
> >> > > >
> >> > > > -----Mensaje original-----
> >> > > > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el:
> >> > > > jueves,
> >> 31 de
> >> > > > marzo de 2022 23:49
> >> > > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> >> > > > <ro...@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<
> >> > joshtynjala@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>
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
Re: New --watch compiler option
Posted by Josh Tynjala <jo...@bowlerhat.dev>.
I was really hoping that Maven handled resource copying during the
process-resources phase, but if it happens during the install phase, what
you describe makes sense. I made it so that the Royale maven plugin doesn't
continue beyond the compile phase when --watch is used.
I wonder if I can create a new Mojo that hooks into the install phase and
pauses there instead.
--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>
On Sat, Apr 9, 2022 at 6:20 PM Maria Jose Esteve <mj...@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 <mj...@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 <hf...@gmail.com> Enviado el: sábado, 9 de abril
> de 2022 3:26
> Para: Apache Royale Development <de...@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 <hf...@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 <jo...@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 <hf...@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 <mj...@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 <jo...@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
> >> > > <mj...@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 <mj...@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 <mj...@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 <jo...@bowlerhat.dev> Enviado el:
> >> > > > jueves,
> >> 31 de
> >> > > > marzo de 2022 23:49
> >> > > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> >> > > > <ro...@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<
> >> > joshtynjala@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>
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
RE: New --watch compiler option
Posted by Maria Jose Esteve <mj...@iest.com>.
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 <mj...@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 <hf...@gmail.com> Enviado el: sábado, 9 de abril de 2022 3:26
Para: Apache Royale Development <de...@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 <hf...@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 <jo...@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 <hf...@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 <mj...@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 <jo...@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
>> > > <mj...@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 <mj...@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 <mj...@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 <jo...@bowlerhat.dev> Enviado el:
>> > > > jueves,
>> 31 de
>> > > > marzo de 2022 23:49
>> > > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
>> > > > <ro...@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<
>> > joshtynjala@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>
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
RE: New --watch compiler option
Posted by Maria Jose Esteve <mj...@iest.com>.
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 <hf...@gmail.com>
Enviado el: sábado, 9 de abril de 2022 3:26
Para: Apache Royale Development <de...@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 <hf...@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 <jo...@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 <hf...@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 <mj...@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 <jo...@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
>> > > <mj...@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 <mj...@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 <mj...@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 <jo...@bowlerhat.dev> Enviado el:
>> > > > jueves,
>> 31 de
>> > > > marzo de 2022 23:49
>> > > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
>> > > > <ro...@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<
>> > joshtynjala@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>
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
Re: New --watch compiler option
Posted by Hugo Ferreira <hf...@gmail.com>.
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 <hf...@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 <jo...@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 <hf...@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 <mj...@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 <jo...@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 <mj...@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:compile
>> > > > -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:compile
>> > > > -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.buildProjec
>> > > > t
>> > > > (LifecycleModuleBuilder.java:117)
>> > > > at
>> > > >
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
>> > > > t
>> > > > (LifecycleModuleBuilder.java:81)
>> > > > at
>> > > >
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea
>> > > > 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.launchEnhanced
>> > > > (Launcher.java:282)
>> > > > at org.codehaus.plexus.classworlds.launcher.Launcher.launch
>> > > > (Launcher.java:225)
>> > > > at
>> > > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
>> > > > (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.buildProjec
>> > > > t
>> > > > (LifecycleModuleBuilder.java:117)
>> > > > at
>> > > >
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
>> > > > t
>> > > > (LifecycleModuleBuilder.java:81)
>> > > > at
>> > > >
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea
>> > > > 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.launchEnhanced
>> > > > (Launcher.java:282)
>> > > > at org.codehaus.plexus.classworlds.launcher.Launcher.launch
>> > > > (Launcher.java:225)
>> > > > at
>> > > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
>> > > > (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/MojoExecutionExceptio
>> > > > 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 <mj...@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 <mj...@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\roy
>> > > > 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,PostConstruct
>> > > >
>> -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transien
>> > > > -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\royale
>> > > > 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:compile
>> > > > -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(Watc
>> > > > hThread.java:262)
>> > > >
>> > > > at
>> > > >
>> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThrea
>> > > > 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.unsynchronizedLoadCla
>> > > > 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/view
>> > > > ?usp=sharing
>> > > >
>> > > >
>> > > > Hiedra
>> > > >
>> > > > -----Mensaje original-----
>> > > > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves,
>> 31 de
>> > > > marzo de 2022 23:49
>> > > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
>> > > > <ro...@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<
>> > joshtynjala@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>
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
Re: New --watch compiler option
Posted by Hugo Ferreira <hf...@gmail.com>.
Thank you.
You saved me and the Royale community countless hours of build - "wait" -
test.
You removed the "wait" from the equation :)
Josh Tynjala <jo...@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 <hf...@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 <mj...@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 <jo...@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 <mj...@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:compile
> > > > -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:compile
> > > > -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.buildProjec
> > > > t
> > > > (LifecycleModuleBuilder.java:117)
> > > > at
> > > >
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > > > t
> > > > (LifecycleModuleBuilder.java:81)
> > > > at
> > > >
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea
> > > > 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.launchEnhanced
> > > > (Launcher.java:282)
> > > > at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> > > > (Launcher.java:225)
> > > > at
> > > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> > > > (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.buildProjec
> > > > t
> > > > (LifecycleModuleBuilder.java:117)
> > > > at
> > > >
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > > > t
> > > > (LifecycleModuleBuilder.java:81)
> > > > at
> > > >
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea
> > > > 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.launchEnhanced
> > > > (Launcher.java:282)
> > > > at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> > > > (Launcher.java:225)
> > > > at
> > > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> > > > (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/MojoExecutionExceptio
> > > > 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 <mj...@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 <mj...@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\roy
> > > > 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,PostConstruct
> > > >
> -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transien
> > > > -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\royale
> > > > 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:compile
> > > > -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(Watc
> > > > hThread.java:262)
> > > >
> > > > at
> > > >
> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThrea
> > > > 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.unsynchronizedLoadCla
> > > > 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/view
> > > > ?usp=sharing
> > > >
> > > >
> > > > Hiedra
> > > >
> > > > -----Mensaje original-----
> > > > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves, 31
> de
> > > > marzo de 2022 23:49
> > > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> > > > <ro...@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<
> > joshtynjala@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>
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: New --watch compiler option
Posted by Josh Tynjala <jo...@bowlerhat.dev>.
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 <hf...@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 <mj...@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 <jo...@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 <mj...@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:compile
> > > -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:compile
> > > -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.buildProjec
> > > t
> > > (LifecycleModuleBuilder.java:117)
> > > at
> > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > > t
> > > (LifecycleModuleBuilder.java:81)
> > > at
> > > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea
> > > 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.launchEnhanced
> > > (Launcher.java:282)
> > > at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> > > (Launcher.java:225)
> > > at
> > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> > > (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.buildProjec
> > > t
> > > (LifecycleModuleBuilder.java:117)
> > > at
> > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > > t
> > > (LifecycleModuleBuilder.java:81)
> > > at
> > > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea
> > > 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.launchEnhanced
> > > (Launcher.java:282)
> > > at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> > > (Launcher.java:225)
> > > at
> > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> > > (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/MojoExecutionExceptio
> > > 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 <mj...@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 <mj...@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\roy
> > > 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,PostConstruct
> > > -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transien
> > > -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\royale
> > > 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:compile
> > > -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(Watc
> > > hThread.java:262)
> > >
> > > at
> > > org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThrea
> > > 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.unsynchronizedLoadCla
> > > 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/view
> > > ?usp=sharing
> > >
> > >
> > > Hiedra
> > >
> > > -----Mensaje original-----
> > > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves, 31 de
> > > marzo de 2022 23:49
> > > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> > > <ro...@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<
> joshtynjala@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>
> > > >
> > > >
> > >
> >
>
Re: New --watch compiler option
Posted by Hugo Ferreira <hf...@gmail.com>.
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 <mj...@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 <jo...@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 <mj...@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:compile
> > -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:compile
> > -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.buildProjec
> > t
> > (LifecycleModuleBuilder.java:117)
> > at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > t
> > (LifecycleModuleBuilder.java:81)
> > at
> > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea
> > 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.launchEnhanced
> > (Launcher.java:282)
> > at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> > (Launcher.java:225)
> > at
> > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> > (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.buildProjec
> > t
> > (LifecycleModuleBuilder.java:117)
> > at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> > t
> > (LifecycleModuleBuilder.java:81)
> > at
> > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea
> > 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.launchEnhanced
> > (Launcher.java:282)
> > at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> > (Launcher.java:225)
> > at
> > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> > (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/MojoExecutionExceptio
> > 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 <mj...@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 <mj...@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\roy
> > 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,PostConstruct
> > -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transien
> > -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\royale
> > 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:compile
> > -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(Watc
> > hThread.java:262)
> >
> > at
> > org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThrea
> > 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.unsynchronizedLoadCla
> > 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/view
> > ?usp=sharing
> >
> >
> > Hiedra
> >
> > -----Mensaje original-----
> > De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves, 31 de
> > marzo de 2022 23:49
> > Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> > <ro...@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<joshtynjala@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>
> > >
> > >
> >
>
RE: New --watch compiler option
Posted by Maria Jose Esteve <mj...@iest.com>.
Hi Josh, thx
I will compile the sdk and come back here with the results.
Hiedra
-----Mensaje original-----
De: Josh Tynjala <jo...@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 <mj...@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:compile
> -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:compile
> -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.buildProjec
> t
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea
> 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.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (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.buildProjec
> t
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProjec
> t
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThrea
> 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.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (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/MojoExecutionExceptio
> 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 <mj...@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 <mj...@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\roy
> 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,PostConstruct
> -keep-as3-metadata+,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transien
> -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\royale
> 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:compile
> -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(Watc
> hThread.java:262)
>
> at
> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThrea
> 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.unsynchronizedLoadCla
> 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/view
> ?usp=sharing
>
>
> Hiedra
>
> -----Mensaje original-----
> De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves, 31 de
> marzo de 2022 23:49
> Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> <ro...@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<jo...@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>
> >
> >
>
Re: New --watch compiler option
Posted by Josh Tynjala <jo...@bowlerhat.dev>.
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 <mj...@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:compile-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:compile-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.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.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.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (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.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.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.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (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/MojoExecutionException
> [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 <mj...@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 <mj...@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\royalelogin\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,PostConstruct,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transient,
> -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\royalelogin\target\javascript,
> -compiler.targets=JSRoyale,
> D:\Develop_Royale\Projects\WinPlusWebSuite\royaleapp\royalelogin\src\main\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:compile-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(WatchThread.java:262)
>
> at
> org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThread.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.unsynchronizedLoadClass(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/view?usp=sharing
>
>
> Hiedra
>
> -----Mensaje original-----
> De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves, 31 de
> marzo de 2022 23:49
> Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID
> <ro...@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<jo...@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>
> >
> >
>
RE: New --watch compiler option
Posted by Maria Jose Esteve <mj...@iest.com>.
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:compile-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:compile-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.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.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.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (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.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.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.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (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/MojoExecutionException
[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 <mj...@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 <mj...@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\royalelogin\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,PostConstruct,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transient, -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\royalelogin\target\javascript, -compiler.targets=JSRoyale, D:\Develop_Royale\Projects\WinPlusWebSuite\royaleapp\royalelogin\src\main\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:compile-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(WatchThread.java:262)
at org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThread.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.unsynchronizedLoadClass(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/view?usp=sharing
Hiedra
-----Mensaje original-----
De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves, 31 de marzo de 2022 23:49
Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID <ro...@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<jo...@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>
>
>
RE: New --watch compiler option
Posted by Maria Jose Esteve <mj...@iest.com>.
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 <mj...@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\royalelogin\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,PostConstruct,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transient, -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\royalelogin\target\javascript, -compiler.targets=JSRoyale, D:\Develop_Royale\Projects\WinPlusWebSuite\royaleapp\royalelogin\src\main\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:compile-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(WatchThread.java:262)
at org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThread.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.unsynchronizedLoadClass(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/view?usp=sharing
Hiedra
-----Mensaje original-----
De: Josh Tynjala <jo...@bowlerhat.dev> Enviado el: jueves, 31 de marzo de 2022 23:49
Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID <ro...@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<jo...@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>
>
>
RE: New --watch compiler option
Posted by Maria Jose Esteve <mj...@iest.com>.
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\royalelogin\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,PostConstruct,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transient, -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\royalelogin\target\javascript, -compiler.targets=JSRoyale, D:\Develop_Royale\Projects\WinPlusWebSuite\royaleapp\royalelogin\src\main\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:compile-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(WatchThread.java:262)
at org.apache.royale.compiler.internal.watcher.WatchThread.run(WatchThread.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.unsynchronizedLoadClass(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/view?usp=sharing
Hiedra
-----Mensaje original-----
De: Josh Tynjala <jo...@bowlerhat.dev>
Enviado el: jueves, 31 de marzo de 2022 23:49
Para: dev@royale.apache.org; romanisitua@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 romanisitua@yahoo.com.INVALID <ro...@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<jo...@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>
>
>
Re: New --watch compiler option
Posted by Hugo Ferreira <hf...@gmail.com>.
After update and compile the framework with ANT, I add --watch (also tryied
-watch) to additionalOptions of asconfig.json (I'm using VS Code) and I got:
unknown configuration variable 'watch'.
Hugo Ferreira <hf...@gmail.com> escreveu no dia quinta, 31/03/2022
à(s) 22:54:
> I'm just updated Royale and I'm now compiling with ANT.
> I have a Mac Book with 4 years (so it's Intel) and it takes about 15
> minutes to compile Royale.
> Then I will made a few tests and let you know.
>
>
> Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia quinta,
> 31/03/2022 à(s) 22:49:
>
>> 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 romanisitua@yahoo.com.INVALID
>> <ro...@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<jo...@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-command-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>
>> >
>> >
>>
>
Re: New --watch compiler option
Posted by Hugo Ferreira <hf...@gmail.com>.
I'm just updated Royale and I'm now compiling with ANT.
I have a Mac Book with 4 years (so it's Intel) and it takes about 15
minutes to compile Royale.
Then I will made a few tests and let you know.
Josh Tynjala <jo...@bowlerhat.dev> escreveu no dia quinta, 31/03/2022
à(s) 22:49:
> 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 romanisitua@yahoo.com.INVALID
> <ro...@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<jo...@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-command-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>
> >
> >
>
Re: New --watch compiler option
Posted by Josh Tynjala <jo...@bowlerhat.dev>.
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 romanisitua@yahoo.com.INVALID
<ro...@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<jo...@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-command-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>
>
>
Re: New --watch compiler option
Posted by "romanisitua@yahoo.com.INVALID" <ro...@yahoo.com.INVALID>.
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<jo...@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-command-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>