You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Maria Jose Esteve <mj...@iest.com> on 2020/01/08 13:10:31 UTC

Error after compiled develop branch

Hi,
this morning we have compiled the develop branch of the sdk 0.9.7 and, since then, we cannot compile our application (maven).

This is an excerpt from the log:

...
[DEBUG] Skipped remote request for org.apache.royale.framework:Basic:0.9.7-SNAPSHOT/maven-metadata.xml locally installed metadata up-to-date.
[INFO] Executing MXMLC in tool group Royale with args: [-load-config=D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\royaleapp\royalelogin\target\compile-app-config.xml, -js-default-initializers=true, -source-map=true, -compiler.exclude-defaults-css-files=MXRoyale-0.9.7-SNAPSHOT-js.swc:defaults.css, -keep-as3-metadata+=Inject,Dispatcher,EventHandler,PostConstruct,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transient, -keep-code-with-metadata=Inject, -js-output=D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\royaleapp\royalelogin\target\javascript, -compiler.targets=JSRoyale, D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\royaleapp\royalelogin\src\main\royale\App.mxml]
D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82): col: 2 Error: Type selector without namespace prefix requires a default namespace to be defined. a:visited


D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82): col: 2 Error: Type selector without namespace prefix requires a default namespace to be defined. a:visited


D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82): col: 2 Error: Type selector without namespace prefix requires a default namespace to be defined. a:visited


D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86): col: 2 Error: Type selector without namespace prefix requires a default namespace to be defined. a:hover


D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86): col: 2 Error: Type selector without namespace prefix requires a default namespace to be defined. a:hover


D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86): col: 2 Error: Type selector without namespace prefix requires a default namespace to be defined. a:hover


D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90): col: 2 Error: Type selector without namespace prefix requires a default namespace to be defined. a:active


D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90): col: 2 Error: Type selector without namespace prefix requires a default namespace to be defined. a:active


D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90): col: 2 Error: Type selector without namespace prefix requires a default namespace to be defined. a:active


[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Suite Plus 1.0.0-SNAPSHOT:
[INFO]
[INFO] Suite Plus ................................... SUCCESS [  0.644 s]
[INFO] Royale Libs ........................................ SUCCESS [  0.604 s]
[INFO] Royale Libs Components ............................. SUCCESS [  8.316 s]
[INFO] Royale Libs DTO .................................... SUCCESS [  7.178 s]
[INFO] Royale Libs Arq .................................... SUCCESS [  4.920 s]
[INFO] Royale Libs Security ............................... SUCCESS [  5.502 s]
[INFO] Royale App And Modules ............................. SUCCESS [  0.329 s]
[INFO] Royale Application ................................. FAILURE [  3.007 s]
[INFO] Royale Libs Test ................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  32.670 s
[INFO] Finished at: 2020-01-08T14:00:46+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.royale.compiler:royale-maven-plugin:0.9.7-SNAPSHOT:compile-app (default-compile-app) on project royalelogin: There were errors during the build. Got return code 3 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.royale.compiler:royale-maven-plugin:0.9.7-SNAPSHOT:compile-app (default-compile-app) on project royalelogin: There were errors during the build. Got return code 3
    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 3
    at org.apache.royale.maven.BaseMojo.handleExitCode (BaseMojo.java:382)
    at org.apache.royale.maven.BaseMojo.execute (BaseMojo.java:376)
    at org.apache.royale.maven.CompileAppMojo.execute (CompileAppMojo.java:107)
    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]

Has it happened to someone else?
How can I report this error if it is?

Thank you,
Hiedra.

RE: Error after compiled develop branch

Posted by Maria Jose Esteve <mj...@iest.com>.
Hi Carlos,
Everything works perfect now. You have compiled and reloaded the selected theme.

Thank you
Hiedra

-----Mensaje original-----
De: Carlos Rovira <ca...@apache.org> 
Enviado el: miércoles, 8 de enero de 2020 18:24
Para: dev@royale.apache.org
Asunto: Re: Error after compiled develop branch

