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 <[email protected]>
Enviado el: viernes, 1 de abril de 2022 12:08
Para: [email protected]
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 <[email protected]> Enviado el: viernes, 1 de abril de
2022 11:38
Para: [email protected]
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 <[email protected]> Enviado el: jueves, 31 de marzo de
2022 23:49
Para: [email protected]; [email protected]
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 [email protected]
<[email protected]> 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<[email protected]>
> 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>
>
>