Hi Maria Jose,
fix is already done in this
commit: 3652f3d72e9d2258077850708d475bd8294f8fca (jewel-themes: fix usage of separated themes that was broken due to a recent optimization) sorry for the inconvenience

El mié., 8 ene. 2020 a las 16:48, Maria Jose Esteve (<mj...@iest.com>)
escribió:

> Thank you for your attention Carlos.
>
> We already compile.
> I will be attentive to progress.
>
> Thank you,
> Hiedra
>
> -----Mensaje original-----
> De: Carlos Rovira <ca...@apache.org> Enviado el: miércoles, 8 
> de enero de 2020 16:03
> Para: dev@royale.apache.org
> Asunto: Re: Error after compiled develop branch
>
> Hi Maria Jose,
>
> thanks for reporting. I could reproduce that bug. I'll be fixing now.
> In the meantime, please, change the pom.xml with the 3 jewel theme 
> dependencies with the master jewel theme:
>
> <dependency>
> <groupId>org.apache.royale.framework</groupId>
> <artifactId>JewelTheme</artifactId>
> <version>0.9.7-SNAPSHOT</version>
> <type>swc</type>
> <scope>theme</scope>
> <classifier>js</classifier>
> </dependency>
>
> In this way you'll be able to compile
> I'll report here when this problem is resolved, hopefully very soon 
> And sorry for the inconvenience, this was introduced when I develop 
> this days the runtime theme switch feature Thanks!
>
> Carlos
>
> El mié., 8 ene. 2020 a las 14:10, Maria Jose Esteve 
> (<mj...@iest.com>)
> escribió:
>
> > Hi,
> > this morning we have compiled the develop branch of the sdk 0.9.7 
> > and, since then, we cannot compile our application (maven).
> >
> > This is an excerpt from the log:
> >
> > ...
> > [DEBUG] Skipped remote request for
> > org.apache.royale.framework:Basic:0.9.7-SNAPSHOT/maven-metadata.xml
> > locally installed metadata up-to-date.
> > [INFO] Executing MXMLC in tool group Royale with args:
> > [-load-config=D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\roy
> > al eapp\royalelogin\target\compile-app-config.xml,
> > -js-default-initializers=true, -source-map=true, 
> > -compiler.exclude-defaults-css-files=MXRoyale-0.9.7-SNAPSHOT-js.swc:
> > de
> > faults.css,
> > -keep-as3-metadata+=Inject,Dispatcher,EventHandler,PostConstruct,Pre
> > -keep-as3-metadata+De 
> > -keep-as3-metadata+stroy,ViewAdded,ViewRemoved,Bindable,Transient,
> > -keep-code-with-metadata=Inject,
> > -js-output=D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\royale
> > ap
> > p\royalelogin\target\javascript,
> > -compiler.targets=JSRoyale,
> > D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\royaleapp\royalel
> > og
> > in\src\main\royale\App.mxml]
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82):
> > col: 2 Error: Type selector without namespace prefix requires a 
> > default namespace to be defined. a:visited
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82):
> > col: 2 Error: Type selector without namespace prefix requires a 
> > default namespace to be defined. a:visited
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82):
> > col: 2 Error: Type selector without namespace prefix requires a 
> > default namespace to be defined. a:visited
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86):
> > col: 2 Error: Type selector without namespace prefix requires a 
> > default namespace to be defined. a:hover
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86):
> > col: 2 Error: Type selector without namespace prefix requires a 
> > default namespace to be defined. a:hover
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86):
> > col: 2 Error: Type selector without namespace prefix requires a 
> > default namespace to be defined. a:hover
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90):
> > col: 2 Error: Type selector without namespace prefix requires a 
> > default namespace to be defined. a:active
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90):
> > col: 2 Error: Type selector without namespace prefix requires a 
> > default namespace to be defined. a:active
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90):
> > col: 2 Error: Type selector without namespace prefix requires a 
> > default namespace to be defined. a:active
> >
> >
> > [INFO]
> > --------------------------------------------------------------------
> > --
> > -- [INFO] Reactor Summary for Suite Plus 1.0.0-SNAPSHOT:
> > [INFO]
> > [INFO] Suite Plus ................................... SUCCESS [  
> > 0.644 s] [INFO] Royale Libs ........................................ 
> > SUCCESS [
> > 0.604 s]
> > [INFO] Royale Libs Components ............................. SUCCESS 
> > [
> > 8.316 s]
> > [INFO] Royale Libs DTO .................................... SUCCESS 
> > [
> > 7.178 s]
> > [INFO] Royale Libs Arq .................................... SUCCESS 
> > [
> > 4.920 s]
> > [INFO] Royale Libs Security ............................... SUCCESS 
> > [
> > 5.502 s]
> > [INFO] Royale App And Modules ............................. SUCCESS 
> > [
> > 0.329 s]
> > [INFO] Royale Application ................................. FAILURE 
> > [
> > 3.007 s]
> > [INFO] Royale Libs Test ................................... SKIPPED 
> > [INFO]
> > --------------------------------------------------------------------
> > --
> > --
> > [INFO] BUILD FAILURE
> > [INFO]
> > --------------------------------------------------------------------
> > --
> > --
> > [INFO] Total time:  32.670 s
> > [INFO] Finished at: 2020-01-08T14:00:46+01:00 [INFO]
> > --------------------------------------------------------------------
> > --
> > --
> > [ERROR] Failed to execute goal
> > org.apache.royale.compiler:royale-maven-plugin:0.9.7-SNAPSHOT:compil
> > e-
> > app
> > (default-compile-app) on project royalelogin: There were errors 
> > during the build. Got return code 3 -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
> > execute goal
> > org.apache.royale.compiler:royale-maven-plugin:0.9.7-SNAPSHOT:compil
> > e-
> > app
> > (default-compile-app) on project royalelogin: There were errors 
> > during the build. Got return code 3
> >     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.buildProj
> > ec
> > t
> > (LifecycleModuleBuilder.java:117)
> >     at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProj
> > ec
> > t
> > (LifecycleModuleBuilder.java:81)
> >     at
> > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThr
> > ea
> > 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 3
> >     at org.apache.royale.maven.BaseMojo.handleExitCode
> (BaseMojo.java:382)
> >     at org.apache.royale.maven.BaseMojo.execute (BaseMojo.java:376)
> >     at org.apache.royale.maven.CompileAppMojo.execute
> > (CompileAppMojo.java:107)
> >     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.buildProj
> > ec
> > t
> > (LifecycleModuleBuilder.java:117)
> >     at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProj
> > ec
> > t
> > (LifecycleModuleBuilder.java:81)
> >     at
> > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThr
> > ea
> > 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]
> >
> > Has it happened to someone else?
> > How can I report this error if it is?
> >
> > Thank you,
> > Hiedra.
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


--
Carlos Rovira
http://about.me/carlosrovira

Re: Error after compiled develop branch

Posted by Carlos Rovira <ca...@apache.org>.
Hi Maria Jose,
fix is already done in this
commit: 3652f3d72e9d2258077850708d475bd8294f8fca (jewel-themes: fix usage
of separated themes that was broken due to a recent optimization)
sorry for the inconvenience

El mié., 8 ene. 2020 a las 16:48, Maria Jose Esteve (<mj...@iest.com>)
escribió:

> Thank you for your attention Carlos.
>
> We already compile.
> I will be attentive to progress.
>
> Thank you,
> Hiedra
>
> -----Mensaje original-----
> De: Carlos Rovira <ca...@apache.org>
> Enviado el: miércoles, 8 de enero de 2020 16:03
> Para: dev@royale.apache.org
> Asunto: Re: Error after compiled develop branch
>
> Hi Maria Jose,
>
> thanks for reporting. I could reproduce that bug. I'll be fixing now.
> In the meantime, please, change the pom.xml with the 3 jewel theme
> dependencies with the master jewel theme:
>
> <dependency>
> <groupId>org.apache.royale.framework</groupId>
> <artifactId>JewelTheme</artifactId>
> <version>0.9.7-SNAPSHOT</version>
> <type>swc</type>
> <scope>theme</scope>
> <classifier>js</classifier>
> </dependency>
>
> In this way you'll be able to compile
> I'll report here when this problem is resolved, hopefully very soon And
> sorry for the inconvenience, this was introduced when I develop this days
> the runtime theme switch feature Thanks!
>
> Carlos
>
> El mié., 8 ene. 2020 a las 14:10, Maria Jose Esteve (<mj...@iest.com>)
> escribió:
>
> > Hi,
> > this morning we have compiled the develop branch of the sdk 0.9.7 and,
> > since then, we cannot compile our application (maven).
> >
> > This is an excerpt from the log:
> >
> > ...
> > [DEBUG] Skipped remote request for
> > org.apache.royale.framework:Basic:0.9.7-SNAPSHOT/maven-metadata.xml
> > locally installed metadata up-to-date.
> > [INFO] Executing MXMLC in tool group Royale with args:
> > [-load-config=D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\royal
> > eapp\royalelogin\target\compile-app-config.xml,
> > -js-default-initializers=true, -source-map=true,
> > -compiler.exclude-defaults-css-files=MXRoyale-0.9.7-SNAPSHOT-js.swc:de
> > faults.css,
> > -keep-as3-metadata+=Inject,Dispatcher,EventHandler,PostConstruct,PreDe
> > -keep-as3-metadata+stroy,ViewAdded,ViewRemoved,Bindable,Transient,
> > -keep-code-with-metadata=Inject,
> > -js-output=D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\royaleap
> > p\royalelogin\target\javascript,
> > -compiler.targets=JSRoyale,
> > D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\royaleapp\royalelog
> > in\src\main\royale\App.mxml]
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82):
> > col: 2 Error: Type selector without namespace prefix requires a
> > default namespace to be defined. a:visited
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82):
> > col: 2 Error: Type selector without namespace prefix requires a
> > default namespace to be defined. a:visited
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82):
> > col: 2 Error: Type selector without namespace prefix requires a
> > default namespace to be defined. a:visited
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86):
> > col: 2 Error: Type selector without namespace prefix requires a
> > default namespace to be defined. a:hover
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86):
> > col: 2 Error: Type selector without namespace prefix requires a
> > default namespace to be defined. a:hover
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86):
> > col: 2 Error: Type selector without namespace prefix requires a
> > default namespace to be defined. a:hover
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90):
> > col: 2 Error: Type selector without namespace prefix requires a
> > default namespace to be defined. a:active
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90):
> > col: 2 Error: Type selector without namespace prefix requires a
> > default namespace to be defined. a:active
> >
> >
> >
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90):
> > col: 2 Error: Type selector without namespace prefix requires a
> > default namespace to be defined. a:active
> >
> >
> > [INFO]
> > ----------------------------------------------------------------------
> > -- [INFO] Reactor Summary for Suite Plus 1.0.0-SNAPSHOT:
> > [INFO]
> > [INFO] Suite Plus ................................... SUCCESS [  0.644
> > s] [INFO] Royale Libs ........................................ SUCCESS
> > [
> > 0.604 s]
> > [INFO] Royale Libs Components ............................. SUCCESS [
> > 8.316 s]
> > [INFO] Royale Libs DTO .................................... SUCCESS [
> > 7.178 s]
> > [INFO] Royale Libs Arq .................................... SUCCESS [
> > 4.920 s]
> > [INFO] Royale Libs Security ............................... SUCCESS [
> > 5.502 s]
> > [INFO] Royale App And Modules ............................. SUCCESS [
> > 0.329 s]
> > [INFO] Royale Application ................................. FAILURE [
> > 3.007 s]
> > [INFO] Royale Libs Test ................................... SKIPPED
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> > [INFO] BUILD FAILURE
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> > [INFO] Total time:  32.670 s
> > [INFO] Finished at: 2020-01-08T14:00:46+01:00 [INFO]
> > ----------------------------------------------------------------------
> > --
> > [ERROR] Failed to execute goal
> > org.apache.royale.compiler:royale-maven-plugin:0.9.7-SNAPSHOT:compile-
> > app
> > (default-compile-app) on project royalelogin: There were errors during
> > the build. Got return code 3 -> [Help 1]
> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> > execute goal
> > org.apache.royale.compiler:royale-maven-plugin:0.9.7-SNAPSHOT:compile-
> > app
> > (default-compile-app) on project royalelogin: There were errors during
> > the build. Got return code 3
> >     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 3
> >     at org.apache.royale.maven.BaseMojo.handleExitCode
> (BaseMojo.java:382)
> >     at org.apache.royale.maven.BaseMojo.execute (BaseMojo.java:376)
> >     at org.apache.royale.maven.CompileAppMojo.execute
> > (CompileAppMojo.java:107)
> >     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]
> >
> > Has it happened to someone else?
> > How can I report this error if it is?
> >
> > Thank you,
> > Hiedra.
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Carlos Rovira
http://about.me/carlosrovira

RE: Error after compiled develop branch

Posted by Maria Jose Esteve <mj...@iest.com>.
Thank you for your attention Carlos.

We already compile.
I will be attentive to progress.

Thank you,
Hiedra

-----Mensaje original-----
De: Carlos Rovira <ca...@apache.org> 
Enviado el: miércoles, 8 de enero de 2020 16:03
Para: dev@royale.apache.org
Asunto: Re: Error after compiled develop branch

Hi Maria Jose,

thanks for reporting. I could reproduce that bug. I'll be fixing now.
In the meantime, please, change the pom.xml with the 3 jewel theme dependencies with the master jewel theme:

<dependency>
<groupId>org.apache.royale.framework</groupId>
<artifactId>JewelTheme</artifactId>
<version>0.9.7-SNAPSHOT</version>
<type>swc</type>
<scope>theme</scope>
<classifier>js</classifier>
</dependency>

In this way you'll be able to compile
I'll report here when this problem is resolved, hopefully very soon And sorry for the inconvenience, this was introduced when I develop this days the runtime theme switch feature Thanks!

Carlos

El mié., 8 ene. 2020 a las 14:10, Maria Jose Esteve (<mj...@iest.com>)
escribió:

> Hi,
> this morning we have compiled the develop branch of the sdk 0.9.7 and, 
> since then, we cannot compile our application (maven).
>
> This is an excerpt from the log:
>
> ...
> [DEBUG] Skipped remote request for
> org.apache.royale.framework:Basic:0.9.7-SNAPSHOT/maven-metadata.xml 
> locally installed metadata up-to-date.
> [INFO] Executing MXMLC in tool group Royale with args:
> [-load-config=D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\royal
> eapp\royalelogin\target\compile-app-config.xml,
> -js-default-initializers=true, -source-map=true, 
> -compiler.exclude-defaults-css-files=MXRoyale-0.9.7-SNAPSHOT-js.swc:de
> faults.css,
> -keep-as3-metadata+=Inject,Dispatcher,EventHandler,PostConstruct,PreDe
> -keep-as3-metadata+stroy,ViewAdded,ViewRemoved,Bindable,Transient,
> -keep-code-with-metadata=Inject,
> -js-output=D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\royaleap
> p\royalelogin\target\javascript,
> -compiler.targets=JSRoyale,
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\royaleapp\royalelog
> in\src\main\royale\App.mxml]
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82):
> col: 2 Error: Type selector without namespace prefix requires a 
> default namespace to be defined. a:visited
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82):
> col: 2 Error: Type selector without namespace prefix requires a 
> default namespace to be defined. a:visited
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82):
> col: 2 Error: Type selector without namespace prefix requires a 
> default namespace to be defined. a:visited
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86):
> col: 2 Error: Type selector without namespace prefix requires a 
> default namespace to be defined. a:hover
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86):
> col: 2 Error: Type selector without namespace prefix requires a 
> default namespace to be defined. a:hover
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86):
> col: 2 Error: Type selector without namespace prefix requires a 
> default namespace to be defined. a:hover
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90):
> col: 2 Error: Type selector without namespace prefix requires a 
> default namespace to be defined. a:active
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90):
> col: 2 Error: Type selector without namespace prefix requires a 
> default namespace to be defined. a:active
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90):
> col: 2 Error: Type selector without namespace prefix requires a 
> default namespace to be defined. a:active
>
>
> [INFO]
> ----------------------------------------------------------------------
> -- [INFO] Reactor Summary for Suite Plus 1.0.0-SNAPSHOT:
> [INFO]
> [INFO] Suite Plus ................................... SUCCESS [  0.644 
> s] [INFO] Royale Libs ........................................ SUCCESS 
> [
> 0.604 s]
> [INFO] Royale Libs Components ............................. SUCCESS [
> 8.316 s]
> [INFO] Royale Libs DTO .................................... SUCCESS [
> 7.178 s]
> [INFO] Royale Libs Arq .................................... SUCCESS [
> 4.920 s]
> [INFO] Royale Libs Security ............................... SUCCESS [
> 5.502 s]
> [INFO] Royale App And Modules ............................. SUCCESS [
> 0.329 s]
> [INFO] Royale Application ................................. FAILURE [
> 3.007 s]
> [INFO] Royale Libs Test ................................... SKIPPED 
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] BUILD FAILURE
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Total time:  32.670 s
> [INFO] Finished at: 2020-01-08T14:00:46+01:00 [INFO]
> ----------------------------------------------------------------------
> --
> [ERROR] Failed to execute goal
> org.apache.royale.compiler:royale-maven-plugin:0.9.7-SNAPSHOT:compile-
> app
> (default-compile-app) on project royalelogin: There were errors during 
> the build. Got return code 3 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
> execute goal 
> org.apache.royale.compiler:royale-maven-plugin:0.9.7-SNAPSHOT:compile-
> app
> (default-compile-app) on project royalelogin: There were errors during 
> the build. Got return code 3
>     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 3
>     at org.apache.royale.maven.BaseMojo.handleExitCode (BaseMojo.java:382)
>     at org.apache.royale.maven.BaseMojo.execute (BaseMojo.java:376)
>     at org.apache.royale.maven.CompileAppMojo.execute
> (CompileAppMojo.java:107)
>     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]
>
> Has it happened to someone else?
> How can I report this error if it is?
>
> Thank you,
> Hiedra.
>


--
Carlos Rovira
http://about.me/carlosrovira

Re: Error after compiled develop branch

Posted by Carlos Rovira <ca...@apache.org>.
Hi Maria Jose,

thanks for reporting. I could reproduce that bug. I'll be fixing now.
In the meantime, please, change the pom.xml with the 3 jewel theme
dependencies with the master jewel theme:

<dependency>
<groupId>org.apache.royale.framework</groupId>
<artifactId>JewelTheme</artifactId>
<version>0.9.7-SNAPSHOT</version>
<type>swc</type>
<scope>theme</scope>
<classifier>js</classifier>
</dependency>

In this way you'll be able to compile
I'll report here when this problem is resolved, hopefully very soon
And sorry for the inconvenience, this was introduced when I develop this
days the runtime theme switch feature
Thanks!

Carlos

El mié., 8 ene. 2020 a las 14:10, Maria Jose Esteve (<mj...@iest.com>)
escribió:

> Hi,
> this morning we have compiled the develop branch of the sdk 0.9.7 and,
> since then, we cannot compile our application (maven).
>
> This is an excerpt from the log:
>
> ...
> [DEBUG] Skipped remote request for
> org.apache.royale.framework:Basic:0.9.7-SNAPSHOT/maven-metadata.xml locally
> installed metadata up-to-date.
> [INFO] Executing MXMLC in tool group Royale with args:
> [-load-config=D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\royaleapp\royalelogin\target\compile-app-config.xml,
> -js-default-initializers=true, -source-map=true,
> -compiler.exclude-defaults-css-files=MXRoyale-0.9.7-SNAPSHOT-js.swc:defaults.css,
> -keep-as3-metadata+=Inject,Dispatcher,EventHandler,PostConstruct,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transient,
> -keep-code-with-metadata=Inject,
> -js-output=D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\royaleapp\royalelogin\target\javascript,
> -compiler.targets=JSRoyale,
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\royaleapp\royalelogin\src\main\royale\App.mxml]
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82):
> col: 2 Error: Type selector without namespace prefix requires a default
> namespace to be defined. a:visited
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82):
> col: 2 Error: Type selector without namespace prefix requires a default
> namespace to be defined. a:visited
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(82):
> col: 2 Error: Type selector without namespace prefix requires a default
> namespace to be defined. a:visited
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86):
> col: 2 Error: Type selector without namespace prefix requires a default
> namespace to be defined. a:hover
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86):
> col: 2 Error: Type selector without namespace prefix requires a default
> namespace to be defined. a:hover
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(86):
> col: 2 Error: Type selector without namespace prefix requires a default
> namespace to be defined. a:hover
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90):
> col: 2 Error: Type selector without namespace prefix requires a default
> namespace to be defined. a:active
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90):
> col: 2 Error: Type selector without namespace prefix requires a default
> namespace to be defined. a:active
>
>
> D:\Desarrollo_Royale\Proyectos\Splus\Splus.develop\Jewel-Light-NoFlat-Secondary-Red-Theme-0.9.7-SNAPSHOT-js.swc:defaults.css(90):
> col: 2 Error: Type selector without namespace prefix requires a default
> namespace to be defined. a:active
>
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary for Suite Plus 1.0.0-SNAPSHOT:
> [INFO]
> [INFO] Suite Plus ................................... SUCCESS [  0.644 s]
> [INFO] Royale Libs ........................................ SUCCESS [
> 0.604 s]
> [INFO] Royale Libs Components ............................. SUCCESS [
> 8.316 s]
> [INFO] Royale Libs DTO .................................... SUCCESS [
> 7.178 s]
> [INFO] Royale Libs Arq .................................... SUCCESS [
> 4.920 s]
> [INFO] Royale Libs Security ............................... SUCCESS [
> 5.502 s]
> [INFO] Royale App And Modules ............................. SUCCESS [
> 0.329 s]
> [INFO] Royale Application ................................. FAILURE [
> 3.007 s]
> [INFO] Royale Libs Test ................................... SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time:  32.670 s
> [INFO] Finished at: 2020-01-08T14:00:46+01:00
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.royale.compiler:royale-maven-plugin:0.9.7-SNAPSHOT:compile-app
> (default-compile-app) on project royalelogin: There were errors during the
> build. Got return code 3 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal
> org.apache.royale.compiler:royale-maven-plugin:0.9.7-SNAPSHOT:compile-app
> (default-compile-app) on project royalelogin: There were errors during the
> build. Got return code 3
>     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 3
>     at org.apache.royale.maven.BaseMojo.handleExitCode (BaseMojo.java:382)
>     at org.apache.royale.maven.BaseMojo.execute (BaseMojo.java:376)
>     at org.apache.royale.maven.CompileAppMojo.execute
> (CompileAppMojo.java:107)
>     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]
>
> Has it happened to someone else?
> How can I report this error if it is?
>
> Thank you,
> Hiedra.
>


-- 
Carlos Rovira
http://about.me/carlosrovira