Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

Hi Chris,

I think those changes are good to be merg. Yishay is going to start release
maybe it’s worth to do this before.

Thanks,
Piotr

On Wed, 17 Mar 2021 at 10:36, Maria Jose Esteve  wrote:

> Chris, I just compiled your last change and everything is ok.
>
> Hiedra
>
> -Mensaje original-
> De: Christofer Dutz 
> Enviado el: miércoles, 17 de marzo de 2021 10:14
> Para: dev@royale.apache.org
> Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hi all,
>
> Ok .. so, I stripped down the Maven distribution to only contain the jars
> the Ant version uses. Before that I could see most dependencies related to
> the royale-maven-plugin pulling in all sorts of Maven dependencies, which
> clearly aren't needed in the distribution (You don't ship Maven plugins in
> a distribution ... that just doesn't make sense)
>
> I also validated we weren't including stripped-down versions in the maven
> distribution (Like in the case of Antlr)
>
> I did however notice, the Ant version includes commons-lang3 ... we don't
> have any code (except 2 classes in the compiler tests) that need this
> library. I didn't force usage of it in the Maven distribution (It could
> probably also be removed from the Ant distribution ... but no real harm
> done)
>
> Right now, I can't think of anything else needing to be done. So I guess
> it's up to you folks to test, test, test and start using it.
>
> Chris
>
>
> -Ursprüngliche Nachricht-
> Von: Christofer Dutz 
> Gesendet: Mittwoch, 17. März 2021 09:46
> An: dev@royale.apache.org
> Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hi all,
>
> So, I guess the last optimization I know I could do, would be to exclude
> unneeded jars.
> I know the number of jars in the ANT build's "external" directory is a lot
> less than the Maven version.
> I guess Maven just adds all transitive dependencies, no matter if the used
> code-paths actually use them.
> This would even reduce the size of the SDK.
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Maria Jose Esteve 
> Gesendet: Dienstag, 16. März 2021 18:23
> An: dev@royale.apache.org
> Betreff: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Well, I already have it clear ...
> The errors that I am receiving do not have to do with the distribution but
> with the modifications that I have had to make due to the 
> error, the inclusion of  true  and the elimination of the
> folder ". m2 / com / ... myproject / .. "on the PC where I am testing the
> distribution generate dependency errors because before the arqs were
> generated. Swf.swc and js.swc and not now.
> What a mess right? LOL
>
> As the errors have to do with the issue "" I will detail it
> there so as not to create more confusion.
>
> @Chris, I think I need to do a test: modify the sdk and see if the changes
> take me, I remember that I also had problems with this ...
> I tell you things.
>
> Hiedra.
>
> -Mensaje original-
> De: Maria Jose Esteve
> Enviado el: martes, 16 de marzo de 2021 17:11
> Para: dev@royale.apache.org
> Asunto: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hahahaha, I haven't detailed anything because I haven't seen them in depth
> yet and I don't want to waste your time.
> Although I know that the errors have to do with the distribution, since
> they do not occur with the normal compilation, I am not sure if they
> originate from this. Soon I will tell you more things.
>
> Hiedra.
>
> -Mensaje original-
> De: Christofer Dutz  Enviado el: martes, 16 de
> marzo de 2021 17:03
> Para: dev@royale.apache.org
> Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hi Hiedra,
>
> could you please explain what's not working for that project? I can't
> quite see in your email that it's not working.
>
> Chris
>
>
> -Ursprüngliche Nachricht-
> Von: Maria Jose Esteve 
> Gesendet: Dienstag, 16. März 2021 16:58
> An: dev@royale.apache.org
> Betreff: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> I'm glad too  hahahaha. Thank you for your work.
>
>
>
> "I still do not give you 100%  because the large project does not
> compile with the distribution" and yes with the compilation without
> distribution ...
>
> Surely there is something that I have to put differently ...
>
> I'll keep you informed.
>
>
>
> Hiedra
>
>
>
> -Mensaje original-
> De: Christofer Dutz  Enviado el: martes, 16 de
> marzo de 2021 16:36
> Para: dev@royale.apache.org
> Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Mave

RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Maria Jose Esteve]

Chris, I just compiled your last change and everything is ok.

Hiedra

-Mensaje original-
De: Christofer Dutz  
Enviado el: miércoles, 17 de marzo de 2021 10:14
Para: dev@royale.apache.org
Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Hi all,

Ok .. so, I stripped down the Maven distribution to only contain the jars the 
Ant version uses. Before that I could see most dependencies related to the 
royale-maven-plugin pulling in all sorts of Maven dependencies, which clearly 
aren't needed in the distribution (You don't ship Maven plugins in a 
distribution ... that just doesn't make sense)

I also validated we weren't including stripped-down versions in the maven 
distribution (Like in the case of Antlr)

I did however notice, the Ant version includes commons-lang3 ... we don't have 
any code (except 2 classes in the compiler tests) that need this library. I 
didn't force usage of it in the Maven distribution (It could probably also be 
removed from the Ant distribution ... but no real harm done)

Right now, I can't think of anything else needing to be done. So I guess it's 
up to you folks to test, test, test and start using it.

Chris


-Ursprüngliche Nachricht-
Von: Christofer Dutz  
Gesendet: Mittwoch, 17. März 2021 09:46
An: dev@royale.apache.org
Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Hi all,

So, I guess the last optimization I know I could do, would be to exclude 
unneeded jars.
I know the number of jars in the ANT build's "external" directory is a lot less 
than the Maven version.
I guess Maven just adds all transitive dependencies, no matter if the used 
code-paths actually use them.
This would even reduce the size of the SDK.

Chris

-Ursprüngliche Nachricht-
Von: Maria Jose Esteve  
Gesendet: Dienstag, 16. März 2021 18:23
An: dev@royale.apache.org
Betreff: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Well, I already have it clear ...
The errors that I am receiving do not have to do with the distribution but with 
the modifications that I have had to make due to the  error, the 
inclusion of  true  and the elimination of the folder ". m2 / 
com / ... myproject / .. "on the PC where I am testing the distribution 
generate dependency errors because before the arqs were generated. Swf.swc and 
js.swc and not now.
What a mess right? LOL

As the errors have to do with the issue "" I will detail it there so 
as not to create more confusion.

@Chris, I think I need to do a test: modify the sdk and see if the changes take 
me, I remember that I also had problems with this ...
I tell you things.

Hiedra.

-Mensaje original-
De: Maria Jose Esteve 
Enviado el: martes, 16 de marzo de 2021 17:11
Para: dev@royale.apache.org
Asunto: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Hahahaha, I haven't detailed anything because I haven't seen them in depth yet 
and I don't want to waste your time.
Although I know that the errors have to do with the distribution, since they do 
not occur with the normal compilation, I am not sure if they originate from 
this. Soon I will tell you more things.

Hiedra.

-Mensaje original-
De: Christofer Dutz  Enviado el: martes, 16 de marzo 
de 2021 17:03
Para: dev@royale.apache.org
Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Hi Hiedra,

could you please explain what's not working for that project? I can't quite see 
in your email that it's not working.

Chris


-Ursprüngliche Nachricht-
Von: Maria Jose Esteve 
Gesendet: Dienstag, 16. März 2021 16:58
An: dev@royale.apache.org
Betreff: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

I'm glad too  hahahaha. Thank you for your work.



"I still do not give you 100%  because the large project does not compile with 
the distribution" and yes with the compilation without distribution ...

Surely there is something that I have to put differently ...

I'll keep you informed.



Hiedra



-Mensaje original-
De: Christofer Dutz  Enviado el: martes, 16 de marzo 
de 2021 16:36
Para: dev@royale.apache.org
Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned



Hi Hiedra,



happy that it worked for you ... in general people were complaining that the 
Maven distribution wasn't "working" for them.

This was in various situations and IDEs ... so what I did, was to try to change 
the maven distribution to me more like the one produced by Ant, generally 
allowing us to use the Maven-built distribution for download.



Chris



-Ursprüngliche Nachricht-

Von: Maria Jose Esteve mailto:mjest...@iest.com>>

Gesendet: Dienstag, 16. März 2021 16:08

An: dev@royale.apache.org<mailto:dev@royale.apache.org>

Betreff: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned



Hi, I have had a difficult few weeks with work, I feel the silence.







First I wanted to remember that my environment and routin

RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Maria Jose Esteve]

Well, I already have it clear ...
The errors that I am receiving do not have to do with the distribution but with 
the modifications that I have had to make due to the  error, the 
inclusion of  true  and the elimination of the folder ". m2 / 
com / ... myproject / .. "on the PC where I am testing the distribution 
generate dependency errors because before the arqs were generated. Swf.swc and 
js.swc and not now.
What a mess right? LOL

As the errors have to do with the issue "" I will detail it there so 
as not to create more confusion.

@Chris, I think I need to do a test: modify the sdk and see if the changes take 
me, I remember that I also had problems with this ...
I tell you things.

Hiedra.

-Mensaje original-
De: Maria Jose Esteve 
Enviado el: martes, 16 de marzo de 2021 17:11
Para: dev@royale.apache.org
Asunto: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Hahahaha, I haven't detailed anything because I haven't seen them in depth yet 
and I don't want to waste your time.
Although I know that the errors have to do with the distribution, since they do 
not occur with the normal compilation, I am not sure if they originate from 
this. Soon I will tell you more things.

Hiedra.

-Mensaje original-
De: Christofer Dutz  Enviado el: martes, 16 de marzo 
de 2021 17:03
Para: dev@royale.apache.org
Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Hi Hiedra,

could you please explain what's not working for that project? I can't quite see 
in your email that it's not working.

Chris


-Ursprüngliche Nachricht-
Von: Maria Jose Esteve 
Gesendet: Dienstag, 16. März 2021 16:58
An: dev@royale.apache.org
Betreff: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

I'm glad too  hahahaha. Thank you for your work.



"I still do not give you 100%  because the large project does not compile with 
the distribution" and yes with the compilation without distribution ...

Surely there is something that I have to put differently ...

I'll keep you informed.



Hiedra



-Mensaje original-
De: Christofer Dutz  Enviado el: martes, 16 de marzo 
de 2021 16:36
Para: dev@royale.apache.org
Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned



Hi Hiedra,



happy that it worked for you ... in general people were complaining that the 
Maven distribution wasn't "working" for them.

This was in various situations and IDEs ... so what I did, was to try to change 
the maven distribution to me more like the one produced by Ant, generally 
allowing us to use the Maven-built distribution for download.



Chris



-Ursprüngliche Nachricht-

Von: Maria Jose Esteve mailto:mjest...@iest.com>>

Gesendet: Dienstag, 16. März 2021 16:08

An: dev@royale.apache.org<mailto:dev@royale.apache.org>

Betreff: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned



Hi, I have had a difficult few weeks with work, I feel the silence.







First I wanted to remember that my environment and routines I think are a 
little different from Piotr's, maybe someone is in the same situation:



- IDE: vsCode



- Maven royale-compiler, royale-typedefs and royale-asjs compilation, js only.



- I compile the projects with maven: mvn clean install 
-Droyalelib=${env:ROYALE_HOME}\\frameworks



Env:ROYALE_HOME --> sdk distribution folder



In the pom.xml / 
-compiler.exclude-defaults-css-files=MXRoyale-0.9.8-SNAPSHOT-js.swc:defaults.css;



- Test projects: Jewel application.



Project Ex. 1: Royale-Echarts [1] - targets: JSRoyale



Project Ex. 2: AppWithLib [2] && Simplelib [3] - targets: 
JSRoyale



Project Ex. 3: Custom app.



   - Jewel application



   - crux and mx.rpc.remoting.RemoteObject



   - project consisting of an app project (views) 
and an external library - JSRoyale (classes, controllers, models and delegates)







Project Ex. 4: Custom app.



   - Jewel application



   - crux and mx.rpc.remoting.RemoteObject



- This project is not my belief, the framework 
was created by some external collaborators.



   It is made up of a royale-app and a royale-libs 
composed of several interconnected libraries and of these with the royale-app.



   In royale-app as expected, the views, and in 
royale-libs all the rest of the code (general classes, custom components, 
echarts [1], controllers, models and delegates)



   The application is compiled with the JSRoyale 
target and the libraries are compiled in js and swf (I can't understand this 
because the target is also JSRoyale)







[1] https://github.com/mjesteve/Royale-ECharts/

RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Maria Jose Esteve]

Hahahaha, I haven't detailed anything because I haven't seen them in depth yet 
and I don't want to waste your time.
Although I know that the errors have to do with the distribution, since they do 
not occur with the normal compilation, I am not sure if they originate from 
this. Soon I will tell you more things.

Hiedra.

-Mensaje original-
De: Christofer Dutz  
Enviado el: martes, 16 de marzo de 2021 17:03
Para: dev@royale.apache.org
Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Hi Hiedra,

could you please explain what's not working for that project? I can't quite see 
in your email that it's not working.

Chris


-Ursprüngliche Nachricht-
Von: Maria Jose Esteve  
Gesendet: Dienstag, 16. März 2021 16:58
An: dev@royale.apache.org
Betreff: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

I'm glad too  hahahaha. Thank you for your work.



"I still do not give you 100%  because the large project does not compile with 
the distribution" and yes with the compilation without distribution ...

Surely there is something that I have to put differently ...

I'll keep you informed.



Hiedra



-Mensaje original-
De: Christofer Dutz  Enviado el: martes, 16 de marzo 
de 2021 16:36
Para: dev@royale.apache.org
Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned



Hi Hiedra,



happy that it worked for you ... in general people were complaining that the 
Maven distribution wasn't "working" for them.

This was in various situations and IDEs ... so what I did, was to try to change 
the maven distribution to me more like the one produced by Ant, generally 
allowing us to use the Maven-built distribution for download.



Chris



-Ursprüngliche Nachricht-

Von: Maria Jose Esteve mailto:mjest...@iest.com>>

Gesendet: Dienstag, 16. März 2021 16:08

An: dev@royale.apache.org<mailto:dev@royale.apache.org>

Betreff: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned



Hi, I have had a difficult few weeks with work, I feel the silence.







First I wanted to remember that my environment and routines I think are a 
little different from Piotr's, maybe someone is in the same situation:



- IDE: vsCode



- Maven royale-compiler, royale-typedefs and royale-asjs compilation, js only.



- I compile the projects with maven: mvn clean install 
-Droyalelib=${env:ROYALE_HOME}\\frameworks



Env:ROYALE_HOME --> sdk distribution folder



In the pom.xml / 
-compiler.exclude-defaults-css-files=MXRoyale-0.9.8-SNAPSHOT-js.swc:defaults.css;



- Test projects: Jewel application.



Project Ex. 1: Royale-Echarts [1] - targets: JSRoyale



Project Ex. 2: AppWithLib [2] && Simplelib [3] - targets: 
JSRoyale



Project Ex. 3: Custom app.



   - Jewel application



   - crux and mx.rpc.remoting.RemoteObject



   - project consisting of an app project (views) 
and an external library - JSRoyale (classes, controllers, models and delegates)







Project Ex. 4: Custom app.



   - Jewel application



   - crux and mx.rpc.remoting.RemoteObject



- This project is not my belief, the framework 
was created by some external collaborators.



   It is made up of a royale-app and a royale-libs 
composed of several interconnected libraries and of these with the royale-app.



   In royale-app as expected, the views, and in 
royale-libs all the rest of the code (general classes, custom components, 
echarts [1], controllers, models and delegates)



   The application is compiled with the JSRoyale 
target and the libraries are compiled in js and swf (I can't understand this 
because the target is also JSRoyale)







[1] https://github.com/mjesteve/Royale-ECharts/tree/develop_v5



[2] 
https://github.com/mjesteve/royale-asjs/tree/Example_AppWithLib/examples/crux/AppWithLib



[3] 
https://github.com/mjesteve/royale-asjs/tree/Example_AppWithLib/examples/crux/SampleLib







@Chris, I have generated the distribution to the second , had always used "-P 
with-distribution" (with white space between the "-P" and the "w") but now it 
does not recognize me. Yes I was recognized by "-Pwith-distribution" --> Ok all







Although I do not use the mvn swf-js distribution, I have also compiled it and 
generated it correctly.



I don't know what should be generated with the distribution to be considered 
"aligned with the ant distribution" but in the "themes" folder, of the swf-js 
distribution, the "Halo" folder is missing and I don't know if anything else is 
there? should it be generated?

RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Maria Jose Esteve]

I'm glad too  hahahaha. Thank you for your work.



"I still do not give you 100%  because the large project does not compile with 
the distribution" and yes with the compilation without distribution ...

Surely there is something that I have to put differently ...

I'll keep you informed.



Hiedra



-Mensaje original-
De: Christofer Dutz 
Enviado el: martes, 16 de marzo de 2021 16:36
Para: dev@royale.apache.org
Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned



Hi Hiedra,



happy that it worked for you ... in general people were complaining that the 
Maven distribution wasn't "working" for them.

This was in various situations and IDEs ... so what I did, was to try to change 
the maven distribution to me more like the one produced by Ant, generally 
allowing us to use the Maven-built distribution for download.



Chris



-Ursprüngliche Nachricht-

Von: Maria Jose Esteve mailto:mjest...@iest.com>>

Gesendet: Dienstag, 16. März 2021 16:08

An: dev@royale.apache.org<mailto:dev@royale.apache.org>

Betreff: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned



Hi, I have had a difficult few weeks with work, I feel the silence.







First I wanted to remember that my environment and routines I think are a 
little different from Piotr's, maybe someone is in the same situation:



- IDE: vsCode



- Maven royale-compiler, royale-typedefs and royale-asjs compilation, js only.



- I compile the projects with maven: mvn clean install 
-Droyalelib=${env:ROYALE_HOME}\\frameworks



Env:ROYALE_HOME --> sdk distribution folder



In the pom.xml / 
-compiler.exclude-defaults-css-files=MXRoyale-0.9.8-SNAPSHOT-js.swc:defaults.css;



- Test projects: Jewel application.



Project Ex. 1: Royale-Echarts [1] - targets: JSRoyale



Project Ex. 2: AppWithLib [2] && Simplelib [3] - targets: 
JSRoyale



Project Ex. 3: Custom app.



   - Jewel application



   - crux and mx.rpc.remoting.RemoteObject



   - project consisting of an app project (views) 
and an external library - JSRoyale (classes, controllers, models and delegates)







Project Ex. 4: Custom app.



   - Jewel application



   - crux and mx.rpc.remoting.RemoteObject



- This project is not my belief, the framework 
was created by some external collaborators.



   It is made up of a royale-app and a royale-libs 
composed of several interconnected libraries and of these with the royale-app.



   In royale-app as expected, the views, and in 
royale-libs all the rest of the code (general classes, custom components, 
echarts [1], controllers, models and delegates)



   The application is compiled with the JSRoyale 
target and the libraries are compiled in js and swf (I can't understand this 
because the target is also JSRoyale)







[1] https://github.com/mjesteve/Royale-ECharts/tree/develop_v5



[2] 
https://github.com/mjesteve/royale-asjs/tree/Example_AppWithLib/examples/crux/AppWithLib



[3] 
https://github.com/mjesteve/royale-asjs/tree/Example_AppWithLib/examples/crux/SampleLib







@Chris, I have generated the distribution to the second , had always used "-P 
with-distribution" (with white space between the "-P" and the "w") but now it 
does not recognize me. Yes I was recognized by "-Pwith-distribution" --> Ok all







Although I do not use the mvn swf-js distribution, I have also compiled it and 
generated it correctly.



I don't know what should be generated with the distribution to be considered 
"aligned with the ant distribution" but in the "themes" folder, of the swf-js 
distribution, the "Halo" folder is missing and I don't know if anything else is 
there? should it be generated?







The IDE perfectly recognizes both distributions.



Successful mvn compilation of "Project Ex. 1", "Project Ex. 2" and "Project Ex. 
3" but with "Project Ex. 4" I get errors that I am debugging right now and that 
I will share with you in a bit.



I have to say that all "Projects Ex." compile without errors if I use the 
compiled SDK "no distribution"







Hiedra







-Mensaje original-

De: Piotr Zarzycki 
mailto:piotrzarzyck...@gmail.com>> Enviado el: 
lunes, 15 de marzo de 2021 13:39

Para: Apache Royale Development 
mailto:dev@royale.apache.org>>

Asunto: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned







Hi Chris,







I have tested your changes and finally I'm able build project using



generated distribution. I would like to test it f

RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Maria Jose Esteve]

Sorry, I forgot to say that I can debug the sdk code without any problems. For 
example, I put a breakpoint in Alert.as and the debugging flow stops on it.

Hiedra

De: Maria Jose Esteve
Enviado el: martes, 16 de marzo de 2021 16:08
Para: dev@royale.apache.org
Asunto: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned


Hi, I have had a difficult few weeks with work, I feel the silence.



First I wanted to remember that my environment and routines I think are a 
little different from Piotr's, maybe someone is in the same situation:

- IDE: vsCode

- Maven royale-compiler, royale-typedefs and royale-asjs compilation, js only.

- I compile the projects with maven: mvn clean install 
-Droyalelib=${env:ROYALE_HOME}\\frameworks

Env:ROYALE_HOME --> sdk distribution folder

In the pom.xml / 
-compiler.exclude-defaults-css-files=MXRoyale-0.9.8-SNAPSHOT-js.swc:defaults.css;

- Test projects: Jewel application.

Project Ex. 1: Royale-Echarts [1] - targets: JSRoyale

Project Ex. 2: AppWithLib [2] && Simplelib [3] - targets: 
JSRoyale

Project Ex. 3: Custom app.

   - Jewel application

   - crux and mx.rpc.remoting.RemoteObject

   - project consisting of an app project (views) 
and an external library - JSRoyale (classes, controllers, models and delegates)



Project Ex. 4: Custom app.

   - Jewel application

   - crux and mx.rpc.remoting.RemoteObject

- This project is not my belief, the framework 
was created by some external collaborators.

   It is made up of a royale-app and a royale-libs 
composed of several interconnected libraries and of these with the royale-app.

   In royale-app as expected, the views, and in 
royale-libs all the rest of the code (general classes, custom components, 
echarts [1], controllers, models and delegates)

   The application is compiled with the JSRoyale 
target and the libraries are compiled in js and swf (I can't understand this 
because the target is also JSRoyale)



[1] https://github.com/mjesteve/Royale-ECharts/tree/develop_v5

[2] 
https://github.com/mjesteve/royale-asjs/tree/Example_AppWithLib/examples/crux/AppWithLib

[3] 
https://github.com/mjesteve/royale-asjs/tree/Example_AppWithLib/examples/crux/SampleLib



@Chris, I have generated the distribution to the second , had always used "-P 
with-distribution" (with white space between the "-P" and the "w") but now it 
does not recognize me. Yes I was recognized by "-Pwith-distribution" --> Ok all



Although I do not use the mvn swf-js distribution, I have also compiled it and 
generated it correctly.

I don't know what should be generated with the distribution to be considered 
"aligned with the ant distribution" but in the "themes" folder, of the swf-js 
distribution, the "Halo" folder is missing and I don't know if anything else is 
there? should it be generated?



The IDE perfectly recognizes both distributions.

Successful mvn compilation of "Project Ex. 1", "Project Ex. 2" and "Project Ex. 
3" but with "Project Ex. 4" I get errors that I am debugging right now and that 
I will share with you in a bit.

I have to say that all "Projects Ex." compile without errors if I use the 
compiled SDK "no distribution"



Hiedra



-Mensaje original-
De: Piotr Zarzycki mailto:piotrzarzyck...@gmail.com>>
Enviado el: lunes, 15 de marzo de 2021 13:39
Para: Apache Royale Development 
mailto:dev@royale.apache.org>>
Asunto: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned



Hi Chris,



I have tested your changes and finally I'm able build project using

generated distribution. I would like to test it for couple of days to see

if I won't have any problems with Josh's language server and we should be

good here.



Thanks,

Piotr



sob., 13 mar 2021 o 15:10 Christofer Dutz 
mailto:christofer.d...@c-ware.de>>

napisał(a):



> Hi Piotr,

>

> ok ... that was easily fixable.

> In one of my last commits I had removed the class path entry to

> antlr-runtime.jar as the Ant one didn't have this.

> But the missing class you reported is in this jar.

>

> So, I compared the antlr.jar in the Ant and Maven distribution. They were

> greatly different in size (Ant:2,4MB vs Maven 0.4MB)

> I therefore re-added the antlr-rutime.jar back to the class path of the

> Maven distribution.

>

> This error should now disappear.

>

> Chris

>…

RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Maria Jose Esteve]

Hi, I have had a difficult few weeks with work, I feel the silence.



First I wanted to remember that my environment and routines I think are a 
little different from Piotr's, maybe someone is in the same situation:

- IDE: vsCode

- Maven royale-compiler, royale-typedefs and royale-asjs compilation, js only.

- I compile the projects with maven: mvn clean install 
-Droyalelib=${env:ROYALE_HOME}\\frameworks

Env:ROYALE_HOME --> sdk distribution folder

In the pom.xml / 
-compiler.exclude-defaults-css-files=MXRoyale-0.9.8-SNAPSHOT-js.swc:defaults.css;

- Test projects: Jewel application.

Project Ex. 1: Royale-Echarts [1] - targets: JSRoyale

Project Ex. 2: AppWithLib [2] && Simplelib [3] - targets: 
JSRoyale

Project Ex. 3: Custom app.

   - Jewel application

   - crux and mx.rpc.remoting.RemoteObject

   - project consisting of an app project (views) 
and an external library - JSRoyale (classes, controllers, models and delegates)



Project Ex. 4: Custom app.

   - Jewel application

   - crux and mx.rpc.remoting.RemoteObject

- This project is not my belief, the framework 
was created by some external collaborators.

   It is made up of a royale-app and a royale-libs 
composed of several interconnected libraries and of these with the royale-app.

   In royale-app as expected, the views, and in 
royale-libs all the rest of the code (general classes, custom components, 
echarts [1], controllers, models and delegates)

   The application is compiled with the JSRoyale 
target and the libraries are compiled in js and swf (I can't understand this 
because the target is also JSRoyale)



[1] https://github.com/mjesteve/Royale-ECharts/tree/develop_v5

[2] 
https://github.com/mjesteve/royale-asjs/tree/Example_AppWithLib/examples/crux/AppWithLib

[3] 
https://github.com/mjesteve/royale-asjs/tree/Example_AppWithLib/examples/crux/SampleLib



@Chris, I have generated the distribution to the second , had always used "-P 
with-distribution" (with white space between the "-P" and the "w") but now it 
does not recognize me. Yes I was recognized by "-Pwith-distribution" --> Ok all



Although I do not use the mvn swf-js distribution, I have also compiled it and 
generated it correctly.

I don't know what should be generated with the distribution to be considered 
"aligned with the ant distribution" but in the "themes" folder, of the swf-js 
distribution, the "Halo" folder is missing and I don't know if anything else is 
there? should it be generated?



The IDE perfectly recognizes both distributions.

Successful mvn compilation of "Project Ex. 1", "Project Ex. 2" and "Project Ex. 
3" but with "Project Ex. 4" I get errors that I am debugging right now and that 
I will share with you in a bit.

I have to say that all "Projects Ex." compile without errors if I use the 
compiled SDK "no distribution"



Hiedra



-Mensaje original-
De: Piotr Zarzycki 
Enviado el: lunes, 15 de marzo de 2021 13:39
Para: Apache Royale Development 
Asunto: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned



Hi Chris,



I have tested your changes and finally I'm able build project using

generated distribution. I would like to test it for couple of days to see

if I won't have any problems with Josh's language server and we should be

good here.



Thanks,

Piotr



sob., 13 mar 2021 o 15:10 Christofer Dutz 
mailto:christofer.d...@c-ware.de>>

napisał(a):



> Hi Piotr,

>

> ok ... that was easily fixable.

> In one of my last commits I had removed the class path entry to

> antlr-runtime.jar as the Ant one didn't have this.

> But the missing class you reported is in this jar.

>

> So, I compared the antlr.jar in the Ant and Maven distribution. They were

> greatly different in size (Ant:2,4MB vs Maven 0.4MB)

> I therefore re-added the antlr-rutime.jar back to the class path of the

> Maven distribution.

>

> This error should now disappear.

>

> Chris

>…

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

Hi Chris,

I have tested your changes and finally I'm able build project using
generated distribution. I would like to test it for couple of days to see
if I won't have any problems with Josh's language server and we should be
good here.

Thanks,
Piotr

sob., 13 mar 2021 o 15:10 Christofer Dutz 
napisał(a):

> Hi Piotr,
>
> ok ... that was easily fixable.
> In one of my last commits I had removed the class path entry to
> antlr-runtime.jar as the Ant one didn't have this.
> But the missing class you reported is in this jar.
>
> So, I compared the antlr.jar in the Ant and Maven distribution. They were
> greatly different in size (Ant:2,4MB vs Maven 0.4MB)
> I therefore re-added the antlr-rutime.jar back to the class path of the
> Maven distribution.
>
> This error should now disappear.
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Piotr Zarzycki 
> Gesendet: Freitag, 12. März 2021 15:51
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hi Chris,
>
> I just pulled your changes and rebuild everything. This time I'm getting
> different error:
>
> : Using Royale SDK: "D:\Work\royale_ide\distribution"
> : Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms356m -Xmx3000m
> : MXMLJSC
> :
>
> -sdk-js-lib=D:\Work\royale_ide\distribution\frameworks\js\Royale\generated-sources
> : -load-config+=obj/ProminicNativeWebConfig.xml
> : -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> : -html-template=src/resources/jewel-index-template.html
> : -js-dynamic-access-unknown-members=true
> : -debug=true
> : -compiler.targets=JSRoyale
> : -js-output=C:\xampp\htdocs\prominic
> : java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError:
> org/antlr/runtime/CharStream
> : at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
> : at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
> : at
>
> org.apache.royale.compiler.internal.units.requests.RequestMaker$Request.get(RequestMaker.java:80)
> : at
>
> org.apache.royale.compiler.internal.units.MXMLCompilationUnit.handleABCBytesRequest(MXMLCompilationUnit.java:195)
> : at
>
> org.apache.royale.compiler.internal.units.CompilationUnitBase.processABCBytesRequest(CompilationUnitBase.java:876)
> : at
>
> org.apache.royale.compiler.internal.units.CompilationUnitBase.access$300(CompilationUnitBase.java:109)
> : at
>
> org.apache.royale.compiler.internal.units.CompilationUnitBase$4$1.call(CompilationUnitBase.java:313)
> : at
>
> org.apache.royale.compiler.internal.units.CompilationUnitBase$4$1.call(CompilationUnitBase.java:309)
> : at
>
> org.apache.royale.compiler.internal.units.requests.RequestMaker$1.call(RequestMaker.java:228)
> : at
>
> org.apache.royale.compiler.internal.units.requests.RequestMaker$1.call(RequestMaker.java:222)
> : at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> : at
>
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> : at
>
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> : at java.base/java.lang.Thread.run(Thread.java:834)
> : Caused by: java.lang.NoClassDefFoundError: org/antlr/runtime/CharStream
> : at
>
> org.apache.royale.compiler.internal.tree.mxml.MXMLClassDefinitionNode.processChildTag(MXMLClassDefinitionNode.java:279)
> : at
>
> org.apache.royale.compiler.internal.tree.mxml.MXMLDocumentNode.processChildTag(MXMLDocumentNode.java:101)
> : at
>
> org.apache.royale.compiler.internal.tree.mxml.MXMLNodeBase.processContentUnit(MXMLNodeBase.java:522)
> : at
>
> org.apache.royale.compiler.internal.tree.mxml.MXMLNodeBase.initializeFromTag(MXMLNodeBase.java:280)
> : at
>
> org.apache.royale.compiler.internal.tree.mxml.MXMLFileNode.processRootTag(MXMLFileNode.java:272)
> : at
>
> org.apache.royale.compiler.internal.tree.mxml.MXMLFileNode.processUnits(MXMLFileNode.java:191)
> : at
>
> org.apache.royale.compiler.internal.tree.mxml.MXMLFileNode.initialize(MXMLFileNode.java:156)
> : at
>
> org.apache.royale.compiler.internal.tree.mxml.MXMLTreeBuilder.build(MXMLTreeBuilder.java:319)
> : at
>
> org.apache.royale.compiler.internal.units.MXMLCompilationUnit.handleSyntaxTreeRequest(MXMLCompilationUnit.java:104)
> : at
>
> org.apache.royale.compiler.internal.units.CompilationUnitBase.processSyntaxTreeRequest(CompilationUnitBase.java:839)
> : at
>
> org.apache.royale.compiler.internal.units.CompilationUnitBase.access$100(CompilationUnitBase.java:109)
> : at
>
> org.apache.royale.compiler.internal.units.CompilationUnitBase$2$1.call(CompilationUnitBase.java:263)
> : a

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

generate the manifest
> classpath automatically, but I defined it manually and verified the jars
> exist and have the right name.
> - There was a HUGE difference on where some of the jars in js/libs were
> located, so I've updated the distribution to match that of Ant.
> - I noticed that it seems there is no Maven build for asdoc.jar ... all I
> can see is an Ant build file.
> - The content of the js/lib/google directory greatly differs ... will
> investigate this as soon as I can find some time.
>
> So, I just pushed some updates, but I guess I'll have to continue my work
> on this as soon as I find some time ... would be awesome if anyone could
> actively help on this.
>
> Right now, I'm just creating diffs between the two and trying to get the
> Maven distribution to match this.
>
>  Chris
>
>
> -Ursprüngliche Nachricht-
> Von: Christofer Dutz 
> Gesendet: Freitag, 12. März 2021 09:18
> An: dev@royale.apache.org
> Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Oh gee ... I was hoping not having to do this ... but I'll now compare the
> libs also inside.
>
> Will keep you posted ...
>
>
> Chris
>
>
>
> -Ursprüngliche Nachricht-
> Von: Piotr Zarzycki 
> Gesendet: Freitag, 12. März 2021 00:06
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hey Chris,
>
> Unfortunately I cannot share with you code of that project, unless by
> library you mean distribution which I have generated using your branches.
>
> I will have to double check, but I'm sure that I have rebuild everything
> using your branches.
>
> Thanks,
> Piotr
>
> czw., 11 mar 2021 o 21:47 Christofer Dutz 
> napisał(a):
>
> > Hi Poitr,
> >
> > You re-built the compiler and then the framework (both in my branch and
> > including distribution)?
> >
> > Would you be able to share the library so I could try on my side?
> >
> > Chris
> >
> > -Ursprüngliche Nachricht-
> > Von: Piotr Zarzycki 
> > Gesendet: Donnerstag, 11. März 2021 15:43
> > An: Apache Royale Development 
> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > Hi Chris,
> >
> > I have tested it with your changes and I'm getting same issue:
> >
> > Exception in thread "main" java.lang.NoClassDefFoundError:
> > org/apache/commons/lang/StringEscapeUtils
> > : at
> >
> >
> org.apache.royale.compiler.internal.codegen.js.jx.LiteralEmitter.emit(LiteralEmitter.java:225)
> > : at
> >
> >
> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitLiteral(JSRoyaleEmitter.java:1040)
> > : at
> > org.apache.royale.compiler.internal.codegen.as
> > .ASBlockWalker.visitLiteral(ASBlockWalker.java:479)
> > : at
> > org.apache.royale.compiler.internal.visitor.as
> > .ASNodeSwitch.handle(ASNodeSwitch.java:373)
> > : at
> > org.apache.royale.compiler.internal.visitor.as
> > .ASNodeHandler.handle(ASNodeHandler.java:85)
> > : at
> > org.apache.royale.compiler.internal.visitor.as
> > .BeforeAfterStrategy.handle(BeforeAfterStrategy.java:110)
> > : at
> > org.apache.royale.compiler.internal.codegen.as
> > .ASBlockWalker.walk(ASBlockWalker.java:159)
> > : at
> >
> >
> org.apache.royale.compiler.internal.codegen.js.goog.JSGoogEmitter.emitAssignedValue(JSGoogEmitter.java:965)
> > : at
> >
> >
> org.apache.royale.compiler.internal.codegen.js.JSEmitter.emitAssignmentCoercion(JSEmitter.java:917)
> > : at
> >
> >
> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitAssignmentCoercion(JSRoyaleEmitter.java:1558)
> > : at
> >
> >
> org.apache.royale.compiler.internal.codegen.js.jx.FunctionCallArgumentsEmitter.emitContents(FunctionCallArgumentsEmitter.java:103)
> > : at
> >
> >
> org.apache.royale.compiler.internal.codegen.js.jx.FunctionCallArgumentsEmitter.emit(FunctionCallArgumentsEmitter.java:50)
> > :
> > : at
> >
> >
> org.apache.royale.compiler.internal.codegen.js.jx.FunctionCallArgumentsEmitter.emit(FunctionCallArgumentsEmitter.java:35)
> > : at
> >
> >
> org.apache.royale.compiler.internal.codegen.js.JSEmitter.emitArguments(JSEmitter.java:259)
> > : at
> >
> >
> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitArguments(JSRoyaleEmitter.java:986)
> > : at
> >
> >
> org.apache.royale.compiler.internal.codegen.js.jx.FunctionCallEmitter.emit(FunctionCallE

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

Hey Chris,

Unfortunately I cannot share with you code of that project, unless by
library you mean distribution which I have generated using your branches.

I will have to double check, but I'm sure that I have rebuild everything
using your branches.

Thanks,
Piotr

czw., 11 mar 2021 o 21:47 Christofer Dutz 
napisał(a):

> Hi Poitr,
>
> You re-built the compiler and then the framework (both in my branch and
> including distribution)?
>
> Would you be able to share the library so I could try on my side?
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Piotr Zarzycki 
> Gesendet: Donnerstag, 11. März 2021 15:43
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hi Chris,
>
> I have tested it with your changes and I'm getting same issue:
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/commons/lang/StringEscapeUtils
> : at
>
> org.apache.royale.compiler.internal.codegen.js.jx.LiteralEmitter.emit(LiteralEmitter.java:225)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitLiteral(JSRoyaleEmitter.java:1040)
> : at
> org.apache.royale.compiler.internal.codegen.as
> .ASBlockWalker.visitLiteral(ASBlockWalker.java:479)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .ASNodeSwitch.handle(ASNodeSwitch.java:373)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .ASNodeHandler.handle(ASNodeHandler.java:85)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .BeforeAfterStrategy.handle(BeforeAfterStrategy.java:110)
> : at
> org.apache.royale.compiler.internal.codegen.as
> .ASBlockWalker.walk(ASBlockWalker.java:159)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.goog.JSGoogEmitter.emitAssignedValue(JSGoogEmitter.java:965)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.JSEmitter.emitAssignmentCoercion(JSEmitter.java:917)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitAssignmentCoercion(JSRoyaleEmitter.java:1558)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.jx.FunctionCallArgumentsEmitter.emitContents(FunctionCallArgumentsEmitter.java:103)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.jx.FunctionCallArgumentsEmitter.emit(FunctionCallArgumentsEmitter.java:50)
> :
> : at
>
> org.apache.royale.compiler.internal.codegen.js.jx.FunctionCallArgumentsEmitter.emit(FunctionCallArgumentsEmitter.java:35)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.JSEmitter.emitArguments(JSEmitter.java:259)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitArguments(JSRoyaleEmitter.java:986)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.jx.FunctionCallEmitter.emit(FunctionCallEmitter.java:693)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitFunctionCall(JSRoyaleEmitter.java:906)
> : at
> org.apache.royale.compiler.internal.codegen.as
> .ASBlockWalker.visitFunctionCall(ASBlockWalker.java:330)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .ASNodeSwitch.handle(ASNodeSwitch.java:207)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .ASNodeHandler.handle(ASNodeHandler.java:85)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .BeforeAfterStrategy.handle(BeforeAfterStrategy.java:110)
> : at
> org.apache.royale.compiler.internal.codegen.as
> .ASBlockWalker.walk(ASBlockWalker.java:159)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.goog.JSGoogEmitter.emitAssignedValue(JSGoogEmitter.java:965)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.JSEmitter.emitAssignmentCoercion(JSEmitter.java:917)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitAssignmentCoercion(JSRoyaleEmitter.java:1558)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.jx.BinaryOperatorEmitter.super_emitBinaryOperator(BinaryOperatorEmitter.java:598)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.jx.BinaryOperatorEmitter.emit(BinaryOperatorEmitter.java:500)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitBinaryOperator(JSRoyaleEmitter.java:1028)
> : at
> org.apache.royale.compiler.internal.codegen.as
> .ASBlockWalker.visitBinaryOperator(ASBlockWalker.java:538)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .ASNodeSwitch.handle(ASNodeSwitch.java:348)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .ASNodeHandler.handle(ASNodeHandler.java:85)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .BeforeAfter

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

itter.java:891)
: at
org.apache.royale.compiler.internal.codegen.as.ASBlockWalker.visitFunction(ASBlockWalker.java:290)
: at
org.apache.royale.compiler.internal.visitor.as.ASNodeSwitch.handle(ASNodeSwitch.java:152)
: at
org.apache.royale.compiler.internal.visitor.as.ASNodeHandler.handle(ASNodeHandler.java:85)
: at
org.apache.royale.compiler.internal.visitor.as.BeforeAfterStrategy.handle(BeforeAfterStrategy.java:110)
: at
org.apache.royale.compiler.internal.codegen.as.ASBlockWalker.walk(ASBlockWalker.java:159)
: at
org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyaleEmitter.emitScripts(MXMLRoyaleEmitter.java:2179)
: at
org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyaleEmitter.emitDocument(MXMLRoyaleEmitter.java:899)
: at
org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyaleBlockWalker.visitDocument(MXMLRoyaleBlockWalker.java:69)
: at
org.apache.royale.compiler.internal.visitor.mxml.MXMLNodeSwitch.handle(MXMLNodeSwitch.java:89)
: at
org.apache.royale.compiler.internal.codegen.mxml.MXMLBlockWalker.walk(MXMLBlockWalker.java:156)
: at
org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyaleBlockWalker.visitFile(MXMLRoyaleBlockWalker.java:61)
: at
org.apache.royale.compiler.internal.visitor.mxml.MXMLNodeSwitch.handle(MXMLNodeSwitch.java:95)
: at
org.apache.royale.compiler.internal.codegen.mxml.MXMLBlockWalker.walk(MXMLBlockWalker.java:156)
: at
org.apache.royale.compiler.internal.codegen.mxml.MXMLBlockWalker.visitCompilationUnit(MXMLBlockWalker.java:187)
: at
org.apache.royale.compiler.internal.codegen.mxml.MXMLWriter.writeTo(MXMLWriter.java:69)
: at
org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:411)
: at
org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:259)
: at
org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:216)
: at
org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:363)
: at org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:298)
: at
org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:256)
: at org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:238)
: Caused by: java.lang.ClassNotFoundException:
org.apache.commons.lang.StringEscapeUtils
: at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
: at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
: at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
: ... 67 more

wt., 9 mar 2021 o 16:55 Piotr Zarzycki 
napisał(a):

> Thanks Chris. I will try to give it a try tomorrow.
>
> Piotr
>
> wt., 9 mar 2021 o 16:41 Christofer Dutz 
> napisał(a):
>
>> Hehe ...
>>
>> Murphy's definitely not a nice guy :-/
>>
>> Turns out all libraries in the Ant distribution have no version number
>> ... all except:
>>
>> - commons-compress-1.10.jar
>> - commons-lang-2.6.jar
>> - commons-lang3-3.4.jar
>>
>> The missing class is in commons-lang-2.6.jar
>>
>> I found the invalid classpath entry in compiler-jx which was looking for
>> commons-lang-2.6.jar while it should have been commons-lang.jar. So that
>> issue should be fixed now.
>>
>> You should update compiler and re-build that (mvn clean install) and then
>> re-build the ASJS distribution and give it another try?
>>
>> Chris
>>
>>
>>
>> -Ursprüngliche Nachricht-
>> Von: Piotr Zarzycki 
>> Gesendet: Dienstag, 9. März 2021 15:22
>> An: Apache Royale Development 
>> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>>
>> Hi Chris,
>>
>> So I had some time today and build whole SDK with your latest changes.
>> Distribution has been prepared without the problem. I didn't check yet
>> building only distribution, but I will. I moved to test produced
>> distribution with small example and Moonshine - It builds without the
>> problems.
>>
>> I have tried next build our big Royale project with distribution and I'm
>> keep getting following error. Note that I'm able to build this project
>> with
>> ANT distribution.
>>
>> : Exception in thread "main" java.lang.NoClassDefFoundError:
>> org/apache/commons/lang/StringEscapeUtils
>> : at
>>
>> org.apache.royale.compiler.internal.codegen.js.jx.LiteralEmitter.emit(LiteralEmitter.java:225)
>> : at
>>
>> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitLiteral(JSRoyaleEmitter.java:1040)
>> : at
>> org.apache.royale.compiler.internal.codegen.as
>> .ASBlockWalker.visitLiteral(ASBlockWalker.java:479)
>> : at
>> org.apache.royale.compiler.internal.visitor.a

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

Thanks Chris. I will try to give it a try tomorrow.

Piotr

wt., 9 mar 2021 o 16:41 Christofer Dutz 
napisał(a):

> Hehe ...
>
> Murphy's definitely not a nice guy :-/
>
> Turns out all libraries in the Ant distribution have no version number ...
> all except:
>
> - commons-compress-1.10.jar
> - commons-lang-2.6.jar
> - commons-lang3-3.4.jar
>
> The missing class is in commons-lang-2.6.jar
>
> I found the invalid classpath entry in compiler-jx which was looking for
> commons-lang-2.6.jar while it should have been commons-lang.jar. So that
> issue should be fixed now.
>
> You should update compiler and re-build that (mvn clean install) and then
> re-build the ASJS distribution and give it another try?
>
> Chris
>
>
>
> -Ursprüngliche Nachricht-
> Von: Piotr Zarzycki 
> Gesendet: Dienstag, 9. März 2021 15:22
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hi Chris,
>
> So I had some time today and build whole SDK with your latest changes.
> Distribution has been prepared without the problem. I didn't check yet
> building only distribution, but I will. I moved to test produced
> distribution with small example and Moonshine - It builds without the
> problems.
>
> I have tried next build our big Royale project with distribution and I'm
> keep getting following error. Note that I'm able to build this project with
> ANT distribution.
>
> : Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/commons/lang/StringEscapeUtils
> : at
>
> org.apache.royale.compiler.internal.codegen.js.jx.LiteralEmitter.emit(LiteralEmitter.java:225)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitLiteral(JSRoyaleEmitter.java:1040)
> : at
> org.apache.royale.compiler.internal.codegen.as
> .ASBlockWalker.visitLiteral(ASBlockWalker.java:479)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .ASNodeSwitch.handle(ASNodeSwitch.java:373)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .ASNodeHandler.handle(ASNodeHandler.java:85)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .BeforeAfterStrategy.handle(BeforeAfterStrategy.java:110)
> : at
> org.apache.royale.compiler.internal.codegen.as
> .ASBlockWalker.walk(ASBlockWalker.java:159)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.goog.JSGoogEmitter.emitAssignedValue(JSGoogEmitter.java:965)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.JSEmitter.emitAssignmentCoercion(JSEmitter.java:917)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitAssignmentCoercion(JSRoyaleEmitter.java:1558)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.jx.FunctionCallArgumentsEmitter.emitContents(FunctionCallArgumentsEmitter.java:103)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.jx.FunctionCallArgumentsEmitter.emit(FunctionCallArgumentsEmitter.java:50)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.jx.FunctionCallArgumentsEmitter.emit(FunctionCallArgumentsEmitter.java:35)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.JSEmitter.emitArguments(JSEmitter.java:259)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitArguments(JSRoyaleEmitter.java:986)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.jx.FunctionCallEmitter.emit(FunctionCallEmitter.java:693)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitFunctionCall(JSRoyaleEmitter.java:906)
> : at
> org.apache.royale.compiler.internal.codegen.as
> .ASBlockWalker.visitFunctionCall(ASBlockWalker.java:330)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .ASNodeSwitch.handle(ASNodeSwitch.java:207)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .ASNodeHandler.handle(ASNodeHandler.java:85)
> : at
> org.apache.royale.compiler.internal.visitor.as
> .BeforeAfterStrategy.handle(BeforeAfterStrategy.java:110)
> : at
> org.apache.royale.compiler.internal.codegen.as
> .ASBlockWalker.walk(ASBlockWalker.java:159)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.goog.JSGoogEmitter.emitAssignedValue(JSGoogEmitter.java:965)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.JSEmitter.emitAssignmentCoercion(JSEmitter.java:917)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitAssignmentCoercion(JSRoyaleEmitter.java:1558)
> : at
>
> org.apache.royale.compiler.internal.codegen.js.jx.BinaryOperatorEmitter.super_emitBinaryOperator(BinaryOperatorEmitter.java:598)
> : at
>
> org.apache.royale.compiler.internal.codegen.js

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

y.java:110)
: at
org.apache.royale.compiler.internal.codegen.as.ASBlockWalker.walk(ASBlockWalker.java:159)
: at
org.apache.royale.compiler.internal.codegen.as.ASEmitter.emitMethodScope(ASEmitter.java:830)
: at
org.apache.royale.compiler.internal.codegen.js.jx.MethodEmitter.emit(MethodEmitter.java:160)
: at
org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitMethod(JSRoyaleEmitter.java:891)
: at
org.apache.royale.compiler.internal.codegen.as.ASBlockWalker.visitFunction(ASBlockWalker.java:290)
: at
org.apache.royale.compiler.internal.visitor.as.ASNodeSwitch.handle(ASNodeSwitch.java:152)
: at
org.apache.royale.compiler.internal.visitor.as.ASNodeHandler.handle(ASNodeHandler.java:85)
: at
org.apache.royale.compiler.internal.visitor.as.BeforeAfterStrategy.handle(BeforeAfterStrategy.java:110)
: at
org.apache.royale.compiler.internal.codegen.as.ASBlockWalker.walk(ASBlockWalker.java:159)
: at
org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyaleEmitter.emitScripts(MXMLRoyaleEmitter.java:2179)
: at
org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyaleEmitter.emitDocument(MXMLRoyaleEmitter.java:899)
: at
org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyaleBlockWalker.visitDocument(MXMLRoyaleBlockWalker.java:69)
: at
org.apache.royale.compiler.internal.visitor.mxml.MXMLNodeSwitch.handle(MXMLNodeSwitch.java:89)
: at
org.apache.royale.compiler.internal.codegen.mxml.MXMLBlockWalker.walk(MXMLBlockWalker.java:156)
: at
org.apache.royale.compiler.internal.codegen.mxml.royale.MXMLRoyaleBlockWalker.visitFile(MXMLRoyaleBlockWalker.java:61)
: at
org.apache.royale.compiler.internal.visitor.mxml.MXMLNodeSwitch.handle(MXMLNodeSwitch.java:95)
: at
org.apache.royale.compiler.internal.codegen.mxml.MXMLBlockWalker.walk(MXMLBlockWalker.java:156)
: at
org.apache.royale.compiler.internal.codegen.mxml.MXMLBlockWalker.visitCompilationUnit(MXMLBlockWalker.java:187)
: at
org.apache.royale.compiler.internal.codegen.mxml.MXMLWriter.writeTo(MXMLWriter.java:69)
: at
org.apache.royale.compiler.clients.MXMLJSCRoyale.compile(MXMLJSCRoyale.java:411)
: at
org.apache.royale.compiler.clients.MXMLJSCRoyale._mainNoExit(MXMLJSCRoyale.java:259)
: at
org.apache.royale.compiler.clients.MXMLJSCRoyale.mainNoExit(MXMLJSCRoyale.java:216)
: at
org.apache.royale.compiler.clients.MXMLJSC._mainNoExit(MXMLJSC.java:363)
: at org.apache.royale.compiler.clients.MXMLJSC.mainNoExit(MXMLJSC.java:298)
: at
org.apache.royale.compiler.clients.MXMLJSC.staticMainNoExit(MXMLJSC.java:256)
: at org.apache.royale.compiler.clients.MXMLJSC.main(MXMLJSC.java:238)
: Caused by: java.lang.ClassNotFoundException:
org.apache.commons.lang.StringEscapeUtils
: at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
: at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
: at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
: ... 67 more

Thanks,
Piotr



czw., 4 mar 2021 o 18:46 Piotr Zarzycki 
napisał(a):

> Chris,
>
> I don't know yet. I will check tomorrow or on Monday.
>
> Thanks,
> Piotr
>
> czw., 4 mar 2021 o 18:36 Christofer Dutz 
> napisał(a):
>
>> Hi Piotr,
>>
>> Do things work with "mvn install"?
>>
>> (you could also use "package", just anything "package" or beyond that)
>>
>> Chris
>>
>>
>>
>> -Ursprüngliche Nachricht-
>> Von: Christofer Dutz 
>> Gesendet: Donnerstag, 4. März 2021 11:25
>> An: dev@royale.apache.org
>> Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>>
>> Aaahhh ... I think I know what's going on.
>>
>> I did say "mvn clean install" now multiple times, didn't I?
>> I would like to lay emphasis on the "install" (Not "compile")
>>
>> You are running mvn "compile" ... this is a phase of maven that comes
>> before the "packaging" phase.
>> All the assembly stuff comes in the "packaging" phase.
>>
>> So, everything we do after the compile phase will not be executed ->
>> Therefore nothing is created in your case.
>>
>>
>> Chris
>>
>>
>>
>> -Ursprüngliche Nachricht-
>> Von: Piotr Zarzycki 
>> Gesendet: Donnerstag, 4. März 2021 10:59
>> An: Apache Royale Development 
>> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>>
>> Hi Chris,
>>
>> It doesn't work for me when I do in distribution folder:
>> set distributionTargetFolder= d:\Work\royale_ide\distribution
>>
>> mvn clean compile
>>
>> I will send you off the list logs from my attempt.
>>
>> Thanks,
>> Piotr
>>
>>
>> śr., 3 mar 2021 o 19:26 Piotr Zarzycki 
>> napisał(a):
>>

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

Chris,

I don't know yet. I will check tomorrow or on Monday.

Thanks,
Piotr

czw., 4 mar 2021 o 18:36 Christofer Dutz 
napisał(a):

> Hi Piotr,
>
> Do things work with "mvn install"?
>
> (you could also use "package", just anything "package" or beyond that)
>
> Chris
>
>
>
> -Ursprüngliche Nachricht-
> Von: Christofer Dutz 
> Gesendet: Donnerstag, 4. März 2021 11:25
> An: dev@royale.apache.org
> Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Aaahhh ... I think I know what's going on.
>
> I did say "mvn clean install" now multiple times, didn't I?
> I would like to lay emphasis on the "install" (Not "compile")
>
> You are running mvn "compile" ... this is a phase of maven that comes
> before the "packaging" phase.
> All the assembly stuff comes in the "packaging" phase.
>
> So, everything we do after the compile phase will not be executed ->
> Therefore nothing is created in your case.
>
>
> Chris
>
>
>
> -Ursprüngliche Nachricht-
> Von: Piotr Zarzycki 
> Gesendet: Donnerstag, 4. März 2021 10:59
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hi Chris,
>
> It doesn't work for me when I do in distribution folder:
> set distributionTargetFolder= d:\Work\royale_ide\distribution
>
> mvn clean compile
>
> I will send you off the list logs from my attempt.
>
> Thanks,
> Piotr
>
>
> śr., 3 mar 2021 o 19:26 Piotr Zarzycki 
> napisał(a):
>
> > Chris,
> >
> > Building whole framework with with-distribution - works - I didn't
> > test yet created distribution for any project - I will do that soon.
> >
> > I didn't try yet set distributionTargetFolder=
> > d:\Work\royale_ide\distribution - I will try tomorrow.
> >
> > śr., 3 mar 2021 o 16:19 Piotr Zarzycki 
> > napisał(a):
> >
> >> Good that you have explained it maybe someone benefit from it.
> >>
> >> I'm not sure why this stopped work with -DdistributionTargetFolder
> >> and it's working when I'm building whole framework... That is very
> confusing.
> >>
> >> śr., 3 mar 2021 o 16:02 Christofer Dutz 
> >> napisał(a):
> >>
> >>> That should have been two lines:
> >>>
> >>> set distributionTargetFolder= d:\Work\royale_ide\distribution
> >>>
> >>> mvn clean compile
> >>>
> >>> Chris
> >>>
> >>>
> >>> -Ursprüngliche Nachricht-
> >>> Von: Christofer Dutz 
> >>> Gesendet: Mittwoch, 3. März 2021 15:59
> >>> An: dev@royale.apache.org
> >>> Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >>>
> >>> Hi Piotr,
> >>>
> >>> you remember that I said you have to set a SYSTEM-property?
> >>> Cause I thought you can't use maven properties to activate maven
> >>> profiles.
> >>>
> >>> The strange thing was that after you reported that it worked with
> >>> maven properties, I gave it a try and it worked (Which confused me a
> >>> bit) I thought perhaps things changed in newer Maven versions. Now
> >>> looking again for a solution to this problem I again found the info
> >>> that it has to be a
> >>> SYSTEM-property:
> >>>
> >>> http://maven.40175.n5.nabble.com/Activating-a-profile-in-settings-xm
> >>> l-based-on-a-property-set-in-pom-xml-td512562.html
> >>>
> >>> So please set the distributionTargetFolder property this way:
> >>>
> >>> set distributionTargetFolder= d:\Work\royale_ide\distribution mvn
> >>> clean compile
> >>>
> >>> And I only explained things in detail because from what you wrote I
> >>> had the impression that you didn't really understand what's going on
> >>> and I wanted to provide more background information.
> >>>
> >>> Chris
> >>>
> >>>
> >>> -Ursprüngliche Nachricht-
> >>> Von: Piotr Zarzycki 
> >>> Gesendet: Mittwoch, 3. März 2021 15:45
> >>> An: Apache Royale Development 
> >>> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >>>
> >>> *Comments inline.*
> >>>
> >>> śr., 3 mar 2021 o 15:42 Piotr Zarzycki 
> >>> napisał(a):
> >>>
> >>> > >  Maven ce

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

Hi Chris,

It doesn't work for me when I do in distribution folder:
set distributionTargetFolder= d:\Work\royale_ide\distribution

mvn clean compile

I will send you off the list logs from my attempt.

Thanks,
Piotr


śr., 3 mar 2021 o 19:26 Piotr Zarzycki 
napisał(a):

> Chris,
>
> Building whole framework with with-distribution - works - I didn't test
> yet created distribution for any project - I will do that soon.
>
> I didn't try yet set distributionTargetFolder=
> d:\Work\royale_ide\distribution - I will try tomorrow.
>
> śr., 3 mar 2021 o 16:19 Piotr Zarzycki 
> napisał(a):
>
>> Good that you have explained it maybe someone benefit from it.
>>
>> I'm not sure why this stopped work with -DdistributionTargetFolder and
>> it's working when I'm building whole framework... That is very confusing.
>>
>> śr., 3 mar 2021 o 16:02 Christofer Dutz 
>> napisał(a):
>>
>>> That should have been two lines:
>>>
>>> set distributionTargetFolder= d:\Work\royale_ide\distribution
>>>
>>> mvn clean compile
>>>
>>> Chris
>>>
>>>
>>> -Ursprüngliche Nachricht-
>>> Von: Christofer Dutz 
>>> Gesendet: Mittwoch, 3. März 2021 15:59
>>> An: dev@royale.apache.org
>>> Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>>>
>>> Hi Piotr,
>>>
>>> you remember that I said you have to set a SYSTEM-property?
>>> Cause I thought you can't use maven properties to activate maven
>>> profiles.
>>>
>>> The strange thing was that after you reported that it worked with maven
>>> properties, I gave it a try and it worked (Which confused me a bit) I
>>> thought perhaps things changed in newer Maven versions. Now looking again
>>> for a solution to this problem I again found the info that it has to be a
>>> SYSTEM-property:
>>>
>>> http://maven.40175.n5.nabble.com/Activating-a-profile-in-settings-xml-based-on-a-property-set-in-pom-xml-td512562.html
>>>
>>> So please set the distributionTargetFolder property this way:
>>>
>>> set distributionTargetFolder= d:\Work\royale_ide\distribution mvn clean
>>> compile
>>>
>>> And I only explained things in detail because from what you wrote I had
>>> the impression that you didn't really understand what's going on and I
>>> wanted to provide more background information.
>>>
>>> Chris
>>>
>>>
>>> -Ursprüngliche Nachricht-
>>> Von: Piotr Zarzycki 
>>> Gesendet: Mittwoch, 3. März 2021 15:45
>>> An: Apache Royale Development 
>>> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>>>
>>> *Comments inline.*
>>>
>>> śr., 3 mar 2021 o 15:42 Piotr Zarzycki 
>>> napisał(a):
>>>
>>> > >  Maven central only serves released stuff. We get SNAPSHOT stuff
>>> > > from
>>> > the Apache Maven repo.
>>> >
>>> > True saying Maven central I meant Apache Maven repo or whatever place
>>> > this is stored.
>>> >
>>> > śr., 3 mar 2021 o 15:41 Christofer Dutz 
>>> > napisał(a):
>>> >
>>> >> Hi Piotr,
>>> >>
>>> >> SNAPSHOT stuff is never downloaded from Maven central.
>>> >>
>>> >> Maven central only serves released stuff. We get SNAPSHOT stuff from
>>> >> the Apache Maven repo.
>>> >>
>>> >> BUT ... we only deploy snapshots for stuff on develop. Otherwise, the
>>> >> versions of feature branches would keep on overwriting the develop
>>> >> artifacts and we would have a non-deterministic behavior. So ... if
>>> >> we merged my changes in compiler and typedefs to develop, then the
>>> >> artifacts would be available in Apache's maven repo, otherwise you
>>> >> have to build them yourself.
>>> >>
>>> >>
>>> *I do understand how it is working and before I reported you an issue I
>>> have build whole framework compiler, typedefs and asjs - next I went to
>>> distribution folder and run:* *mvn clean compile
>>> -DdistributionTargetFolder=d:\Work\royale_ide\distribution *
>>>
>>> *Distribution wasn't created. *
>>>
>>>
>>> > So, assuming my changes were merged to develop, then you could do it
>>> > as
>>> >> you describe.
>>> >>
>>> >> Hope that explains th

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

Chris,

Building whole framework with with-distribution - works - I didn't test yet
created distribution for any project - I will do that soon.

I didn't try yet set distributionTargetFolder=
d:\Work\royale_ide\distribution - I will try tomorrow.

śr., 3 mar 2021 o 16:19 Piotr Zarzycki 
napisał(a):

> Good that you have explained it maybe someone benefit from it.
>
> I'm not sure why this stopped work with -DdistributionTargetFolder and
> it's working when I'm building whole framework... That is very confusing.
>
> śr., 3 mar 2021 o 16:02 Christofer Dutz 
> napisał(a):
>
>> That should have been two lines:
>>
>> set distributionTargetFolder= d:\Work\royale_ide\distribution
>>
>> mvn clean compile
>>
>> Chris
>>
>>
>> -Ursprüngliche Nachricht-
>> Von: Christofer Dutz 
>> Gesendet: Mittwoch, 3. März 2021 15:59
>> An: dev@royale.apache.org
>> Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>>
>> Hi Piotr,
>>
>> you remember that I said you have to set a SYSTEM-property?
>> Cause I thought you can't use maven properties to activate maven
>> profiles.
>>
>> The strange thing was that after you reported that it worked with maven
>> properties, I gave it a try and it worked (Which confused me a bit) I
>> thought perhaps things changed in newer Maven versions. Now looking again
>> for a solution to this problem I again found the info that it has to be a
>> SYSTEM-property:
>>
>> http://maven.40175.n5.nabble.com/Activating-a-profile-in-settings-xml-based-on-a-property-set-in-pom-xml-td512562.html
>>
>> So please set the distributionTargetFolder property this way:
>>
>> set distributionTargetFolder= d:\Work\royale_ide\distribution mvn clean
>> compile
>>
>> And I only explained things in detail because from what you wrote I had
>> the impression that you didn't really understand what's going on and I
>> wanted to provide more background information.
>>
>> Chris
>>
>>
>> -Ursprüngliche Nachricht-
>> Von: Piotr Zarzycki 
>> Gesendet: Mittwoch, 3. März 2021 15:45
>> An: Apache Royale Development 
>> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>>
>> *Comments inline.*
>>
>> śr., 3 mar 2021 o 15:42 Piotr Zarzycki 
>> napisał(a):
>>
>> > >  Maven central only serves released stuff. We get SNAPSHOT stuff
>> > > from
>> > the Apache Maven repo.
>> >
>> > True saying Maven central I meant Apache Maven repo or whatever place
>> > this is stored.
>> >
>> > śr., 3 mar 2021 o 15:41 Christofer Dutz 
>> > napisał(a):
>> >
>> >> Hi Piotr,
>> >>
>> >> SNAPSHOT stuff is never downloaded from Maven central.
>> >>
>> >> Maven central only serves released stuff. We get SNAPSHOT stuff from
>> >> the Apache Maven repo.
>> >>
>> >> BUT ... we only deploy snapshots for stuff on develop. Otherwise, the
>> >> versions of feature branches would keep on overwriting the develop
>> >> artifacts and we would have a non-deterministic behavior. So ... if
>> >> we merged my changes in compiler and typedefs to develop, then the
>> >> artifacts would be available in Apache's maven repo, otherwise you
>> >> have to build them yourself.
>> >>
>> >>
>> *I do understand how it is working and before I reported you an issue I
>> have build whole framework compiler, typedefs and asjs - next I went to
>> distribution folder and run:* *mvn clean compile
>> -DdistributionTargetFolder=d:\Work\royale_ide\distribution *
>>
>> *Distribution wasn't created. *
>>
>>
>> > So, assuming my changes were merged to develop, then you could do it
>> > as
>> >> you describe.
>> >>
>> >> Hope that explains things.
>> >>
>> >> Chris
>> >>
>> >> -Ursprüngliche Nachricht-
>> >> Von: Piotr Zarzycki 
>> >> Gesendet: Mittwoch, 3. März 2021 15:30
>> >> An: Apache Royale Development 
>> >> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>> >>
>> >> Chris,
>> >>
>> >> I'm reporting you how I used to create distribution and how I
>> >> expected to be working. If I remember correctly If I run my command
>> >> pom from distribution should take care of compiler/royale version -
>> >> if the freshest

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Carlos Rovira]

Hi Chris,

I built all (Maven+ANT) and it's working fully as always. Then tried the
distribution on some few different examples to test it with different
setups. And all seems to work ok.

Good work on getting finally this done :)


El mié, 3 mar 2021 a las 16:19, Piotr Zarzycki ()
escribió:

> Good that you have explained it maybe someone benefit from it.
>
> I'm not sure why this stopped work with -DdistributionTargetFolder and it's
> working when I'm building whole framework... That is very confusing.
>
> śr., 3 mar 2021 o 16:02 Christofer Dutz 
> napisał(a):
>
> > That should have been two lines:
> >
> > set distributionTargetFolder= d:\Work\royale_ide\distribution
> >
> > mvn clean compile
> >
> > Chris
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Christofer Dutz 
> > Gesendet: Mittwoch, 3. März 2021 15:59
> > An: dev@royale.apache.org
> > Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > Hi Piotr,
> >
> > you remember that I said you have to set a SYSTEM-property?
> > Cause I thought you can't use maven properties to activate maven
> profiles.
> >
> > The strange thing was that after you reported that it worked with maven
> > properties, I gave it a try and it worked (Which confused me a bit) I
> > thought perhaps things changed in newer Maven versions. Now looking again
> > for a solution to this problem I again found the info that it has to be a
> > SYSTEM-property:
> >
> >
> http://maven.40175.n5.nabble.com/Activating-a-profile-in-settings-xml-based-on-a-property-set-in-pom-xml-td512562.html
> >
> > So please set the distributionTargetFolder property this way:
> >
> > set distributionTargetFolder= d:\Work\royale_ide\distribution mvn clean
> > compile
> >
> > And I only explained things in detail because from what you wrote I had
> > the impression that you didn't really understand what's going on and I
> > wanted to provide more background information.
> >
> > Chris
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Piotr Zarzycki 
> > Gesendet: Mittwoch, 3. März 2021 15:45
> > An: Apache Royale Development 
> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > *Comments inline.*
> >
> > śr., 3 mar 2021 o 15:42 Piotr Zarzycki 
> > napisał(a):
> >
> > > >  Maven central only serves released stuff. We get SNAPSHOT stuff
> > > > from
> > > the Apache Maven repo.
> > >
> > > True saying Maven central I meant Apache Maven repo or whatever place
> > > this is stored.
> > >
> > > śr., 3 mar 2021 o 15:41 Christofer Dutz 
> > > napisał(a):
> > >
> > >> Hi Piotr,
> > >>
> > >> SNAPSHOT stuff is never downloaded from Maven central.
> > >>
> > >> Maven central only serves released stuff. We get SNAPSHOT stuff from
> > >> the Apache Maven repo.
> > >>
> > >> BUT ... we only deploy snapshots for stuff on develop. Otherwise, the
> > >> versions of feature branches would keep on overwriting the develop
> > >> artifacts and we would have a non-deterministic behavior. So ... if
> > >> we merged my changes in compiler and typedefs to develop, then the
> > >> artifacts would be available in Apache's maven repo, otherwise you
> > >> have to build them yourself.
> > >>
> > >>
> > *I do understand how it is working and before I reported you an issue I
> > have build whole framework compiler, typedefs and asjs - next I went to
> > distribution folder and run:* *mvn clean compile
> > -DdistributionTargetFolder=d:\Work\royale_ide\distribution *
> >
> > *Distribution wasn't created. *
> >
> >
> > > So, assuming my changes were merged to develop, then you could do it
> > > as
> > >> you describe.
> > >>
> > >> Hope that explains things.
> > >>
> > >> Chris
> > >>
> > >> -Ursprüngliche Nachricht-
> > >> Von: Piotr Zarzycki 
> > >> Gesendet: Mittwoch, 3. März 2021 15:30
> > >> An: Apache Royale Development 
> > >> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> > >>
> > >> Chris,
> > >>
> > >> I'm reporting you how I used to create distribution and how I
> > >> expected to be working. If I remember correctly If I run my command
> > >> pom from distribution should

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

Good that you have explained it maybe someone benefit from it.

I'm not sure why this stopped work with -DdistributionTargetFolder and it's
working when I'm building whole framework... That is very confusing.

śr., 3 mar 2021 o 16:02 Christofer Dutz 
napisał(a):

> That should have been two lines:
>
> set distributionTargetFolder= d:\Work\royale_ide\distribution
>
> mvn clean compile
>
> Chris
>
>
> -Ursprüngliche Nachricht-
> Von: Christofer Dutz 
> Gesendet: Mittwoch, 3. März 2021 15:59
> An: dev@royale.apache.org
> Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hi Piotr,
>
> you remember that I said you have to set a SYSTEM-property?
> Cause I thought you can't use maven properties to activate maven profiles.
>
> The strange thing was that after you reported that it worked with maven
> properties, I gave it a try and it worked (Which confused me a bit) I
> thought perhaps things changed in newer Maven versions. Now looking again
> for a solution to this problem I again found the info that it has to be a
> SYSTEM-property:
>
> http://maven.40175.n5.nabble.com/Activating-a-profile-in-settings-xml-based-on-a-property-set-in-pom-xml-td512562.html
>
> So please set the distributionTargetFolder property this way:
>
> set distributionTargetFolder= d:\Work\royale_ide\distribution mvn clean
> compile
>
> And I only explained things in detail because from what you wrote I had
> the impression that you didn't really understand what's going on and I
> wanted to provide more background information.
>
> Chris
>
>
> -Ursprüngliche Nachricht-----
> Von: Piotr Zarzycki 
> Gesendet: Mittwoch, 3. März 2021 15:45
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> *Comments inline.*
>
> śr., 3 mar 2021 o 15:42 Piotr Zarzycki 
> napisał(a):
>
> > >  Maven central only serves released stuff. We get SNAPSHOT stuff
> > > from
> > the Apache Maven repo.
> >
> > True saying Maven central I meant Apache Maven repo or whatever place
> > this is stored.
> >
> > śr., 3 mar 2021 o 15:41 Christofer Dutz 
> > napisał(a):
> >
> >> Hi Piotr,
> >>
> >> SNAPSHOT stuff is never downloaded from Maven central.
> >>
> >> Maven central only serves released stuff. We get SNAPSHOT stuff from
> >> the Apache Maven repo.
> >>
> >> BUT ... we only deploy snapshots for stuff on develop. Otherwise, the
> >> versions of feature branches would keep on overwriting the develop
> >> artifacts and we would have a non-deterministic behavior. So ... if
> >> we merged my changes in compiler and typedefs to develop, then the
> >> artifacts would be available in Apache's maven repo, otherwise you
> >> have to build them yourself.
> >>
> >>
> *I do understand how it is working and before I reported you an issue I
> have build whole framework compiler, typedefs and asjs - next I went to
> distribution folder and run:* *mvn clean compile
> -DdistributionTargetFolder=d:\Work\royale_ide\distribution *
>
> *Distribution wasn't created. *
>
>
> > So, assuming my changes were merged to develop, then you could do it
> > as
> >> you describe.
> >>
> >> Hope that explains things.
> >>
> >> Chris
> >>
> >> -Ursprüngliche Nachricht-
> >> Von: Piotr Zarzycki 
> >> Gesendet: Mittwoch, 3. März 2021 15:30
> >> An: Apache Royale Development 
> >> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >>
> >> Chris,
> >>
> >> I'm reporting you how I used to create distribution and how I
> >> expected to be working. If I remember correctly If I run my command
> >> pom from distribution should take care of compiler/royale version -
> >> if the freshest stuff doesn't exists locally it should download from
> >> Maven central - where is the problem ? What has been changed that
> >> this doesn't work like that anymore ?
> >>
> >> In general preparing distribution should take max 5 minutes - I don't
> >> have to build whole framework at all.
> >>
> >> Thanks,
> >> Piotr
> >>
> >> śr., 3 mar 2021 o 14:53 Christofer Dutz 
> >> napisał(a):
> >>
> >> > Hi Piotr,
> >> >
> >> > Well, that's something completely different. So, you want to create
> >> > a distribution from what was already released?
> >> > That's not how the maven-assembly-plugin work

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

*Comments inline.*

śr., 3 mar 2021 o 15:42 Piotr Zarzycki 
napisał(a):

> >  Maven central only serves released stuff. We get SNAPSHOT stuff from
> the Apache Maven repo.
>
> True saying Maven central I meant Apache Maven repo or whatever place this
> is stored.
>
> śr., 3 mar 2021 o 15:41 Christofer Dutz 
> napisał(a):
>
>> Hi Piotr,
>>
>> SNAPSHOT stuff is never downloaded from Maven central.
>>
>> Maven central only serves released stuff. We get SNAPSHOT stuff from the
>> Apache Maven repo.
>>
>> BUT ... we only deploy snapshots for stuff on develop. Otherwise, the
>> versions of feature branches would keep on overwriting the develop
>> artifacts and we would have a non-deterministic behavior. So ... if we
>> merged my changes in compiler and typedefs to develop, then the artifacts
>> would be available in Apache's maven repo, otherwise you have to build them
>> yourself.
>>
>>
*I do understand how it is working and before I reported you an issue I
have build whole framework compiler, typedefs and asjs - next I went to
distribution folder and run:*
*mvn clean compile
-DdistributionTargetFolder=d:\Work\royale_ide\distribution *

*Distribution wasn't created. *


> So, assuming my changes were merged to develop, then you could do it as
>> you describe.
>>
>> Hope that explains things.
>>
>> Chris
>>
>> -Ursprüngliche Nachricht-
>> Von: Piotr Zarzycki 
>> Gesendet: Mittwoch, 3. März 2021 15:30
>> An: Apache Royale Development 
>> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>>
>> Chris,
>>
>> I'm reporting you how I used to create distribution and how I expected to
>> be working. If I remember correctly If I run my command pom from
>> distribution should take care of compiler/royale version - if the freshest
>> stuff doesn't exists locally it should download from Maven central - where
>> is the problem ? What has been changed that this doesn't work like that
>> anymore ?
>>
>> In general preparing distribution should take max 5 minutes - I don't
>> have to build whole framework at all.
>>
>> Thanks,
>> Piotr
>>
>> śr., 3 mar 2021 o 14:53 Christofer Dutz 
>> napisał(a):
>>
>> > Hi Piotr,
>> >
>> > Well, that's something completely different. So, you want to create a
>> > distribution from what was already released?
>> > That's not how the maven-assembly-plugin works. You can't think of the
>> > distribution as some tooling you can apply to something else.
>> > It's more a facet of the current build.
>> >
>> > Theoretically you should be able to do that if we also had a "
>> > royale.framework.version" property and would use that in the
>> distribution.
>> > Then you could override the 4 properties:
>> >
>> > 1.2.1
>> > 0.9.8-SNAPSHOT
>> > 0.9.8-SNAPSHOT
>> > 0.9.8-SNAPSHOT> > framework.version>
>> >
>> > But even that wouldn't work as we would still be missing 2 artifacts
>> > for the older versions.
>> > (I now zip up the shell scripts of the compiler module as one artifact
>> > and the ACE typedef as a second artifact)
>> >
>> > If the distribution built from the current state works, we can start
>> > shipping Maven-built distributions starting now, but not for earlier
>> > versions.
>> >
>> > Chris
>> >
>> >
>> >
>> > -Ursprüngliche Nachricht-
>> > Von: Piotr Zarzycki 
>> > Gesendet: Mittwoch, 3. März 2021 14:36
>> > An: Apache Royale Development 
>> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>> >
>> > Chris,
>> >
>> > What you are showing me is running and building SDK with distribution
>> > - that is ok - this is one option, but If I already build whole SDK or
>> > I would like to based my distribution on what I have in maven central
>> > - I should be able to go to directory royale-asjs\distribution\ and run
>> command:
>> >
>> > mvn clean compile
>> > -DdistributionTargetFolder=d:\Work\royale_ide\distribution
>> >
>> > I don't have to be forced to build SDK in order to prepare distribution.
>> >
>> >
>> > śr., 3 mar 2021 o 14:30 Piotr Zarzycki 
>> > napisał(a):
>> >
>> > > You are running in what directory ?
>> > >
>> > > śr., 3 mar 2021 o 14:27 Christofer Dutz 
>> > > napisał(

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

>  Maven central only serves released stuff. We get SNAPSHOT stuff from the
Apache Maven repo.

True saying Maven central I meant Apache Maven repo or whatever place this
is stored.

śr., 3 mar 2021 o 15:41 Christofer Dutz 
napisał(a):

> Hi Piotr,
>
> SNAPSHOT stuff is never downloaded from Maven central.
>
> Maven central only serves released stuff. We get SNAPSHOT stuff from the
> Apache Maven repo.
>
> BUT ... we only deploy snapshots for stuff on develop. Otherwise, the
> versions of feature branches would keep on overwriting the develop
> artifacts and we would have a non-deterministic behavior. So ... if we
> merged my changes in compiler and typedefs to develop, then the artifacts
> would be available in Apache's maven repo, otherwise you have to build them
> yourself.
>
> So, assuming my changes were merged to develop, then you could do it as
> you describe.
>
> Hope that explains things.
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Piotr Zarzycki 
> Gesendet: Mittwoch, 3. März 2021 15:30
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Chris,
>
> I'm reporting you how I used to create distribution and how I expected to
> be working. If I remember correctly If I run my command pom from
> distribution should take care of compiler/royale version - if the freshest
> stuff doesn't exists locally it should download from Maven central - where
> is the problem ? What has been changed that this doesn't work like that
> anymore ?
>
> In general preparing distribution should take max 5 minutes - I don't have
> to build whole framework at all.
>
> Thanks,
> Piotr
>
> śr., 3 mar 2021 o 14:53 Christofer Dutz 
> napisał(a):
>
> > Hi Piotr,
> >
> > Well, that's something completely different. So, you want to create a
> > distribution from what was already released?
> > That's not how the maven-assembly-plugin works. You can't think of the
> > distribution as some tooling you can apply to something else.
> > It's more a facet of the current build.
> >
> > Theoretically you should be able to do that if we also had a "
> > royale.framework.version" property and would use that in the
> distribution.
> > Then you could override the 4 properties:
> >
> > 1.2.1
> > 0.9.8-SNAPSHOT
> > 0.9.8-SNAPSHOT
> > 0.9.8-SNAPSHOT > framework.version>
> >
> > But even that wouldn't work as we would still be missing 2 artifacts
> > for the older versions.
> > (I now zip up the shell scripts of the compiler module as one artifact
> > and the ACE typedef as a second artifact)
> >
> > If the distribution built from the current state works, we can start
> > shipping Maven-built distributions starting now, but not for earlier
> > versions.
> >
> > Chris
> >
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Piotr Zarzycki 
> > Gesendet: Mittwoch, 3. März 2021 14:36
> > An: Apache Royale Development 
> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > Chris,
> >
> > What you are showing me is running and building SDK with distribution
> > - that is ok - this is one option, but If I already build whole SDK or
> > I would like to based my distribution on what I have in maven central
> > - I should be able to go to directory royale-asjs\distribution\ and run
> command:
> >
> > mvn clean compile
> > -DdistributionTargetFolder=d:\Work\royale_ide\distribution
> >
> > I don't have to be forced to build SDK in order to prepare distribution.
> >
> >
> > śr., 3 mar 2021 o 14:30 Piotr Zarzycki 
> > napisał(a):
> >
> > > You are running in what directory ?
> > >
> > > śr., 3 mar 2021 o 14:27 Christofer Dutz 
> > > napisał(a):
> > >
> > >> So I'm running:
> > >>
> > >> mvn  -DskipTests=true clean install
> > >> -DdistributionTargetFolder=C:\Temp\RoyaleSDK-with-swf -P
> > >> with-distribution,option-with-swf
> > >>
> > >> And It's working nicely .. same as
> > >>
> > >> mvn -DskipTests=true clean install
> > >> -DdistributionTargetFolder=C:\Temp\RoyaleSDK-with-swf -P
> > >> with-distribution
> > >>
> > >>
> > >> Chris
> > >>
> > >>
> > >> -Ursprüngliche Nachricht-
> > >> Von: Piotr Zarzycki 
> > >> Gesendet: Mittwoch, 3. März 2021 13:59
> > >> An: Apache Royale Development 
&

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

Chris,

I'm reporting you how I used to create distribution and how I expected to
be working. If I remember correctly If I run my command pom from
distribution should take care of compiler/royale version - if the freshest
stuff doesn't exists locally it should download from Maven central - where
is the problem ? What has been changed that this doesn't work like that
anymore ?

In general preparing distribution should take max 5 minutes - I don't have
to build whole framework at all.

Thanks,
Piotr

śr., 3 mar 2021 o 14:53 Christofer Dutz 
napisał(a):

> Hi Piotr,
>
> Well, that's something completely different. So, you want to create a
> distribution from what was already released?
> That's not how the maven-assembly-plugin works. You can't think of the
> distribution as some tooling you can apply to something else.
> It's more a facet of the current build.
>
> Theoretically you should be able to do that if we also had a "
> royale.framework.version" property and would use that in the distribution.
> Then you could override the 4 properties:
>
> 1.2.1
> 0.9.8-SNAPSHOT
> 0.9.8-SNAPSHOT
> 0.9.8-SNAPSHOT
>
> But even that wouldn't work as we would still be missing 2 artifacts for
> the older versions.
> (I now zip up the shell scripts of the compiler module as one artifact and
> the ACE typedef as a second artifact)
>
> If the distribution built from the current state works, we can start
> shipping Maven-built distributions starting now, but not for earlier
> versions.
>
> Chris
>
>
>
> -Ursprüngliche Nachricht-
> Von: Piotr Zarzycki 
> Gesendet: Mittwoch, 3. März 2021 14:36
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Chris,
>
> What you are showing me is running and building SDK with distribution -
> that is ok - this is one option, but If I already build whole SDK or I
> would like to based my distribution on what I have in maven central - I
> should be able to go to directory royale-asjs\distribution\ and run command:
>
> mvn clean compile
> -DdistributionTargetFolder=d:\Work\royale_ide\distribution
>
> I don't have to be forced to build SDK in order to prepare distribution.
>
>
> śr., 3 mar 2021 o 14:30 Piotr Zarzycki 
> napisał(a):
>
> > You are running in what directory ?
> >
> > śr., 3 mar 2021 o 14:27 Christofer Dutz 
> > napisał(a):
> >
> >> So I'm running:
> >>
> >> mvn  -DskipTests=true clean install
> >> -DdistributionTargetFolder=C:\Temp\RoyaleSDK-with-swf -P
> >> with-distribution,option-with-swf
> >>
> >> And It's working nicely .. same as
> >>
> >> mvn -DskipTests=true clean install
> >> -DdistributionTargetFolder=C:\Temp\RoyaleSDK-with-swf -P
> >> with-distribution
> >>
> >>
> >> Chris
> >>
> >>
> >> -Ursprüngliche Nachricht-
> >> Von: Piotr Zarzycki 
> >> Gesendet: Mittwoch, 3. März 2021 13:59
> >> An: Apache Royale Development 
> >> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >>
> >> Unfortunately it didn't work. After build in distribution I have
> >> empty folder. Whole build of distribution took 36 seconds, which
> >> definitely is not good:
> >>
> >> [INFO] Reactor Summary for Apache Royale: Distribution 0.9.8-SNAPSHOT:
> >> [INFO]
> >> [INFO] compc .. SUCCESS [
> >>  8.952 s]
> >> [INFO] compiler-asc ... SUCCESS [
> >>  1.559 s]
> >> [INFO] compiler-compc . SUCCESS [
> >>  1.567 s]
> >> [INFO] compiler-compjsc ... SUCCESS [
> >>  1.284 s]
> >> [INFO] compiler-mxmlc . SUCCESS [
> >>  1.347 s]
> >> [INFO] compiler-mxmljsc ... SUCCESS [
> >>  1.683 s]
> >> [INFO] compiler-optimizer . SUCCESS [
> >>  1.675 s]
> >> [INFO] compiler-swfdump ... SUCCESS [
> >>  1.295 s]
> >> [INFO] mxmlc .. SUCCESS [
> >>  1.305 s]
> >> [INFO] Apache Royale: Distribution  SUCCESS [
> >> 14.948 s]
> >> [INFO]
> >> -
> >> ---
> >> [INFO] BUILD SUCCESS
> >> [INFO]
> >> 

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

Chris,

What you are showing me is running and building SDK with distribution -
that is ok - this is one option, but If I already build whole SDK or I
would like to based my distribution on what I have in maven central - I
should be able to go to directory royale-asjs\distribution\ and run command:

mvn clean compile -DdistributionTargetFolder=d:\Work\royale_ide\distribution

I don't have to be forced to build SDK in order to prepare distribution.


śr., 3 mar 2021 o 14:30 Piotr Zarzycki 
napisał(a):

> You are running in what directory ?
>
> śr., 3 mar 2021 o 14:27 Christofer Dutz 
> napisał(a):
>
>> So I'm running:
>>
>> mvn  -DskipTests=true clean install
>> -DdistributionTargetFolder=C:\Temp\RoyaleSDK-with-swf -P
>> with-distribution,option-with-swf
>>
>> And It's working nicely .. same as
>>
>> mvn -DskipTests=true clean install
>> -DdistributionTargetFolder=C:\Temp\RoyaleSDK-with-swf -P with-distribution
>>
>>
>> Chris
>>
>>
>> -Ursprüngliche Nachricht-
>> Von: Piotr Zarzycki 
>> Gesendet: Mittwoch, 3. März 2021 13:59
>> An: Apache Royale Development 
>> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>>
>> Unfortunately it didn't work. After build in distribution I have empty
>> folder. Whole build of distribution took 36 seconds, which definitely is
>> not good:
>>
>> [INFO] Reactor Summary for Apache Royale: Distribution 0.9.8-SNAPSHOT:
>> [INFO]
>> [INFO] compc .. SUCCESS [
>>  8.952 s]
>> [INFO] compiler-asc ... SUCCESS [
>>  1.559 s]
>> [INFO] compiler-compc . SUCCESS [
>>  1.567 s]
>> [INFO] compiler-compjsc ... SUCCESS [
>>  1.284 s]
>> [INFO] compiler-mxmlc . SUCCESS [
>>  1.347 s]
>> [INFO] compiler-mxmljsc ... SUCCESS [
>>  1.683 s]
>> [INFO] compiler-optimizer . SUCCESS [
>>  1.675 s]
>> [INFO] compiler-swfdump ... SUCCESS [
>>  1.295 s]
>> [INFO] mxmlc .. SUCCESS [
>>  1.305 s]
>> [INFO] Apache Royale: Distribution  SUCCESS [
>> 14.948 s]
>> [INFO]
>> 
>> [INFO] BUILD SUCCESS
>> [INFO]
>> 
>> [INFO] Total time:  36.807 s
>> [INFO] Finished at: 2021-03-03T13:55:54+01:00 [INFO]
>> 
>>
>> D:\Work\royale-sources\royale-asjs\distribution>
>>
>> I'm not sure what is happening.
>>
>> śr., 3 mar 2021 o 13:32 Christofer Dutz 
>> napisał(a):
>>
>> > Hi Piotr,
>> >
>> > sorry for the confusion earlier ... guess that was something that
>> > changed in Maven ...
>> > What you did should work and be all you need.
>> > But be sure to check-out all 3 repos in the feature-branch and run a
>> > mvn install on them as they need one new artifact from compiler and
>> > one new artifact from typedefs.
>> >
>> > Chris
>> >
>> >
>> > -Ursprüngliche Nachricht-
>> > Von: Piotr Zarzycki 
>> > Gesendet: Mittwoch, 3. März 2021 12:09
>> > An: Apache Royale Development 
>> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>> >
>> > Cool. I have switched to your branch. How do I generate distribution
>> > now using Maven ? I did that previously by:
>> >
>> > royale-asjs\distribution\ mvn clean compile
>> > -DdistributionTargetFolder=d:\Work\royale_ide\distribution\
>> >
>> > śr., 3 mar 2021 o 11:43 Christofer Dutz 
>> > napisał(a):
>> >
>> > > Ok ...
>> > >
>> > > you don't need to switch all 3 to my "ranch" but to my "branch" -
>> > > Mainly because I don't have a ranch.
>> > >
>> > > But I think I've addressed everything I found ... would be cool if
>> > > you folks could mass-test it.
>> > >
>> > > Chris
>> > >
>> > > -Ursprüngliche Nachricht-
>> > > Von: Christofer Dutz 
>> > > Gesendet: Mittwoch, 3. März 2021 00:09
>> > > An: dev@royale.apache.org
>> > > Betreff: Re: [MAVEN 

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

You are running in what directory ?

śr., 3 mar 2021 o 14:27 Christofer Dutz 
napisał(a):

> So I'm running:
>
> mvn  -DskipTests=true clean install
> -DdistributionTargetFolder=C:\Temp\RoyaleSDK-with-swf -P
> with-distribution,option-with-swf
>
> And It's working nicely .. same as
>
> mvn -DskipTests=true clean install
> -DdistributionTargetFolder=C:\Temp\RoyaleSDK-with-swf -P with-distribution
>
>
> Chris
>
>
> -Ursprüngliche Nachricht-
> Von: Piotr Zarzycki 
> Gesendet: Mittwoch, 3. März 2021 13:59
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Unfortunately it didn't work. After build in distribution I have empty
> folder. Whole build of distribution took 36 seconds, which definitely is
> not good:
>
> [INFO] Reactor Summary for Apache Royale: Distribution 0.9.8-SNAPSHOT:
> [INFO]
> [INFO] compc .. SUCCESS [
>  8.952 s]
> [INFO] compiler-asc ... SUCCESS [
>  1.559 s]
> [INFO] compiler-compc . SUCCESS [
>  1.567 s]
> [INFO] compiler-compjsc ... SUCCESS [
>  1.284 s]
> [INFO] compiler-mxmlc . SUCCESS [
>  1.347 s]
> [INFO] compiler-mxmljsc ... SUCCESS [
>  1.683 s]
> [INFO] compiler-optimizer . SUCCESS [
>  1.675 s]
> [INFO] compiler-swfdump ... SUCCESS [
>  1.295 s]
> [INFO] mxmlc .. SUCCESS [
>  1.305 s]
> [INFO] Apache Royale: Distribution  SUCCESS [
> 14.948 s]
> [INFO]
> 
> [INFO] BUILD SUCCESS
> [INFO]
> 
> [INFO] Total time:  36.807 s
> [INFO] Finished at: 2021-03-03T13:55:54+01:00 [INFO]
> 
>
> D:\Work\royale-sources\royale-asjs\distribution>
>
> I'm not sure what is happening.
>
> śr., 3 mar 2021 o 13:32 Christofer Dutz 
> napisał(a):
>
> > Hi Piotr,
> >
> > sorry for the confusion earlier ... guess that was something that
> > changed in Maven ...
> > What you did should work and be all you need.
> > But be sure to check-out all 3 repos in the feature-branch and run a
> > mvn install on them as they need one new artifact from compiler and
> > one new artifact from typedefs.
> >
> > Chris
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Piotr Zarzycki 
> > Gesendet: Mittwoch, 3. März 2021 12:09
> > An: Apache Royale Development 
> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > Cool. I have switched to your branch. How do I generate distribution
> > now using Maven ? I did that previously by:
> >
> > royale-asjs\distribution\ mvn clean compile
> > -DdistributionTargetFolder=d:\Work\royale_ide\distribution\
> >
> > śr., 3 mar 2021 o 11:43 Christofer Dutz 
> > napisał(a):
> >
> > > Ok ...
> > >
> > > you don't need to switch all 3 to my "ranch" but to my "branch" -
> > > Mainly because I don't have a ranch.
> > >
> > > But I think I've addressed everything I found ... would be cool if
> > > you folks could mass-test it.
> > >
> > > Chris
> > >
> > > -Ursprüngliche Nachricht-
> > > Von: Christofer Dutz 
> > > Gesendet: Mittwoch, 3. März 2021 00:09
> > > An: dev@royale.apache.org
> > > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> > >
> > > And regarding that Halo.swc,
> > >
> > > I would use a different one, as using the js typedef really feels a
> > > bit random.
> > > But that's something for tomorrow... Signing off for today.
> > >
> > > Chris
> > >
> > > Holen Sie sich Outlook für Android<https://aka.ms/ghei36>
> > >
> > > ____
> > > From: Christofer Dutz 
> > > Sent: Wednesday, March 3, 2021 12:06:32 AM
> > > To: dev@royale.apache.org 
> > > Subject: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> > >
> > > No,
> > >
> > > Unfortunately you need to switch all 3 to my ranch and build all of
> > > them, cause it produces one more artifact in compiler and in the
&

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

Unfortunately it didn't work. After build in distribution I have empty
folder. Whole build of distribution took 36 seconds, which definitely is
not good:

[INFO] Reactor Summary for Apache Royale: Distribution 0.9.8-SNAPSHOT:
[INFO]
[INFO] compc .. SUCCESS [
 8.952 s]
[INFO] compiler-asc ... SUCCESS [
 1.559 s]
[INFO] compiler-compc . SUCCESS [
 1.567 s]
[INFO] compiler-compjsc ... SUCCESS [
 1.284 s]
[INFO] compiler-mxmlc . SUCCESS [
 1.347 s]
[INFO] compiler-mxmljsc ... SUCCESS [
 1.683 s]
[INFO] compiler-optimizer . SUCCESS [
 1.675 s]
[INFO] compiler-swfdump ... SUCCESS [
 1.295 s]
[INFO] mxmlc .. SUCCESS [
 1.305 s]
[INFO] Apache Royale: Distribution  SUCCESS [
14.948 s]
[INFO]

[INFO] BUILD SUCCESS
[INFO]

[INFO] Total time:  36.807 s
[INFO] Finished at: 2021-03-03T13:55:54+01:00
[INFO]


D:\Work\royale-sources\royale-asjs\distribution>

I'm not sure what is happening.

śr., 3 mar 2021 o 13:32 Christofer Dutz 
napisał(a):

> Hi Piotr,
>
> sorry for the confusion earlier ... guess that was something that changed
> in Maven ...
> What you did should work and be all you need.
> But be sure to check-out all 3 repos in the feature-branch and run a mvn
> install on them as they need one new artifact from compiler and one new
> artifact from typedefs.
>
> Chris
>
>
> -Ursprüngliche Nachricht-
> Von: Piotr Zarzycki 
> Gesendet: Mittwoch, 3. März 2021 12:09
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Cool. I have switched to your branch. How do I generate distribution now
> using Maven ? I did that previously by:
>
> royale-asjs\distribution\ mvn clean compile
> -DdistributionTargetFolder=d:\Work\royale_ide\distribution\
>
> śr., 3 mar 2021 o 11:43 Christofer Dutz 
> napisał(a):
>
> > Ok ...
> >
> > you don't need to switch all 3 to my "ranch" but to my "branch" -
> > Mainly because I don't have a ranch.
> >
> > But I think I've addressed everything I found ... would be cool if you
> > folks could mass-test it.
> >
> > Chris
> >
> > -Ursprüngliche Nachricht-
> > Von: Christofer Dutz 
> > Gesendet: Mittwoch, 3. März 2021 00:09
> > An: dev@royale.apache.org
> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > And regarding that Halo.swc,
> >
> > I would use a different one, as using the js typedef really feels a
> > bit random.
> > But that's something for tomorrow... Signing off for today.
> >
> > Chris
> >
> > Holen Sie sich Outlook für Android<https://aka.ms/ghei36>
> >
> > 
> > From: Christofer Dutz 
> > Sent: Wednesday, March 3, 2021 12:06:32 AM
> > To: dev@royale.apache.org 
> > Subject: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > No,
> >
> > Unfortunately you need to switch all 3 to my ranch and build all of
> > them, cause it produces one more artifact in compiler and in the typedef.
> >
> > Chris
> >
> > Holen Sie sich Outlook für Android<https://aka.ms/ghei36>
> >
> > 
> > From: Josh Tynjala 
> > Sent: Tuesday, March 2, 2021 11:14:19 PM
> > To: Apache Royale Development 
> > Subject: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > I'm guessing that Flash Builder expects
> > frameworks/themes/Halo/Halo.swc to exist, and it must be a valid .swc
> > file. So, the person who set that up probably just copied one of the
> existing .swc files.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Tue, Mar 2, 2021 at 2:01 PM Christofer Dutz
> > 
> > wrote:
> >
> > > Hi Josh,
> > >
> > > Well it would probably take me 10 seconds to add them ... I just
> > > didn't want to add stuff we don't need.
> > > So I'll leave them away and if someone complains - I'll add them ;-)
> > >
> > > However the comment in the Ant script says:
> > >
> > > 
> > >
&

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Harbs]

ROTFLOL! :-)

> On Mar 3, 2021, at 12:43 PM, Christofer Dutz  
> wrote:
> 
> you don't need to switch all 3 to my "ranch" but to my "branch" - Mainly 
> because I don't have a ranch.

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

Cool. I have switched to your branch. How do I generate distribution now
using Maven ? I did that previously by:

royale-asjs\distribution\ mvn clean compile
-DdistributionTargetFolder=d:\Work\royale_ide\distribution\

śr., 3 mar 2021 o 11:43 Christofer Dutz 
napisał(a):

> Ok ...
>
> you don't need to switch all 3 to my "ranch" but to my "branch" - Mainly
> because I don't have a ranch.
>
> But I think I've addressed everything I found ... would be cool if you
> folks could mass-test it.
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Christofer Dutz 
> Gesendet: Mittwoch, 3. März 2021 00:09
> An: dev@royale.apache.org
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> And regarding that Halo.swc,
>
> I would use a different one, as using the js typedef really feels a bit
> random.
> But that's something for tomorrow... Signing off for today.
>
> Chris
>
> Holen Sie sich Outlook für Android<https://aka.ms/ghei36>
>
> 
> From: Christofer Dutz 
> Sent: Wednesday, March 3, 2021 12:06:32 AM
> To: dev@royale.apache.org 
> Subject: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> No,
>
> Unfortunately you need to switch all 3 to my ranch and build all of them,
> cause it produces one more artifact in compiler and in the typedef.
>
> Chris
>
> Holen Sie sich Outlook für Android<https://aka.ms/ghei36>
>
> ____
> From: Josh Tynjala 
> Sent: Tuesday, March 2, 2021 11:14:19 PM
> To: Apache Royale Development 
> Subject: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> I'm guessing that Flash Builder expects frameworks/themes/Halo/Halo.swc to
> exist, and it must be a valid .swc file. So, the person who set that up
> probably just copied one of the existing .swc files.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Tue, Mar 2, 2021 at 2:01 PM Christofer Dutz 
> wrote:
>
> > Hi Josh,
> >
> > Well it would probably take me 10 seconds to add them ... I just
> > didn't want to add stuff we don't need.
> > So I'll leave them away and if someone complains - I'll add them ;-)
> >
> > However the comment in the Ant script says:
> >
> > 
> >
> > So I already had all the other dummy files in there, so I now just
> > added these.
> >
> > In this block there is however this command which sort of seems pretty
> > strange ... can anyone explain what it's required for?
> >
> >  > tofile="${ROYALE_HOME}/frameworks/themes/Halo/Halo.swc" />
> >
> > It looks like just providing some random SWC file in a location the
> > FlashBuilder might be looking for.
> >
> > Perhaps it would make sense to refactor my descriptors to have a
> > "flashbuilder-support-assembly.xml" which we could one day simply remove.
> >
> > Chris
> >
> > -Ursprüngliche Nachricht-
> > Von: Josh Tynjala 
> > Gesendet: Dienstag, 2. März 2021 22:47
> > An: Apache Royale Development 
> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > > Can anyone tell me what the localfonts.ser, macfonts.ser and
> > > winfonts.ser
> > files are needed for?
> >
> > It's something related to SWF font embedding. I would assume that
> > Flash Builder expects those files to exist, but if the Flash Builder
> > integration document doesn't mention them, then I don't know.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Tue, Mar 2, 2021 at 1:42 PM Christofer Dutz
> > 
> > wrote:
> >
> > > Hi Josh,
> > >
> > > Ok ... so that's done and looks a lot nicer now :-)
> > >
> > > I also finished the config-sanitazion and the config files used in
> > > the Maven distribution should now match the file names in the
> distribution.
> > >
> > > Can anyone tell me what the localfonts.ser, macfonts.ser and
> > > winfonts.ser files are needed for? They are simply completely empty
> > > filed the Ant build createates via "touch" commant. I could add them
> > > to the Maven distribution, but only want to add stuff that's needed.
> > >
> > > But in it's current state I'm quite happy with the new distribution.
> > > It looks pretty clean, everything needed is in there and in the same
> > > location as with the Ant build, but I left away things I tought are
> > > probably not required i

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Christofer Dutz]

And regarding that Halo.swc,

I would use a different one, as using the js typedef really feels a bit random.
But that's something for tomorrow... Signing off for today.

Chris

Holen Sie sich Outlook für Android<https://aka.ms/ghei36>


From: Christofer Dutz 
Sent: Wednesday, March 3, 2021 12:06:32 AM
To: dev@royale.apache.org 
Subject: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

No,

Unfortunately you need to switch all 3 to my ranch and build all of them, cause 
it produces one more artifact in compiler and in the typedef.

Chris

Holen Sie sich Outlook für Android<https://aka.ms/ghei36>


From: Josh Tynjala 
Sent: Tuesday, March 2, 2021 11:14:19 PM
To: Apache Royale Development 
Subject: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

I'm guessing that Flash Builder expects frameworks/themes/Halo/Halo.swc to
exist, and it must be a valid .swc file. So, the person who set that up
probably just copied one of the existing .swc files.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Tue, Mar 2, 2021 at 2:01 PM Christofer Dutz 
wrote:

> Hi Josh,
>
> Well it would probably take me 10 seconds to add them ... I just didn't
> want to add stuff we don't need.
> So I'll leave them away and if someone complains - I'll add them ;-)
>
> However the comment in the Ant script says:
>
> 
>
> So I already had all the other dummy files in there, so I now just added
> these.
>
> In this block there is however this command which sort of seems pretty
> strange ... can anyone explain what it's required for?
>
>  tofile="${ROYALE_HOME}/frameworks/themes/Halo/Halo.swc" />
>
> It looks like just providing some random SWC file in a location the
> FlashBuilder might be looking for.
>
> Perhaps it would make sense to refactor my descriptors to have a
> "flashbuilder-support-assembly.xml" which we could one day simply remove.
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Josh Tynjala 
> Gesendet: Dienstag, 2. März 2021 22:47
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> > Can anyone tell me what the localfonts.ser, macfonts.ser and
> > winfonts.ser
> files are needed for?
>
> It's something related to SWF font embedding. I would assume that Flash
> Builder expects those files to exist, but if the Flash Builder integration
> document doesn't mention them, then I don't know.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Tue, Mar 2, 2021 at 1:42 PM Christofer Dutz 
> wrote:
>
> > Hi Josh,
> >
> > Ok ... so that's done and looks a lot nicer now :-)
> >
> > I also finished the config-sanitazion and the config files used in the
> > Maven distribution should now match the file names in the distribution.
> >
> > Can anyone tell me what the localfonts.ser, macfonts.ser and
> > winfonts.ser files are needed for? They are simply completely empty
> > filed the Ant build createates via "touch" commant. I could add them
> > to the Maven distribution, but only want to add stuff that's needed.
> >
> > But in it's current state I'm quite happy with the new distribution.
> > It looks pretty clean, everything needed is in there and in the same
> > location as with the Ant build, but I left away things I tought are
> > probably not required in the distribution and are results of simply
> > packing the entire project up.
> >
> > I tested it with a number of example projects ant it worked with all
> > of them (Haven't tried all of them though)
> >
> > Would be cool if you could try it out and give me some feedback on it.
> >
> > Chris
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Josh Tynjala 
> > Gesendet: Dienstag, 2. März 2021 22:35
> > An: Apache Royale Development 
> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > The src directory is probably enough for a good IDE experience while
> > developing a Royale app.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Tue, Mar 2, 2021 at 1:27 PM Christofer Dutz
> > 
> > wrote:
> >
> > > Hi all,
> > >
> > > one question: Is it enough to package up the src directories of all
> > > modules in the "projects" directory to allow the code-insights?
> > >
> > > I'm asking, cause I'm only packing up the essential parts of the "asjs"
> > > project and don't want to 

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Christofer Dutz]

No,

Unfortunately you need to switch all 3 to my ranch and build all of them, cause 
it produces one more artifact in compiler and in the typedef.

Chris

Holen Sie sich Outlook für Android<https://aka.ms/ghei36>


From: Josh Tynjala 
Sent: Tuesday, March 2, 2021 11:14:19 PM
To: Apache Royale Development 
Subject: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

I'm guessing that Flash Builder expects frameworks/themes/Halo/Halo.swc to
exist, and it must be a valid .swc file. So, the person who set that up
probably just copied one of the existing .swc files.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Tue, Mar 2, 2021 at 2:01 PM Christofer Dutz 
wrote:

> Hi Josh,
>
> Well it would probably take me 10 seconds to add them ... I just didn't
> want to add stuff we don't need.
> So I'll leave them away and if someone complains - I'll add them ;-)
>
> However the comment in the Ant script says:
>
> 
>
> So I already had all the other dummy files in there, so I now just added
> these.
>
> In this block there is however this command which sort of seems pretty
> strange ... can anyone explain what it's required for?
>
>  tofile="${ROYALE_HOME}/frameworks/themes/Halo/Halo.swc" />
>
> It looks like just providing some random SWC file in a location the
> FlashBuilder might be looking for.
>
> Perhaps it would make sense to refactor my descriptors to have a
> "flashbuilder-support-assembly.xml" which we could one day simply remove.
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Josh Tynjala 
> Gesendet: Dienstag, 2. März 2021 22:47
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> > Can anyone tell me what the localfonts.ser, macfonts.ser and
> > winfonts.ser
> files are needed for?
>
> It's something related to SWF font embedding. I would assume that Flash
> Builder expects those files to exist, but if the Flash Builder integration
> document doesn't mention them, then I don't know.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Tue, Mar 2, 2021 at 1:42 PM Christofer Dutz 
> wrote:
>
> > Hi Josh,
> >
> > Ok ... so that's done and looks a lot nicer now :-)
> >
> > I also finished the config-sanitazion and the config files used in the
> > Maven distribution should now match the file names in the distribution.
> >
> > Can anyone tell me what the localfonts.ser, macfonts.ser and
> > winfonts.ser files are needed for? They are simply completely empty
> > filed the Ant build createates via "touch" commant. I could add them
> > to the Maven distribution, but only want to add stuff that's needed.
> >
> > But in it's current state I'm quite happy with the new distribution.
> > It looks pretty clean, everything needed is in there and in the same
> > location as with the Ant build, but I left away things I tought are
> > probably not required in the distribution and are results of simply
> > packing the entire project up.
> >
> > I tested it with a number of example projects ant it worked with all
> > of them (Haven't tried all of them though)
> >
> > Would be cool if you could try it out and give me some feedback on it.
> >
> > Chris
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Josh Tynjala 
> > Gesendet: Dienstag, 2. März 2021 22:35
> > An: Apache Royale Development 
> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > The src directory is probably enough for a good IDE experience while
> > developing a Royale app.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Tue, Mar 2, 2021 at 1:27 PM Christofer Dutz
> > 
> > wrote:
> >
> > > Hi all,
> > >
> > > one question: Is it enough to package up the src directories of all
> > > modules in the "projects" directory to allow the code-insights?
> > >
> > > I'm asking, cause I'm only packing up the essential parts of the "asjs"
> > > project and don't want to have a half build system included.
> > >
> > > Chris
> > >
> > > -Ursprüngliche Nachricht-
> > > Von: Christofer Dutz 
> > > Gesendet: Montag, 1. März 2021 23:18
> > > An: dev@royale.apache.org
> > > Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> > >
> > > Ah ... ok ... thanks for the explanation.
> > >

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Josh Tynjala]

I'm guessing that Flash Builder expects frameworks/themes/Halo/Halo.swc to
exist, and it must be a valid .swc file. So, the person who set that up
probably just copied one of the existing .swc files.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Tue, Mar 2, 2021 at 2:01 PM Christofer Dutz 
wrote:

> Hi Josh,
>
> Well it would probably take me 10 seconds to add them ... I just didn't
> want to add stuff we don't need.
> So I'll leave them away and if someone complains - I'll add them ;-)
>
> However the comment in the Ant script says:
>
> 
>
> So I already had all the other dummy files in there, so I now just added
> these.
>
> In this block there is however this command which sort of seems pretty
> strange ... can anyone explain what it's required for?
>
>  tofile="${ROYALE_HOME}/frameworks/themes/Halo/Halo.swc" />
>
> It looks like just providing some random SWC file in a location the
> FlashBuilder might be looking for.
>
> Perhaps it would make sense to refactor my descriptors to have a
> "flashbuilder-support-assembly.xml" which we could one day simply remove.
>
> Chris
>
> -Ursprüngliche Nachricht-----
> Von: Josh Tynjala 
> Gesendet: Dienstag, 2. März 2021 22:47
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> > Can anyone tell me what the localfonts.ser, macfonts.ser and
> > winfonts.ser
> files are needed for?
>
> It's something related to SWF font embedding. I would assume that Flash
> Builder expects those files to exist, but if the Flash Builder integration
> document doesn't mention them, then I don't know.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Tue, Mar 2, 2021 at 1:42 PM Christofer Dutz 
> wrote:
>
> > Hi Josh,
> >
> > Ok ... so that's done and looks a lot nicer now :-)
> >
> > I also finished the config-sanitazion and the config files used in the
> > Maven distribution should now match the file names in the distribution.
> >
> > Can anyone tell me what the localfonts.ser, macfonts.ser and
> > winfonts.ser files are needed for? They are simply completely empty
> > filed the Ant build createates via "touch" commant. I could add them
> > to the Maven distribution, but only want to add stuff that's needed.
> >
> > But in it's current state I'm quite happy with the new distribution.
> > It looks pretty clean, everything needed is in there and in the same
> > location as with the Ant build, but I left away things I tought are
> > probably not required in the distribution and are results of simply
> > packing the entire project up.
> >
> > I tested it with a number of example projects ant it worked with all
> > of them (Haven't tried all of them though)
> >
> > Would be cool if you could try it out and give me some feedback on it.
> >
> > Chris
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Josh Tynjala 
> > Gesendet: Dienstag, 2. März 2021 22:35
> > An: Apache Royale Development 
> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > The src directory is probably enough for a good IDE experience while
> > developing a Royale app.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Tue, Mar 2, 2021 at 1:27 PM Christofer Dutz
> > 
> > wrote:
> >
> > > Hi all,
> > >
> > > one question: Is it enough to package up the src directories of all
> > > modules in the "projects" directory to allow the code-insights?
> > >
> > > I'm asking, cause I'm only packing up the essential parts of the "asjs"
> > > project and don't want to have a half build system included.
> > >
> > > Chris
> > >
> > > -Ursprüngliche Nachricht-
> > > Von: Christofer Dutz 
> > > Gesendet: Montag, 1. März 2021 23:18
> > > An: dev@royale.apache.org
> > > Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> > >
> > > Ah ... ok ... thanks for the explanation.
> > >
> > > That does make sense ... guess I just never completely understood
> > > the typedef stuff ;)
> > >
> > > ... so I'll have to find a way to streamline the names of the
> > > typedef libraries in all of these 2 (Well actually probably just 2)
> > > - external-library-path
> > > - js-external-library-path
> > >
> > > But that

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Piotr Zarzycki]

Hi Chris,

In order to test it I should switch in each repository to your branch or
changes are only in asjs repo ?

On Tue, 2 Mar 2021 at 23:01, Christofer Dutz 
wrote:

> Hi Josh,
>
> Well it would probably take me 10 seconds to add them ... I just didn't
> want to add stuff we don't need.
> So I'll leave them away and if someone complains - I'll add them ;-)
>
> However the comment in the Ant script says:
>
> 
>
> So I already had all the other dummy files in there, so I now just added
> these.
>
> In this block there is however this command which sort of seems pretty
> strange ... can anyone explain what it's required for?
>
>  tofile="${ROYALE_HOME}/frameworks/themes/Halo/Halo.swc" />
>
> It looks like just providing some random SWC file in a location the
> FlashBuilder might be looking for.
>
> Perhaps it would make sense to refactor my descriptors to have a
> "flashbuilder-support-assembly.xml" which we could one day simply remove.
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Josh Tynjala 
> Gesendet: Dienstag, 2. März 2021 22:47
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> > Can anyone tell me what the localfonts.ser, macfonts.ser and
> > winfonts.ser
> files are needed for?
>
> It's something related to SWF font embedding. I would assume that Flash
> Builder expects those files to exist, but if the Flash Builder integration
> document doesn't mention them, then I don't know.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Tue, Mar 2, 2021 at 1:42 PM Christofer Dutz 
> wrote:
>
> > Hi Josh,
> >
> > Ok ... so that's done and looks a lot nicer now :-)
> >
> > I also finished the config-sanitazion and the config files used in the
> > Maven distribution should now match the file names in the distribution.
> >
> > Can anyone tell me what the localfonts.ser, macfonts.ser and
> > winfonts.ser files are needed for? They are simply completely empty
> > filed the Ant build createates via "touch" commant. I could add them
> > to the Maven distribution, but only want to add stuff that's needed.
> >
> > But in it's current state I'm quite happy with the new distribution.
> > It looks pretty clean, everything needed is in there and in the same
> > location as with the Ant build, but I left away things I tought are
> > probably not required in the distribution and are results of simply
> > packing the entire project up.
> >
> > I tested it with a number of example projects ant it worked with all
> > of them (Haven't tried all of them though)
> >
> > Would be cool if you could try it out and give me some feedback on it.
> >
> > Chris
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Josh Tynjala 
> > Gesendet: Dienstag, 2. März 2021 22:35
> > An: Apache Royale Development 
> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > The src directory is probably enough for a good IDE experience while
> > developing a Royale app.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Tue, Mar 2, 2021 at 1:27 PM Christofer Dutz
> > 
> > wrote:
> >
> > > Hi all,
> > >
> > > one question: Is it enough to package up the src directories of all
> > > modules in the "projects" directory to allow the code-insights?
> > >
> > > I'm asking, cause I'm only packing up the essential parts of the "asjs"
> > > project and don't want to have a half build system included.
> > >
> > > Chris
> > >
> > > -Ursprüngliche Nachricht-
> > > Von: Christofer Dutz 
> > > Gesendet: Montag, 1. März 2021 23:18
> > > An: dev@royale.apache.org
> > > Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> > >
> > > Ah ... ok ... thanks for the explanation.
> > >
> > > That does make sense ... guess I just never completely understood
> > > the typedef stuff ;)
> > >
> > > ... so I'll have to find a way to streamline the names of the
> > > typedef libraries in all of these 2 (Well actually probably just 2)
> > > - external-library-path
> > > - js-external-library-path
> > >
> > > But that will be a thing for tomorrow ... calling it a day and
> > > signing off for today.
> > >
> > > I just pushed my changes from today 

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Josh Tynjala]

> Can anyone tell me what the localfonts.ser, macfonts.ser and winfonts.ser
files are needed for?

It's something related to SWF font embedding. I would assume that Flash
Builder expects those files to exist, but if the Flash Builder integration
document doesn't mention them, then I don't know.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Tue, Mar 2, 2021 at 1:42 PM Christofer Dutz 
wrote:

> Hi Josh,
>
> Ok ... so that's done and looks a lot nicer now :-)
>
> I also finished the config-sanitazion and the config files used in the
> Maven distribution should now match the file names in the distribution.
>
> Can anyone tell me what the localfonts.ser, macfonts.ser and winfonts.ser
> files are needed for? They are simply completely empty filed the Ant build
> createates via "touch" commant. I could add them to the Maven distribution,
> but only want to add stuff that's needed.
>
> But in it's current state I'm quite happy with the new distribution. It
> looks pretty clean, everything needed is in there and in the same location
> as with the Ant build, but I left away things I tought are probably not
> required in the distribution and are results of simply packing the entire
> project up.
>
> I tested it with a number of example projects ant it worked with all of
> them (Haven't tried all of them though)
>
> Would be cool if you could try it out and give me some feedback on it.
>
> Chris
>
>
> -Ursprüngliche Nachricht-
> Von: Josh Tynjala 
> Gesendet: Dienstag, 2. März 2021 22:35
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> The src directory is probably enough for a good IDE experience while
> developing a Royale app.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Tue, Mar 2, 2021 at 1:27 PM Christofer Dutz 
> wrote:
>
> > Hi all,
> >
> > one question: Is it enough to package up the src directories of all
> > modules in the "projects" directory to allow the code-insights?
> >
> > I'm asking, cause I'm only packing up the essential parts of the "asjs"
> > project and don't want to have a half build system included.
> >
> > Chris
> >
> > -Ursprüngliche Nachricht-
> > Von: Christofer Dutz 
> > Gesendet: Montag, 1. März 2021 23:18
> > An: dev@royale.apache.org
> > Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > Ah ... ok ... thanks for the explanation.
> >
> > That does make sense ... guess I just never completely understood the
> > typedef stuff ;)
> >
> > ... so I'll have to find a way to streamline the names of the typedef
> > libraries in all of these 2 (Well actually probably just 2)
> > - external-library-path
> > - js-external-library-path
> >
> > But that will be a thing for tomorrow ... calling it a day and signing
> > off for today.
> >
> > I just pushed my changes from today ... so if you folks want to check
> > what I'm doing ... now you have something to look at :.)
> >
> > Chris
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Josh Tynjala 
> > Gesendet: Montag, 1. März 2021 23:13
> > An: Apache Royale Development 
> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > As you've seen, there are three different external-library-path options:
> > external-library-path, js-external-library-path and
> > swf-external-library-path.
> >
> > By default, external-library-path is used by both JS and SWF targets,
> > but you can use js-external-library-path or swf-external-library-path
> > to override the external-library-path for a specific target.
> >
> > In other words, if js-external-library-path is defined:
> >
> > - the JS target will use js-external-library-path, and it will ignore
> > external-library-path
> > - the SWF target will still use external-library-path
> >
> > Similarly, if swf-external-library-path is defined:
> >
> > - the SWF target will use swf-external-library-path, and it will
> > ignore external-library-path
> > - the JS target will still use external-library-path
> >
> >  If both js-external-library-path and swf-external-library-path are
> > defined:
> >
> > - the JS target will use js-external-library-path, and it will ignore
> > external-library-path
> > - the SWF target will use swf-external-library-path, and it will
> > ignore external-library-path
> >
> > The air-config.xml, flex-config.xml, and royale-config.xml conf

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Josh Tynjala]

The src directory is probably enough for a good IDE experience while
developing a Royale app.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Tue, Mar 2, 2021 at 1:27 PM Christofer Dutz 
wrote:

> Hi all,
>
> one question: Is it enough to package up the src directories of all
> modules in the "projects" directory to allow the code-insights?
>
> I'm asking, cause I'm only packing up the essential parts of the "asjs"
> project and don't want to have a half build system included.
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Christofer Dutz 
> Gesendet: Montag, 1. März 2021 23:18
> An: dev@royale.apache.org
> Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Ah ... ok ... thanks for the explanation.
>
> That does make sense ... guess I just never completely understood the
> typedef stuff ;)
>
> ... so I'll have to find a way to streamline the names of the typedef
> libraries in all of these 2 (Well actually probably just 2)
> - external-library-path
> - js-external-library-path
>
> But that will be a thing for tomorrow ... calling it a day and signing off
> for today.
>
> I just pushed my changes from today ... so if you folks want to check what
> I'm doing ... now you have something to look at :.)
>
> Chris
>
>
> -Ursprüngliche Nachricht-
> Von: Josh Tynjala 
> Gesendet: Montag, 1. März 2021 23:13
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> As you've seen, there are three different external-library-path options:
> external-library-path, js-external-library-path and
> swf-external-library-path.
>
> By default, external-library-path is used by both JS and SWF targets, but
> you can use js-external-library-path or swf-external-library-path to
> override the external-library-path for a specific target.
>
> In other words, if js-external-library-path is defined:
>
> - the JS target will use js-external-library-path, and it will ignore
> external-library-path
> - the SWF target will still use external-library-path
>
> Similarly, if swf-external-library-path is defined:
>
> - the SWF target will use swf-external-library-path, and it will ignore
> external-library-path
> - the JS target will still use external-library-path
>
>  If both js-external-library-path and swf-external-library-path are
> defined:
>
> - the JS target will use js-external-library-path, and it will ignore
> external-library-path
> - the SWF target will use swf-external-library-path, and it will ignore
> external-library-path
>
> The air-config.xml, flex-config.xml, and royale-config.xml configs are all
> expected to be used for both JS and SWF targets. Different libraries are
> needed for each target, so we're using js-external-library-path to override
> which libraries are used for the JS target. The SWF target will use
> external-library-path.
>
> The other -config.xml files are configs that are expected to be used with
> JS only. Basically, these ones can use external-library-path directly
> because they don't need to target SWF. If we wanted, we could change them
> to use js-external-library-path instead, and they should still work.
>
> In theory, we could always use js-external-library-path and
> swf-external-library-path, and never use external-library-path. However, I
> do not recall if there was some legacy reason (like Flash Builder support)
> for why we defaulted to playerglobal.swc on the external-library-path for
> the SWF target instead of using swf-external-library-path. I think that
> js-external-library-path or swf-external-library-path were introduced
> before I started working on the compiler, so I can only guess.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Mon, Mar 1, 2021 at 1:45 PM Christofer Dutz 
> wrote:
>
> > Hi Josh,
> >
> > While comparing the results I noticed there are some inconsistencies
> > in the config files and I'm currently not quite sure to which is the
> > correct
> > version:
> >
> > In:
> > - ace-config.xml
> > - create-js-config.xml
> > - jquery-config.xml
> > - js-config.xml
> > - node-config.xml
> > The typedefs are defined in an element called: external-library-path
> >
> > In:
> > - air-config.xml
> > - flex-config.xml
> > - royale-config.xml
> > The typedefs are defined in an element called:
> > js-external-library-path
> >
> > Which is the correct version?
> >
> > Also are the target-player and swf-version defined as properties in
> > all configs except:
> > - asdoc-config.xml 

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Josh Tynjala]

As you've seen, there are three different external-library-path options:
external-library-path, js-external-library-path and
swf-external-library-path.

By default, external-library-path is used by both JS and SWF targets, but
you can use js-external-library-path or swf-external-library-path to
override the external-library-path for a specific target.

In other words, if js-external-library-path is defined:

- the JS target will use js-external-library-path, and it will ignore
external-library-path
- the SWF target will still use external-library-path

Similarly, if swf-external-library-path is defined:

- the SWF target will use swf-external-library-path, and it will ignore
external-library-path
- the JS target will still use external-library-path

 If both js-external-library-path and swf-external-library-path are defined:

- the JS target will use js-external-library-path, and it will ignore
external-library-path
- the SWF target will use swf-external-library-path, and it will ignore
external-library-path

The air-config.xml, flex-config.xml, and royale-config.xml configs are all
expected to be used for both JS and SWF targets. Different libraries are
needed for each target, so we're using js-external-library-path to override
which libraries are used for the JS target. The SWF target will use
external-library-path.

The other -config.xml files are configs that are expected to be used with
JS only. Basically, these ones can use external-library-path directly
because they don't need to target SWF. If we wanted, we could change them
to use js-external-library-path instead, and they should still work.

In theory, we could always use js-external-library-path and
swf-external-library-path, and never use external-library-path. However, I
do not recall if there was some legacy reason (like Flash Builder support)
for why we defaulted to playerglobal.swc on the external-library-path for
the SWF target instead of using swf-external-library-path. I think that
js-external-library-path or swf-external-library-path were introduced
before I started working on the compiler, so I can only guess.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Mon, Mar 1, 2021 at 1:45 PM Christofer Dutz 
wrote:

> Hi Josh,
>
> While comparing the results I noticed there are some inconsistencies in
> the config files and I'm currently not quite sure to which is the correct
> version:
>
> In:
> - ace-config.xml
> - create-js-config.xml
> - jquery-config.xml
> - js-config.xml
> - node-config.xml
> The typedefs are defined in an element called: external-library-path
>
> In:
> - air-config.xml
> - flex-config.xml
> - royale-config.xml
> The typedefs are defined in an element called: js-external-library-path
>
> Which is the correct version?
>
> Also are the target-player and swf-version defined as properties in all
> configs except:
> - asdoc-config.xml (player 11.1 swf: 14)
>
> Probably it would make sense to process the asdoc-config.xml the same way
> as all the others.
> Right now I'd just keep it the way it is. Just thought I'd point it out.
>
> Chris
>
>
> -Ursprüngliche Nachricht-----
> Von: Josh Tynjala 
> Gesendet: Montag, 1. März 2021 19:29
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hi Chris,
>
> Yes, that looks to me to be what the Ant build is doing too, so I think
> you are correct.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Mon, Mar 1, 2021 at 10:21 AM Christofer Dutz  >
> wrote:
>
> > Hi Josh
> >
> > Yeah .. I saw in the commit history, that they sort of were creatd
> > shortly after the big-bang ;-) ...
> >
> > That's why I decided to take these as basis.
> >
> > What I'm now doing is generate a config from each by:
> >
> > 1. Replacing the playerversion
> > 2. Replacing the swfversion
> > 3. Replacing the locale
> > 4. In case of a no-swf distribution filtering out the references to
> > playerglobal
> >
> > I hope I got things right ... but I'm only including the output in the
> > distribution and not the templates, as I assume they are not needed.
> >
> > Is that corect?
> >
> > Chris
> >
> > -Ursprüngliche Nachricht-
> > Von: Josh Tynjala 
> > Gesendet: Montag, 1. März 2021 18:46
> > An: Apache Royale Development 
> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > I can tell you that the template config files have existed since the
> > Flex days. The "create-config" task in frameworks/build.xml replaces
> > certain tokens in the template based on the Ant build's current
> configuration.
> >
> > Traditiona

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Josh Tynjala]

Hi Chris,

Yes, that looks to me to be what the Ant build is doing too, so I think you
are correct.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Mon, Mar 1, 2021 at 10:21 AM Christofer Dutz 
wrote:

> Hi Josh
>
> Yeah .. I saw in the commit history, that they sort of were creatd shortly
> after the big-bang ;-) ...
>
> That's why I decided to take these as basis.
>
> What I'm now doing is generate a config from each by:
>
> 1. Replacing the playerversion
> 2. Replacing the swfversion
> 3. Replacing the locale
> 4. In case of a no-swf distribution filtering out the references to
> playerglobal
>
> I hope I got things right ... but I'm only including the output in the
> distribution and not the templates, as I assume they are not needed.
>
> Is that corect?
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Josh Tynjala 
> Gesendet: Montag, 1. März 2021 18:46
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> I can tell you that the template config files have existed since the Flex
> days. The "create-config" task in frameworks/build.xml replaces certain
> tokens in the template based on the Ant build's current configuration.
>
> Traditionally, a distribution would include all of the Ant build.xml files
> to allow users to manually rebuild the framework with local changes. If
> this still holds true, then the config templates are probably required.
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Sun, Feb 28, 2021 at 1:07 PM Christofer Dutz  >
> wrote:
>
> > Hi Carlos,
> >
> > no ... the templates weren't created by me ... they always were in the
> > frameworks dir ... I think the ANT build takes the templates and
> > inserts variables to generate the real versions. I think I'll try to
> > use these to do the same with maven ... unfortunately the files have
> > gotten pretty out of sync.
> >
> > But can anyone here tell me if the "template" files need to be in the
> > distribution? Are they needed for anything? Cause I would just add the
> > generated versions.
> >
> > Chris
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Carlos Rovira 
> > Gesendet: Sonntag, 28. Februar 2021 16:53
> > An: Apache Royale Development 
> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > Hi Chris,
> >
> > >
> > >
> > > I do have some questions:
> > > - the "framework" directory contains a log of tupples:
> > > xyz-config-template.xml and xyz-config.xml: Where does the
> > > xyz-config.xml get generated from the template in the ANT build? (I
> > > assume it generates them from the templates as part of the build)...
> > > could we possibly omit the "templates"? It seems as if they are only
> > > needed to generate the configs for a given set of configured
> > > properties. If that's the case, we don't need them in the distribution.
> > >
> >
> > I always though the template was created by you when you created the
> > maven build for Royale. So if you think you can remove templates, I
> > think it would be good to reduce files if they are not used at all.
> >
> >
> > > - The root element of the flex-config.xml was named "roayale-config"
> > > in the Maven distribution and "flex-config" in the Ant distribution
> > > and it contained a reference to the mxml-2009-manifest.xml. Also did
> > > the Ant version contain a lot more implicit imports as well as a
> > > fxg-base-class element
> > >
> > >
> > maybe this could be the problem we're facing with fx:Array
> >
> >
> > > So far the changes I found ... I updated the distribution in the
> > > "features/distribution-allignment" branch.
> > >
> >
> > Great!
> >
> >
> > >
> > > But I guess I'll keep working on this and try to get the maven
> > > distribution to have the same directory structure as the Ant one
> > > (but excluding all the unnecessary stuff).
> > >
> >
> > Chris, let us know when is safe to test, and I'll do a try.
> >
> > Thanks for working on this!
> >
> >
> > >
> > > Chris
> > >
> > >
> > >
> > > -Ursprüngliche Nachricht-
> > > Von: Christofer Dutz 
> > > Gesendet: Sonntag, 28. Februar 2021 12:28
> > > An: dev@royale.apache.org
> > > Betreff: AW: [MAVEN

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Josh Tynjala]

I can tell you that the template config files have existed since the Flex
days. The "create-config" task in frameworks/build.xml replaces certain
tokens in the template based on the Ant build's current configuration.

Traditionally, a distribution would include all of the Ant build.xml files
to allow users to manually rebuild the framework with local changes. If
this still holds true, then the config templates are probably required.

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Sun, Feb 28, 2021 at 1:07 PM Christofer Dutz 
wrote:

> Hi Carlos,
>
> no ... the templates weren't created by me ... they always were in the
> frameworks dir ... I think the ANT build takes the templates and inserts
> variables to generate the real versions. I think I'll try to use these to
> do the same with maven ... unfortunately the files have gotten pretty out
> of sync.
>
> But can anyone here tell me if the "template" files need to be in the
> distribution? Are they needed for anything? Cause I would just add the
> generated versions.
>
> Chris
>
>
> -Ursprüngliche Nachricht-
> Von: Carlos Rovira 
> Gesendet: Sonntag, 28. Februar 2021 16:53
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hi Chris,
>
> >
> >
> > I do have some questions:
> > - the "framework" directory contains a log of tupples:
> > xyz-config-template.xml and xyz-config.xml: Where does the
> > xyz-config.xml get generated from the template in the ANT build? (I
> > assume it generates them from the templates as part of the build)...
> > could we possibly omit the "templates"? It seems as if they are only
> > needed to generate the configs for a given set of configured
> > properties. If that's the case, we don't need them in the distribution.
> >
>
> I always though the template was created by you when you created the maven
> build for Royale. So if you think you can remove templates, I think it
> would be good to reduce files if they are not used at all.
>
>
> > - The root element of the flex-config.xml was named "roayale-config"
> > in the Maven distribution and "flex-config" in the Ant distribution
> > and it contained a reference to the mxml-2009-manifest.xml. Also did
> > the Ant version contain a lot more implicit imports as well as a
> > fxg-base-class element
> >
> >
> maybe this could be the problem we're facing with fx:Array
>
>
> > So far the changes I found ... I updated the distribution in the
> > "features/distribution-allignment" branch.
> >
>
> Great!
>
>
> >
> > But I guess I'll keep working on this and try to get the maven
> > distribution to have the same directory structure as the Ant one (but
> > excluding all the unnecessary stuff).
> >
>
> Chris, let us know when is safe to test, and I'll do a try.
>
> Thanks for working on this!
>
>
> >
> > Chris
> >
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Christofer Dutz 
> > Gesendet: Sonntag, 28. Februar 2021 12:28
> > An: dev@royale.apache.org
> > Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > Ok ... regarding the Array problem ...
> >
> > I have found the "Array.as" file in "compiler-externc" and
> > "royale-typedefs/js" ... both are identical ...
> > I'm not quite sure which one is used (I'm a bit rusty regarding how
> > all of these externs and stuff work together)
> >
> > I did check and the royale-config.xml lists the mxml-2009-manifest.xml
> > (in both the non-swf as well as the with-swf version) so not quite
> > sure why adding that to the configuration changes anything.
> >
> > Chris
> >
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Christofer Dutz 
> > Gesendet: Sonntag, 28. Februar 2021 12:08
> > An: dev@royale.apache.org
> > Betreff: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > Hi all,
> >
> > so thankfully Carlos re-sent me this link:
> > flex-sdk/README_integration_with_Adobe_FlashBuilder.txt at master *
> > apache/flex-sdk (github.com)<
> > https://github.com/apache/flex-sdk/blob/master/ide/flashbuilder/README
> > _integration_with_Adobe_FlashBuilder.txt
> > >
> >
> > So it seems as if we don't have a
> > ide/flashbuilder/flashbuilder-config.xml
> > with a "express-install-swf" element in it (we don't have the entire
> > file) ... do we need this?
> >
> > Besides that, it seems all is setup as expected.
> >
> > Will continue looking into other things that could be wrong.
> >
> > Chris
> >
>
>
> --
> Carlos Rovira
> Apache Member & Apache Royale PMC
> *Apache Software Foundation*
> http://about.me/carlosrovira
>

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Carlos Rovira]

Hi Chris,

Awesome!, thanks for working on this. I think that will be a great
improvement!

El lun, 1 mar 2021 a las 12:10, Christofer Dutz ()
escribió:

> Hi Carlos,
>
> So in the branch I'm currently working on changing the distribution build
> to ensure the config files are created based on the templates in the
> asjs/frameworks directory. It is my goal that we have only one place to
> update as probably in most cases the Maven version would be forgotten and
> the content would diverge (I saw the config files and bin scripts in the
> maven distribution already greatly diverged) ... as soon as I'm done with
> the changes, it should be in-sync automatically.
>
> It's quite a bit of work as it effectively is like creating the maven
> distribution from scratch and trying to find out what the ANT build does.
>
> I hope I'll be finished soon, but I have to continue this in my free time
> (I already invested allmost the entire last weekend).
>
> Also I'll try to move things to the same location as with the ANT build
> and hopefully include the sources so debugging should work.
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Carlos Rovira 
> Gesendet: Montag, 1. März 2021 10:13
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hi Chris,
>
> Thanks Chris, I don't think templates should be in distribution SDK. I
> think only generated ones. In ANT since it's overlying the repo we can find
> both, but an IDE using the SDK should not need it, just the generated
> versions.
>
> El dom, 28 feb 2021 a las 22:08, Christofer Dutz (<
> christofer.d...@c-ware.de>)
> escribió:
>
> > Hi Carlos,
> >
> > no ... the templates weren't created by me ... they always were in the
> > frameworks dir ... I think the ANT build takes the templates and
> > inserts variables to generate the real versions. I think I'll try to
> > use these to do the same with maven ... unfortunately the files have
> > gotten pretty out of sync.
> >
> > But can anyone here tell me if the "template" files need to be in the
> > distribution? Are they needed for anything? Cause I would just add the
> > generated versions.
> >
> > Chris
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Carlos Rovira 
> > Gesendet: Sonntag, 28. Februar 2021 16:53
> > An: Apache Royale Development 
> > Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > Hi Chris,
> >
> > >
> > >
> > > I do have some questions:
> > > - the "framework" directory contains a log of tupples:
> > > xyz-config-template.xml and xyz-config.xml: Where does the
> > > xyz-config.xml get generated from the template in the ANT build? (I
> > > assume it generates them from the templates as part of the build)...
> > > could we possibly omit the "templates"? It seems as if they are only
> > > needed to generate the configs for a given set of configured
> > > properties. If that's the case, we don't need them in the distribution.
> > >
> >
> > I always though the template was created by you when you created the
> > maven build for Royale. So if you think you can remove templates, I
> > think it would be good to reduce files if they are not used at all.
> >
> >
> > > - The root element of the flex-config.xml was named "roayale-config"
> > > in the Maven distribution and "flex-config" in the Ant distribution
> > > and it contained a reference to the mxml-2009-manifest.xml. Also did
> > > the Ant version contain a lot more implicit imports as well as a
> > > fxg-base-class element
> > >
> > >
> > maybe this could be the problem we're facing with fx:Array
> >
> >
> > > So far the changes I found ... I updated the distribution in the
> > > "features/distribution-allignment" branch.
> > >
> >
> > Great!
> >
> >
> > >
> > > But I guess I'll keep working on this and try to get the maven
> > > distribution to have the same directory structure as the Ant one
> > > (but excluding all the unnecessary stuff).
> > >
> >
> > Chris, let us know when is safe to test, and I'll do a try.
> >
> > Thanks for working on this!
> >
> >
> > >
> > > Chris
> > >
> > >
> > >
> > > -Ursprüngliche Nachricht-
> > > Von: Christofer Dutz 
> > > Gesendet: Sonntag, 28. Februar 2021 12:28
> > > An: dev@royale.apac

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Carlos Rovira]

Hi Chris,

Thanks Chris, I don't think templates should be in distribution SDK. I
think only generated ones. In ANT since it's overlying the repo we can find
both, but an IDE using the SDK should not need it, just the generated
versions.

El dom, 28 feb 2021 a las 22:08, Christofer Dutz ()
escribió:

> Hi Carlos,
>
> no ... the templates weren't created by me ... they always were in the
> frameworks dir ... I think the ANT build takes the templates and inserts
> variables to generate the real versions. I think I'll try to use these to
> do the same with maven ... unfortunately the files have gotten pretty out
> of sync.
>
> But can anyone here tell me if the "template" files need to be in the
> distribution? Are they needed for anything? Cause I would just add the
> generated versions.
>
> Chris
>
>
> -Ursprüngliche Nachricht-
> Von: Carlos Rovira 
> Gesendet: Sonntag, 28. Februar 2021 16:53
> An: Apache Royale Development 
> Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hi Chris,
>
> >
> >
> > I do have some questions:
> > - the "framework" directory contains a log of tupples:
> > xyz-config-template.xml and xyz-config.xml: Where does the
> > xyz-config.xml get generated from the template in the ANT build? (I
> > assume it generates them from the templates as part of the build)...
> > could we possibly omit the "templates"? It seems as if they are only
> > needed to generate the configs for a given set of configured
> > properties. If that's the case, we don't need them in the distribution.
> >
>
> I always though the template was created by you when you created the maven
> build for Royale. So if you think you can remove templates, I think it
> would be good to reduce files if they are not used at all.
>
>
> > - The root element of the flex-config.xml was named "roayale-config"
> > in the Maven distribution and "flex-config" in the Ant distribution
> > and it contained a reference to the mxml-2009-manifest.xml. Also did
> > the Ant version contain a lot more implicit imports as well as a
> > fxg-base-class element
> >
> >
> maybe this could be the problem we're facing with fx:Array
>
>
> > So far the changes I found ... I updated the distribution in the
> > "features/distribution-allignment" branch.
> >
>
> Great!
>
>
> >
> > But I guess I'll keep working on this and try to get the maven
> > distribution to have the same directory structure as the Ant one (but
> > excluding all the unnecessary stuff).
> >
>
> Chris, let us know when is safe to test, and I'll do a try.
>
> Thanks for working on this!
>
>
> >
> > Chris
> >
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Christofer Dutz 
> > Gesendet: Sonntag, 28. Februar 2021 12:28
> > An: dev@royale.apache.org
> > Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > Ok ... regarding the Array problem ...
> >
> > I have found the "Array.as" file in "compiler-externc" and
> > "royale-typedefs/js" ... both are identical ...
> > I'm not quite sure which one is used (I'm a bit rusty regarding how
> > all of these externs and stuff work together)
> >
> > I did check and the royale-config.xml lists the mxml-2009-manifest.xml
> > (in both the non-swf as well as the with-swf version) so not quite
> > sure why adding that to the configuration changes anything.
> >
> > Chris
> >
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Christofer Dutz 
> > Gesendet: Sonntag, 28. Februar 2021 12:08
> > An: dev@royale.apache.org
> > Betreff: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
> >
> > Hi all,
> >
> > so thankfully Carlos re-sent me this link:
> > flex-sdk/README_integration_with_Adobe_FlashBuilder.txt at master *
> > apache/flex-sdk (github.com)<
> > https://github.com/apache/flex-sdk/blob/master/ide/flashbuilder/README
> > _integration_with_Adobe_FlashBuilder.txt
> > >
> >
> > So it seems as if we don't have a
> > ide/flashbuilder/flashbuilder-config.xml
> > with a "express-install-swf" element in it (we don't have the entire
> > file) ... do we need this?
> >
> > Besides that, it seems all is setup as expected.
> >
> > Will continue looking into other things that could be wrong.
> >
> > Chris
> >
>
>
> --
> Carlos Rovira
> Apache Member & Apache Royale PMC
> *Apache Software Foundation*
> http://about.me/carlosrovira
>


-- 
Carlos Rovira
Apache Member & Apache Royale PMC
*Apache Software Foundation*
http://about.me/carlosrovira

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Carlos Rovira]

Hi MJ,

I'm still seeing issues in AppWithLib+SampleLib
let me some time over it, and will back here as I see results
sorry for the noise

El dom, 28 feb 2021 a las 18:11, Maria Jose Esteve ()
escribió:

> Sorry, sorry, sorry, I got confused, I compiled the "old" SampleLib
> project without my changes.
> I have tested it again and although the compilation of the SDK works fine,
> the project still has the same errors.
>
> Hiedra.
>
> -Mensaje original-
> De: Maria Jose Esteve 
> Enviado el: domingo, 28 de febrero de 2021 17:58
> Para: dev@royale.apache.org
> Asunto: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hello,
> Chris, I have compiled the SDK from your branches "ASF_Git _-_ royale-asjs
> / feature / destirbution-allignment" (asjs, compiler, typedefs) and I HAVE
> PERFECTLY BUILT SimpleLib.
>
> Now I'll test the build from develop, with Carlos's changes [Commit:
> 524dfd33f695ba2fef8dcd3380b40b17b0b77bef [524dfd3]] (which don't have your
> changes included)
>
> I hope that much thread does not confuse us ...
>
> Now I tell you.
> Hiedra
>
> -Mensaje original-
> De: Christofer Dutz  Enviado el: domingo, 28
> de febrero de 2021 15:27
> Para: dev@royale.apache.org
> Asunto: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> You can just checkout the branch and give it a try
>
> Chris
>
> Holen Sie sich Outlook für Android<https://aka.ms/ghei36>
>
> ________
> From: Maria Jose Esteve 
> Sent: Sunday, February 28, 2021 2:33:55 PM
> To: dev@royale.apache.org 
> Subject: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hi Chris, do you want me to try some compilation or could I help you with
> something?
>
> Hiedra
>
> -Mensaje original-
> De: Christofer Dutz  Enviado el: domingo, 28
> de febrero de 2021 14:09
> Para: dev@royale.apache.org
> Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> So I'm currently comparing the Maven and the Ant distributions and looking
> for differences.
>
> I do have some questions:
> - the "framework" directory contains a log of tupples:
> xyz-config-template.xml and xyz-config.xml: Where does the xyz-config.xml
> get generated from the template in the ANT build? (I assume it generates
> them from the templates as part of the build)... could we possibly omit the
> "templates"? It seems as if they are only needed to generate the configs
> for a given set of configured properties. If that's the case, we don't need
> them in the distribution.
>
> - I noticed the externs seem to have completely different names (in
> js/libs) (royale-typedefs-js.swc in Maven and js.swc in Ant) ...
> unfortunately the case seems to be sort of random: js for the js extern,
> but GCL for the gcl one)
>
> - I noticed in the maven version the tag is called
> "swf-external-library-path" and in the Ant version it's
> "external-library-path". Same with swf-libary-path, which is called
> "library-path" in the Ant version.
>
> - The Ant version seems to be missing a number of manifests which the
> Maven version has:
> - manifests/svg-manifest-graphics.xml
> - manifests/html-manifest.xml
> - manifests/mdl-manifest.xml
> - manifests/express-manifest.xml
> - manifests/fa-manifest.xml
> - manifests/jewel-manifest.xml
> - manifests/crux-manifest.xml
> - manifests/icons-manifest.xml
>
> - The Maven version was missing an entry in "theme" which points to
> themes/Basic/src/basic.css in the Ant version
>
> - In the most xyz-config.xml files the library path references the JS
> version instead of the SWF version of Languages lib.
>
> - The root element of the flex-config.xml was named "roayale-config" in
> the Maven distribution and "flex-config" in the Ant distribution and it
> contained a reference to the mxml-2009-manifest.xml. Also did the Ant
> version contain a lot more implicit imports as well as a fxg-base-class
> element
>
> - The Maven version of the royale-config.xml adds a path entry to the
> library-path and js-library-path while the Ant version adds each file
> manually.
>
> So far the changes I found ... I updated the distribution in the
> "features/distribution-allignment" branch.
>
> But I guess I'll keep working on this and try to get the maven
> distribution to have the same directory structure as the Ant one (but
> excluding all the unnecessary stuff).
>
> Chris
>
>
>
> -Ursprüngliche Nachricht-
> Von: Christofer Dutz 
> Gesendet: Sonntag, 28. Feb

RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Maria Jose Esteve]

Sorry, sorry, sorry, I got confused, I compiled the "old" SampleLib project 
without my changes.
I have tested it again and although the compilation of the SDK works fine, the 
project still has the same errors.

Hiedra.

-Mensaje original-
De: Maria Jose Esteve  
Enviado el: domingo, 28 de febrero de 2021 17:58
Para: dev@royale.apache.org
Asunto: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Hello,
Chris, I have compiled the SDK from your branches "ASF_Git _-_ royale-asjs / 
feature / destirbution-allignment" (asjs, compiler, typedefs) and I HAVE 
PERFECTLY BUILT SimpleLib.

Now I'll test the build from develop, with Carlos's changes [Commit: 
524dfd33f695ba2fef8dcd3380b40b17b0b77bef [524dfd3]] (which don't have your 
changes included)

I hope that much thread does not confuse us ...

Now I tell you.
Hiedra

-Mensaje original-
De: Christofer Dutz  Enviado el: domingo, 28 de 
febrero de 2021 15:27
Para: dev@royale.apache.org
Asunto: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

You can just checkout the branch and give it a try

Chris

Holen Sie sich Outlook für Android<https://aka.ms/ghei36>


From: Maria Jose Esteve 
Sent: Sunday, February 28, 2021 2:33:55 PM
To: dev@royale.apache.org 
Subject: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Hi Chris, do you want me to try some compilation or could I help you with 
something?

Hiedra

-Mensaje original-
De: Christofer Dutz  Enviado el: domingo, 28 de 
febrero de 2021 14:09
Para: dev@royale.apache.org
Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

So I'm currently comparing the Maven and the Ant distributions and looking for 
differences.

I do have some questions:
- the "framework" directory contains a log of tupples: xyz-config-template.xml 
and xyz-config.xml: Where does the xyz-config.xml get generated from the 
template in the ANT build? (I assume it generates them from the templates as 
part of the build)... could we possibly omit the "templates"? It seems as if 
they are only needed to generate the configs for a given set of configured 
properties. If that's the case, we don't need them in the distribution.

- I noticed the externs seem to have completely different names (in js/libs) 
(royale-typedefs-js.swc in Maven and js.swc in Ant) ... unfortunately the case 
seems to be sort of random: js for the js extern, but GCL for the gcl one)

- I noticed in the maven version the tag is called "swf-external-library-path" 
and in the Ant version it's "external-library-path". Same with swf-libary-path, 
which is called "library-path" in the Ant version.

- The Ant version seems to be missing a number of manifests which the Maven 
version has:
- manifests/svg-manifest-graphics.xml
- manifests/html-manifest.xml
- manifests/mdl-manifest.xml
- manifests/express-manifest.xml
- manifests/fa-manifest.xml
- manifests/jewel-manifest.xml
- manifests/crux-manifest.xml
- manifests/icons-manifest.xml

- The Maven version was missing an entry in "theme" which points to 
themes/Basic/src/basic.css in the Ant version

- In the most xyz-config.xml files the library path references the JS version 
instead of the SWF version of Languages lib.

- The root element of the flex-config.xml was named "roayale-config" in the 
Maven distribution and "flex-config" in the Ant distribution and it contained a 
reference to the mxml-2009-manifest.xml. Also did the Ant version contain a lot 
more implicit imports as well as a fxg-base-class element

- The Maven version of the royale-config.xml adds a path entry to the 
library-path and js-library-path while the Ant version adds each file manually.

So far the changes I found ... I updated the distribution in the 
"features/distribution-allignment" branch.

But I guess I'll keep working on this and try to get the maven distribution to 
have the same directory structure as the Ant one (but excluding all the 
unnecessary stuff).

Chris



-Ursprüngliche Nachricht-
Von: Christofer Dutz 
Gesendet: Sonntag, 28. Februar 2021 12:28
An: dev@royale.apache.org
Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Ok ... regarding the Array problem ...

I have found the "Array.as" file in "compiler-externc" and "royale-typedefs/js" 
... both are identical ...
I'm not quite sure which one is used (I'm a bit rusty regarding how all of 
these externs and stuff work together)

I did check and the royale-config.xml lists the mxml-2009-manifest.xml (in both 
the non-swf as well as the with-swf version) so not quite sure why adding that 
to the configuration changes anything.

Chris



-Ursprüngliche Nachricht-
Von: Christofer Dutz 
Gesendet: Sonntag, 28. Februar 2021 12:08
An: d

RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Maria Jose Esteve]

Hello,
Chris, I have compiled the SDK from your branches "ASF_Git _-_ royale-asjs / 
feature / destirbution-allignment" (asjs, compiler, typedefs) and I HAVE 
PERFECTLY BUILT SimpleLib.

Now I'll test the build from develop, with Carlos's changes [Commit: 
524dfd33f695ba2fef8dcd3380b40b17b0b77bef [524dfd3]] (which don't have your 
changes included)

I hope that much thread does not confuse us ...

Now I tell you.
Hiedra

-Mensaje original-
De: Christofer Dutz  
Enviado el: domingo, 28 de febrero de 2021 15:27
Para: dev@royale.apache.org
Asunto: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

You can just checkout the branch and give it a try

Chris

Holen Sie sich Outlook für Android<https://aka.ms/ghei36>


From: Maria Jose Esteve 
Sent: Sunday, February 28, 2021 2:33:55 PM
To: dev@royale.apache.org 
Subject: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Hi Chris, do you want me to try some compilation or could I help you with 
something?

Hiedra

-Mensaje original-
De: Christofer Dutz  Enviado el: domingo, 28 de 
febrero de 2021 14:09
Para: dev@royale.apache.org
Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

So I'm currently comparing the Maven and the Ant distributions and looking for 
differences.

I do have some questions:
- the "framework" directory contains a log of tupples: xyz-config-template.xml 
and xyz-config.xml: Where does the xyz-config.xml get generated from the 
template in the ANT build? (I assume it generates them from the templates as 
part of the build)... could we possibly omit the "templates"? It seems as if 
they are only needed to generate the configs for a given set of configured 
properties. If that's the case, we don't need them in the distribution.

- I noticed the externs seem to have completely different names (in js/libs) 
(royale-typedefs-js.swc in Maven and js.swc in Ant) ... unfortunately the case 
seems to be sort of random: js for the js extern, but GCL for the gcl one)

- I noticed in the maven version the tag is called "swf-external-library-path" 
and in the Ant version it's "external-library-path". Same with swf-libary-path, 
which is called "library-path" in the Ant version.

- The Ant version seems to be missing a number of manifests which the Maven 
version has:
- manifests/svg-manifest-graphics.xml
- manifests/html-manifest.xml
- manifests/mdl-manifest.xml
- manifests/express-manifest.xml
- manifests/fa-manifest.xml
- manifests/jewel-manifest.xml
- manifests/crux-manifest.xml
- manifests/icons-manifest.xml

- The Maven version was missing an entry in "theme" which points to 
themes/Basic/src/basic.css in the Ant version

- In the most xyz-config.xml files the library path references the JS version 
instead of the SWF version of Languages lib.

- The root element of the flex-config.xml was named "roayale-config" in the 
Maven distribution and "flex-config" in the Ant distribution and it contained a 
reference to the mxml-2009-manifest.xml. Also did the Ant version contain a lot 
more implicit imports as well as a fxg-base-class element

- The Maven version of the royale-config.xml adds a path entry to the 
library-path and js-library-path while the Ant version adds each file manually.

So far the changes I found ... I updated the distribution in the 
"features/distribution-allignment" branch.

But I guess I'll keep working on this and try to get the maven distribution to 
have the same directory structure as the Ant one (but excluding all the 
unnecessary stuff).

Chris



-Ursprüngliche Nachricht-
Von: Christofer Dutz 
Gesendet: Sonntag, 28. Februar 2021 12:28
An: dev@royale.apache.org
Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Ok ... regarding the Array problem ...

I have found the "Array.as" file in "compiler-externc" and "royale-typedefs/js" 
... both are identical ...
I'm not quite sure which one is used (I'm a bit rusty regarding how all of 
these externs and stuff work together)

I did check and the royale-config.xml lists the mxml-2009-manifest.xml (in both 
the non-swf as well as the with-swf version) so not quite sure why adding that 
to the configuration changes anything.

Chris



-Ursprüngliche Nachricht-
Von: Christofer Dutz 
Gesendet: Sonntag, 28. Februar 2021 12:08
An: dev@royale.apache.org
Betreff: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Hi all,

so thankfully Carlos re-sent me this link:
flex-sdk/README_integration_with_Adobe_FlashBuilder.txt at master * 
apache/flex-sdk 
(github.com)<https://github.com/apache/flex-sdk/blob/master/ide/flashbuilder/README_integration_with_Adobe_FlashBuilder.txt>

So it seems as if we don't have a ide/flashbuilder/flashbuilder-config.xml with 
a "expres

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Carlos Rovira]

Hi Chris,

>
>
> I do have some questions:
> - the "framework" directory contains a log of tupples:
> xyz-config-template.xml and xyz-config.xml: Where does the xyz-config.xml
> get generated from the template in the ANT build? (I assume it generates
> them from the templates as part of the build)... could we possibly omit the
> "templates"? It seems as if they are only needed to generate the configs
> for a given set of configured properties. If that's the case, we don't need
> them in the distribution.
>

I always though the template was created by you when you created the maven
build for Royale. So if you think you can remove templates, I think it
would be good to reduce files if they are not used at all.


> - The root element of the flex-config.xml was named "roayale-config" in
> the Maven distribution and "flex-config" in the Ant distribution and it
> contained a reference to the mxml-2009-manifest.xml. Also did the Ant
> version contain a lot more implicit imports as well as a fxg-base-class
> element
>
>
maybe this could be the problem we're facing with fx:Array


> So far the changes I found ... I updated the distribution in the
> "features/distribution-allignment" branch.
>

Great!


>
> But I guess I'll keep working on this and try to get the maven
> distribution to have the same directory structure as the Ant one (but
> excluding all the unnecessary stuff).
>

Chris, let us know when is safe to test, and I'll do a try.

Thanks for working on this!


>
> Chris
>
>
>
> -Ursprüngliche Nachricht-
> Von: Christofer Dutz 
> Gesendet: Sonntag, 28. Februar 2021 12:28
> An: dev@royale.apache.org
> Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Ok ... regarding the Array problem ...
>
> I have found the "Array.as" file in "compiler-externc" and
> "royale-typedefs/js" ... both are identical ...
> I'm not quite sure which one is used (I'm a bit rusty regarding how all of
> these externs and stuff work together)
>
> I did check and the royale-config.xml lists the mxml-2009-manifest.xml (in
> both the non-swf as well as the with-swf version) so not quite sure why
> adding that to the configuration changes anything.
>
> Chris
>
>
>
> -Ursprüngliche Nachricht-
> Von: Christofer Dutz 
> Gesendet: Sonntag, 28. Februar 2021 12:08
> An: dev@royale.apache.org
> Betreff: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned
>
> Hi all,
>
> so thankfully Carlos re-sent me this link:
> flex-sdk/README_integration_with_Adobe_FlashBuilder.txt at master *
> apache/flex-sdk (github.com)<
> https://github.com/apache/flex-sdk/blob/master/ide/flashbuilder/README_integration_with_Adobe_FlashBuilder.txt
> >
>
> So it seems as if we don't have a ide/flashbuilder/flashbuilder-config.xml
> with a "express-install-swf" element in it (we don't have the entire file)
> ... do we need this?
>
> Besides that, it seems all is setup as expected.
>
> Will continue looking into other things that could be wrong.
>
> Chris
>


-- 
Carlos Rovira
Apache Member & Apache Royale PMC
*Apache Software Foundation*
http://about.me/carlosrovira

Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Christofer Dutz]

You can just checkout the branch and give it a try

Chris

Holen Sie sich Outlook für Android<https://aka.ms/ghei36>


From: Maria Jose Esteve 
Sent: Sunday, February 28, 2021 2:33:55 PM
To: dev@royale.apache.org 
Subject: RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Hi Chris, do you want me to try some compilation or could I help you with 
something?

Hiedra

-Mensaje original-
De: Christofer Dutz 
Enviado el: domingo, 28 de febrero de 2021 14:09
Para: dev@royale.apache.org
Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

So I'm currently comparing the Maven and the Ant distributions and looking for 
differences.

I do have some questions:
- the "framework" directory contains a log of tupples: xyz-config-template.xml 
and xyz-config.xml: Where does the xyz-config.xml get generated from the 
template in the ANT build? (I assume it generates them from the templates as 
part of the build)... could we possibly omit the "templates"? It seems as if 
they are only needed to generate the configs for a given set of configured 
properties. If that's the case, we don't need them in the distribution.

- I noticed the externs seem to have completely different names (in js/libs) 
(royale-typedefs-js.swc in Maven and js.swc in Ant) ... unfortunately the case 
seems to be sort of random: js for the js extern, but GCL for the gcl one)

- I noticed in the maven version the tag is called "swf-external-library-path" 
and in the Ant version it's "external-library-path". Same with swf-libary-path, 
which is called "library-path" in the Ant version.

- The Ant version seems to be missing a number of manifests which the Maven 
version has:
- manifests/svg-manifest-graphics.xml
- manifests/html-manifest.xml
- manifests/mdl-manifest.xml
- manifests/express-manifest.xml
- manifests/fa-manifest.xml
- manifests/jewel-manifest.xml
- manifests/crux-manifest.xml
- manifests/icons-manifest.xml

- The Maven version was missing an entry in "theme" which points to 
themes/Basic/src/basic.css in the Ant version

- In the most xyz-config.xml files the library path references the JS version 
instead of the SWF version of Languages lib.

- The root element of the flex-config.xml was named "roayale-config" in the 
Maven distribution and "flex-config" in the Ant distribution and it contained a 
reference to the mxml-2009-manifest.xml. Also did the Ant version contain a lot 
more implicit imports as well as a fxg-base-class element

- The Maven version of the royale-config.xml adds a path entry to the 
library-path and js-library-path while the Ant version adds each file manually.

So far the changes I found ... I updated the distribution in the 
"features/distribution-allignment" branch.

But I guess I'll keep working on this and try to get the maven distribution to 
have the same directory structure as the Ant one (but excluding all the 
unnecessary stuff).

Chris



-Ursprüngliche Nachricht-
Von: Christofer Dutz 
Gesendet: Sonntag, 28. Februar 2021 12:28
An: dev@royale.apache.org
Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Ok ... regarding the Array problem ...

I have found the "Array.as" file in "compiler-externc" and "royale-typedefs/js" 
... both are identical ...
I'm not quite sure which one is used (I'm a bit rusty regarding how all of 
these externs and stuff work together)

I did check and the royale-config.xml lists the mxml-2009-manifest.xml (in both 
the non-swf as well as the with-swf version) so not quite sure why adding that 
to the configuration changes anything.

Chris



-Ursprüngliche Nachricht-
Von: Christofer Dutz 
Gesendet: Sonntag, 28. Februar 2021 12:08
An: dev@royale.apache.org
Betreff: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Hi all,

so thankfully Carlos re-sent me this link:
flex-sdk/README_integration_with_Adobe_FlashBuilder.txt at master * 
apache/flex-sdk 
(github.com)<https://github.com/apache/flex-sdk/blob/master/ide/flashbuilder/README_integration_with_Adobe_FlashBuilder.txt>

So it seems as if we don't have a ide/flashbuilder/flashbuilder-config.xml with 
a "express-install-swf" element in it (we don't have the entire file) ... do we 
need this?

Besides that, it seems all is setup as expected.

Will continue looking into other things that could be wrong.

Chris

RE: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

[Maria Jose Esteve]

Hi Chris, do you want me to try some compilation or could I help you with 
something?

Hiedra

-Mensaje original-
De: Christofer Dutz  
Enviado el: domingo, 28 de febrero de 2021 14:09
Para: dev@royale.apache.org
Asunto: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

So I'm currently comparing the Maven and the Ant distributions and looking for 
differences.

I do have some questions:
- the "framework" directory contains a log of tupples: xyz-config-template.xml 
and xyz-config.xml: Where does the xyz-config.xml get generated from the 
template in the ANT build? (I assume it generates them from the templates as 
part of the build)... could we possibly omit the "templates"? It seems as if 
they are only needed to generate the configs for a given set of configured 
properties. If that's the case, we don't need them in the distribution.

- I noticed the externs seem to have completely different names (in js/libs) 
(royale-typedefs-js.swc in Maven and js.swc in Ant) ... unfortunately the case 
seems to be sort of random: js for the js extern, but GCL for the gcl one)

- I noticed in the maven version the tag is called "swf-external-library-path" 
and in the Ant version it's "external-library-path". Same with swf-libary-path, 
which is called "library-path" in the Ant version.

- The Ant version seems to be missing a number of manifests which the Maven 
version has: 
- manifests/svg-manifest-graphics.xml
- manifests/html-manifest.xml
- manifests/mdl-manifest.xml
- manifests/express-manifest.xml
- manifests/fa-manifest.xml
- manifests/jewel-manifest.xml
- manifests/crux-manifest.xml
- manifests/icons-manifest.xml

- The Maven version was missing an entry in "theme" which points to 
themes/Basic/src/basic.css in the Ant version

- In the most xyz-config.xml files the library path references the JS version 
instead of the SWF version of Languages lib.

- The root element of the flex-config.xml was named "roayale-config" in the 
Maven distribution and "flex-config" in the Ant distribution and it contained a 
reference to the mxml-2009-manifest.xml. Also did the Ant version contain a lot 
more implicit imports as well as a fxg-base-class element

- The Maven version of the royale-config.xml adds a path entry to the 
library-path and js-library-path while the Ant version adds each file manually.

So far the changes I found ... I updated the distribution in the 
"features/distribution-allignment" branch.

But I guess I'll keep working on this and try to get the maven distribution to 
have the same directory structure as the Ant one (but excluding all the 
unnecessary stuff).

Chris



-Ursprüngliche Nachricht-
Von: Christofer Dutz  
Gesendet: Sonntag, 28. Februar 2021 12:28
An: dev@royale.apache.org
Betreff: AW: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Ok ... regarding the Array problem ...

I have found the "Array.as" file in "compiler-externc" and "royale-typedefs/js" 
... both are identical ...
I'm not quite sure which one is used (I'm a bit rusty regarding how all of 
these externs and stuff work together)

I did check and the royale-config.xml lists the mxml-2009-manifest.xml (in both 
the non-swf as well as the with-swf version) so not quite sure why adding that 
to the configuration changes anything.

Chris



-Ursprüngliche Nachricht-
Von: Christofer Dutz  
Gesendet: Sonntag, 28. Februar 2021 12:08
An: dev@royale.apache.org
Betreff: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

Hi all,

so thankfully Carlos re-sent me this link:
flex-sdk/README_integration_with_Adobe_FlashBuilder.txt at master * 
apache/flex-sdk 
(github.com)

So it seems as if we don't have a ide/flashbuilder/flashbuilder-config.xml with 
a "express-install-swf" element in it (we don't have the entire file) ... do we 
need this?

Besides that, it seems all is setup as expected.

Will continue looking into other things that could be wrong.

Chris

Re: Maven DIstribution

[Christofer Dutz]

Hi Harbs, 

I checked out the rc4 tag for my test ... so I assume the RC is already cut.

Chris

Am 06.05.20, 12:04 schrieb "Harbs" :

Is there any chance of getting the latest changes to XML in the release? 
There were some regressive bugs that were just fixed.

> On May 6, 2020, at 7:50 AM, Yishay Weiss  wrote:
> 
> I’m close to starting a vote on rc4

Re: Maven DIstribution

[Harbs]

Is there any chance of getting the latest changes to XML in the release? There 
were some regressive bugs that were just fixed.

> On May 6, 2020, at 7:50 AM, Yishay Weiss  wrote:
> 
> I’m close to starting a vote on rc4

Re: Maven DIstribution

[Christofer Dutz]

Also confirmed:

So a release candidate should be ok ... if the release branches should be used 
as base for bugfix versions ... perhaps a step should be added to bump the 
compiler and typedef version properties to the next development version?

Chris



Am 06.05.20, 10:17 schrieb "Christofer Dutz" :

Hi all,

I confirm Alex' findings.

The reason is that in the release-branch the version of the asjs artifacts 
differs from that of the compiler.
The compiler version is 0.9.7 but the asjs version is 0.9.8-SNAPSHOT.

In general we should probably update the "rars" sub-modules of the 
distribution to use ${royale.compiler.version} as version.

But the current state in "release/0.9.7" isn't a real valid state anyway 
... usually you would probably bump the compiler and typedefs versions to the 
new SNAPSHOT versions after releasing the module. In that case the versions 
would be back in sync.

Regarding the release ... I think this doesn't have any impact on the 
release itself. Cause in this the compiler, typedefs and asjs all have the 
version 0.9.7 and therefore this shouldn't be an issue.

I'll checkout the release-tag and try again and report back.

Chris



Am 06.05.20, 09:51 schrieb "Christofer Dutz" :

Hi all,

Just some background to get rid of the confusion:
The "with-distribution" enables the distributions you make Maven build 
the archives ... if you provide the distributionTargetFolder property it also 
builds an "exploded" version, which you can directly use in an IDE. If you 
execute the build in the distribution folder, you don't even need to activate 
the "with-distribution" profile.

The artifact it's looking for is one of the jars built as child modules 
of the distribution, which just take a compiler artifact and changes the 
executable class. So if you build the distribution module, so should the 
sub-module.

One thing ... @Alex did you just execute the distribution and prevent 
maven from building anything else? Then this will be the cause ... as you 
haven't enabled the "with-distribution" profile, maven won't build it but also 
not the  9 sub-modules of that module ... so if you now just build only the 
distribution module, it will not find the other stuff it's looking for.

So I just built the distribution in develop and all worked ... now I'm 
switching to the release-branch (is there a reason they are called "rel/0.9.7" 
for compiler and typedefs and "release/0.9.7" for asjs?

Will report anything I find.

Chris





Am 06.05.20, 07:32 schrieb "Alex Harui" :

FWIW, I added -DdistributionTargetFolder= and still the same 
failure.

On 5/5/20, 4:29 PM, "Alex Harui"  wrote:

Maybe. I can't find how to do that in the instructions.  I 
assumed it would end up in a "target" folder.

On 5/5/20, 3:09 PM, "Piotr Zarzycki" 
 wrote:

Shouldn't you add path where distribution will be saved?

On Tue, May 5, 2020, 7:25 PM Alex Harui 
 wrote:

> It may be too early in the morning for me, but I switched 
to the
> release/0.9.7 branch in all 3 repos, did a "mvn clean 
install" all of them,
> then back in royale-asjs I ran
> "mvn -Pwith-distribution clean install" and got an error:
>
> Failed to create assembly: Error adding file to archive:
> 
/Users/aharui/git/royale/maven/royale-asjs/distribution/jars/compiler-mxmljsc/target/compiler-mxmljsc-0.9.7.jar
>
> Interestingly, maybe related, the output on the CI server 
says things like
> " Skipping the assembly in this project because it's not 
the Execution
> Root" which may be why it gets past this point.  So I 
think we're missing
> something somewhere.  I thought it would be as simple as 
selecting that
> profile.
>
> Thoughts?
> -Alex
>
>

Re: Maven DIstribution

[Christofer Dutz]

Hi all,

I confirm Alex' findings.

The reason is that in the release-branch the version of the asjs artifacts 
differs from that of the compiler.
The compiler version is 0.9.7 but the asjs version is 0.9.8-SNAPSHOT.

In general we should probably update the "rars" sub-modules of the distribution 
to use ${royale.compiler.version} as version.

But the current state in "release/0.9.7" isn't a real valid state anyway ... 
usually you would probably bump the compiler and typedefs versions to the new 
SNAPSHOT versions after releasing the module. In that case the versions would 
be back in sync.

Regarding the release ... I think this doesn't have any impact on the release 
itself. Cause in this the compiler, typedefs and asjs all have the version 
0.9.7 and therefore this shouldn't be an issue.

I'll checkout the release-tag and try again and report back.

Chris



Am 06.05.20, 09:51 schrieb "Christofer Dutz" :

Hi all,

Just some background to get rid of the confusion:
The "with-distribution" enables the distributions you make Maven build the 
archives ... if you provide the distributionTargetFolder property it also 
builds an "exploded" version, which you can directly use in an IDE. If you 
execute the build in the distribution folder, you don't even need to activate 
the "with-distribution" profile.

The artifact it's looking for is one of the jars built as child modules of 
the distribution, which just take a compiler artifact and changes the 
executable class. So if you build the distribution module, so should the 
sub-module.

One thing ... @Alex did you just execute the distribution and prevent maven 
from building anything else? Then this will be the cause ... as you haven't 
enabled the "with-distribution" profile, maven won't build it but also not the  
9 sub-modules of that module ... so if you now just build only the distribution 
module, it will not find the other stuff it's looking for.

So I just built the distribution in develop and all worked ... now I'm 
switching to the release-branch (is there a reason they are called "rel/0.9.7" 
for compiler and typedefs and "release/0.9.7" for asjs?

Will report anything I find.

Chris





Am 06.05.20, 07:32 schrieb "Alex Harui" :

FWIW, I added -DdistributionTargetFolder= and still the same failure.

On 5/5/20, 4:29 PM, "Alex Harui"  wrote:

Maybe. I can't find how to do that in the instructions.  I assumed 
it would end up in a "target" folder.

On 5/5/20, 3:09 PM, "Piotr Zarzycki"  
wrote:

Shouldn't you add path where distribution will be saved?

On Tue, May 5, 2020, 7:25 PM Alex Harui 
 wrote:

> It may be too early in the morning for me, but I switched to 
the
> release/0.9.7 branch in all 3 repos, did a "mvn clean 
install" all of them,
> then back in royale-asjs I ran
> "mvn -Pwith-distribution clean install" and got an error:
>
> Failed to create assembly: Error adding file to archive:
> 
/Users/aharui/git/royale/maven/royale-asjs/distribution/jars/compiler-mxmljsc/target/compiler-mxmljsc-0.9.7.jar
>
> Interestingly, maybe related, the output on the CI server 
says things like
> " Skipping the assembly in this project because it's not the 
Execution
> Root" which may be why it gets past this point.  So I think 
we're missing
> something somewhere.  I thought it would be as simple as 
selecting that
> profile.
>
> Thoughts?
> -Alex
>
>

Re: Maven DIstribution

[Christofer Dutz]

Hi all,

Just some background to get rid of the confusion:
The "with-distribution" enables the distributions you make Maven build the 
archives ... if you provide the distributionTargetFolder property it also 
builds an "exploded" version, which you can directly use in an IDE. If you 
execute the build in the distribution folder, you don't even need to activate 
the "with-distribution" profile.

The artifact it's looking for is one of the jars built as child modules of the 
distribution, which just take a compiler artifact and changes the executable 
class. So if you build the distribution module, so should the sub-module.

One thing ... @Alex did you just execute the distribution and prevent maven 
from building anything else? Then this will be the cause ... as you haven't 
enabled the "with-distribution" profile, maven won't build it but also not the  
9 sub-modules of that module ... so if you now just build only the distribution 
module, it will not find the other stuff it's looking for.

So I just built the distribution in develop and all worked ... now I'm 
switching to the release-branch (is there a reason they are called "rel/0.9.7" 
for compiler and typedefs and "release/0.9.7" for asjs?

Will report anything I find.

Chris





Am 06.05.20, 07:32 schrieb "Alex Harui" :

FWIW, I added -DdistributionTargetFolder= and still the same failure.

On 5/5/20, 4:29 PM, "Alex Harui"  wrote:

Maybe. I can't find how to do that in the instructions.  I assumed it 
would end up in a "target" folder.

On 5/5/20, 3:09 PM, "Piotr Zarzycki"  wrote:

Shouldn't you add path where distribution will be saved?

On Tue, May 5, 2020, 7:25 PM Alex Harui  
wrote:

> It may be too early in the morning for me, but I switched to the
> release/0.9.7 branch in all 3 repos, did a "mvn clean install" 
all of them,
> then back in royale-asjs I ran
> "mvn -Pwith-distribution clean install" and got an error:
>
> Failed to create assembly: Error adding file to archive:
> 
/Users/aharui/git/royale/maven/royale-asjs/distribution/jars/compiler-mxmljsc/target/compiler-mxmljsc-0.9.7.jar
>
> Interestingly, maybe related, the output on the CI server says 
things like
> " Skipping the assembly in this project because it's not the 
Execution
> Root" which may be why it gets past this point.  So I think we're 
missing
> something somewhere.  I thought it would be as simple as 
selecting that
> profile.
>
> Thoughts?
> -Alex
>
>

Re: Maven DIstribution

[Alex Harui]

FWIW, I added -DdistributionTargetFolder= and still the same failure.

On 5/5/20, 4:29 PM, "Alex Harui"  wrote:

Maybe. I can't find how to do that in the instructions.  I assumed it would 
end up in a "target" folder.

On 5/5/20, 3:09 PM, "Piotr Zarzycki"  wrote:

Shouldn't you add path where distribution will be saved?

On Tue, May 5, 2020, 7:25 PM Alex Harui  
wrote:

> It may be too early in the morning for me, but I switched to the
> release/0.9.7 branch in all 3 repos, did a "mvn clean install" all of 
them,
> then back in royale-asjs I ran
> "mvn -Pwith-distribution clean install" and got an error:
>
> Failed to create assembly: Error adding file to archive:
> 
/Users/aharui/git/royale/maven/royale-asjs/distribution/jars/compiler-mxmljsc/target/compiler-mxmljsc-0.9.7.jar
>
> Interestingly, maybe related, the output on the CI server says things 
like
> " Skipping the assembly in this project because it's not the Execution
> Root" which may be why it gets past this point.  So I think we're 
missing
> something somewhere.  I thought it would be as simple as selecting 
that
> profile.
>
> Thoughts?
> -Alex
>
>

RE: Maven DIstribution

[Yishay Weiss]

I’m close to starting a vote on rc4. I need to know whether or not to hold up 
the release for this. Is this something we need in 0.9.7 or can it wait for 
0.9.8 ?

Thanks.


From: Alex Harui 
Sent: Wednesday, May 6, 2020 2:29:19 AM
To: dev@royale.apache.org 
Subject: Re: Maven DIstribution

Maybe. I can't find how to do that in the instructions.  I assumed it would end 
up in a "target" folder.

On 5/5/20, 3:09 PM, "Piotr Zarzycki"  wrote:

Shouldn't you add path where distribution will be saved?

On Tue, May 5, 2020, 7:25 PM Alex Harui  wrote:

> It may be too early in the morning for me, but I switched to the
> release/0.9.7 branch in all 3 repos, did a "mvn clean install" all of 
them,
> then back in royale-asjs I ran
> "mvn -Pwith-distribution clean install" and got an error:
>
> Failed to create assembly: Error adding file to archive:
> 
/Users/aharui/git/royale/maven/royale-asjs/distribution/jars/compiler-mxmljsc/target/compiler-mxmljsc-0.9.7.jar
>
> Interestingly, maybe related, the output on the CI server says things like
> " Skipping the assembly in this project because it's not the Execution
> Root" which may be why it gets past this point.  So I think we're missing
> something somewhere.  I thought it would be as simple as selecting that
> profile.
>
> Thoughts?
> -Alex
>
>

Re: Maven DIstribution

[Alex Harui]

Maybe. I can't find how to do that in the instructions.  I assumed it would end 
up in a "target" folder.

On 5/5/20, 3:09 PM, "Piotr Zarzycki"  wrote:

Shouldn't you add path where distribution will be saved?

On Tue, May 5, 2020, 7:25 PM Alex Harui  wrote:

> It may be too early in the morning for me, but I switched to the
> release/0.9.7 branch in all 3 repos, did a "mvn clean install" all of 
them,
> then back in royale-asjs I ran
> "mvn -Pwith-distribution clean install" and got an error:
>
> Failed to create assembly: Error adding file to archive:
> 
/Users/aharui/git/royale/maven/royale-asjs/distribution/jars/compiler-mxmljsc/target/compiler-mxmljsc-0.9.7.jar
>
> Interestingly, maybe related, the output on the CI server says things like
> " Skipping the assembly in this project because it's not the Execution
> Root" which may be why it gets past this point.  So I think we're missing
> something somewhere.  I thought it would be as simple as selecting that
> profile.
>
> Thoughts?
> -Alex
>
>

Re: Maven DIstribution

[Piotr Zarzycki]

Shouldn't you add path where distribution will be saved?

On Tue, May 5, 2020, 7:25 PM Alex Harui  wrote:

> It may be too early in the morning for me, but I switched to the
> release/0.9.7 branch in all 3 repos, did a "mvn clean install" all of them,
> then back in royale-asjs I ran
> "mvn -Pwith-distribution clean install" and got an error:
>
> Failed to create assembly: Error adding file to archive:
> /Users/aharui/git/royale/maven/royale-asjs/distribution/jars/compiler-mxmljsc/target/compiler-mxmljsc-0.9.7.jar
>
> Interestingly, maybe related, the output on the CI server says things like
> " Skipping the assembly in this project because it's not the Execution
> Root" which may be why it gets past this point.  So I think we're missing
> something somewhere.  I thought it would be as simple as selecting that
> profile.
>
> Thoughts?
> -Alex
>
>

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi Piotr,

I had configured SDK in File -> Settings -> Default SDK
Then with your email I tried to configure in the project (that was
emptied). I need to reload Moonshine since it removed options to build.
After reload, I tried to compile but results are the same

Josh told me just now the ${royalelib} token should be populated
automatically.
don't need to configure anything in Moonshine.

Asked to check that the file exists in the Maven distribution:

frameworks/themes/JewelTheme/src/main/resources/defaults.css

I check and the file is there.

So don't see for now issues in Maven distribution. Hope you can track with
Moonshine team

Thanks





El jue., 26 mar. 2020 a las 19:26, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Carlos,
>
> One question to Moonshine. Where do you have configured your SDK. In menu
> File -> Settings -> Default SDK or in right click on the project Settings
> -> Build Options ?
>
> It shouldn't be any difference but I just wanted to know.
>
> Thanks,
> Piotr
>
> czw., 26 mar 2020 o 19:21 Christofer Dutz 
> napisał(a):
>
> > Hi all,
> >
> > well it's probably easy to fix if someone tells me what the difference
> is.
> >
> > Chris
> >
> >
> > Am 26.03.20, 19:15 schrieb "Piotr Zarzycki"  >:
> >
> > Hi Carlos,
> >
> > No you don't need to configure anything in Moonshine TDJ project, it
> > should
> > build with SDK right away - Remember I didn't try Maven SDK
> > distribution
> > with TDJ - I did try only with hello world, so your problem indicates
> > that
> > there is something which is missing.
> >
> > ${royalelib} -> This should be filled automatically by I'm not sure
> > Language server ? Maybe Josh can shed some light I don't remember who
> > filled that part, for sure not Moonshine itself. I do remember there
> > were
> > discussion about that variable on mailing list. :)
> >
> > Thanks,
> > Piotr
> >
> > czw., 26 mar 2020 o 19:09 Carlos Rovira 
> > napisał(a):
> >
> > > Hi Chris,
> > >
> > > not sure is a problem of the Maven sdk since the same is working in
> > VSCode
> > >
> > > The offending line is:
> > >
> > > The error is: command line Error: unable to open
> > > '/themes/JewelTheme/src/main/resources/defaults.css'.
> > >
> > > The config in Moonshine is in TourDejewel.as3proj has this:
> > >
> > >  > >
> > >
> >
> additional="-theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > > -html-template=src/main/resources/jewel-example-index-template.html
> > > -js-dynamic-access-unknown-members=true"/>
> > >
> > > So don't know how ${royalelib} is worked in Moonshine. Maybe is
> > something I
> > > don't have configured yet in Moonshine
> > >
> > > @Piotr, could you let me know if is something that I need to
> > configure? can
> > > you try to compile TDJ with Moonshine and the maven distribution
> too?
> > >
> > > The full output for the record is:
> > >
> > >
> > > : Compiling TourDeJewel
> > > : Command:
> > > "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/bin/mxmlc"
> > > -load-config+=obj/TourDeJewelConfig.xml -optimize=false
> > >
> -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > > -html-template=src/main/resources/jewel-example-index-template.html
> > > -js-dynamic-access-unknown-members=true -debug=true -o
> > bin-debug/App.swf
> > > : SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > > : Sending to mxmlc: export
> > >
> >
> ROYALE_HOME=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven;export
> > > SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en"; export
> > >
> > >
> >
> ROYALE_SWF_COMPILER_HOME=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven&&
> > >
> > "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> > > -load-config+=obj/TourDeJewelConfig.xml -optimize=false
> > >
> -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > > -html-template=src/main/resources/jewel-example-index-template.html
> > > -js-dynamic-access-unknown-members=true -debug=true -o
> > bin-debug/App.swf
> > > -compiler.targets=SWF
> > > : Using Royale Compiler codebase:
> > >
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/../..
> > > : Using Royale SDK:
> > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > > : MXMLJSC
> > > :
> > >
> > >
> >
> +royalelib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks
> > > :
> > >
> > >
> >
> -sdk-js-lib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks/js/Royale/generated-sources
> > > : -load-config+=obj/TourDeJewelConfig.xml
> > > : -optimize=false
> > > : -theme=/themes/JewelTheme/src/main/resources/defaults.css
> > > :
> 

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

Carlos,

One question to Moonshine. Where do you have configured your SDK. In menu
File -> Settings -> Default SDK or in right click on the project Settings
-> Build Options ?

It shouldn't be any difference but I just wanted to know.

Thanks,
Piotr

czw., 26 mar 2020 o 19:21 Christofer Dutz 
napisał(a):

> Hi all,
>
> well it's probably easy to fix if someone tells me what the difference is.
>
> Chris
>
>
> Am 26.03.20, 19:15 schrieb "Piotr Zarzycki" :
>
> Hi Carlos,
>
> No you don't need to configure anything in Moonshine TDJ project, it
> should
> build with SDK right away - Remember I didn't try Maven SDK
> distribution
> with TDJ - I did try only with hello world, so your problem indicates
> that
> there is something which is missing.
>
> ${royalelib} -> This should be filled automatically by I'm not sure
> Language server ? Maybe Josh can shed some light I don't remember who
> filled that part, for sure not Moonshine itself. I do remember there
> were
> discussion about that variable on mailing list. :)
>
> Thanks,
> Piotr
>
> czw., 26 mar 2020 o 19:09 Carlos Rovira 
> napisał(a):
>
> > Hi Chris,
> >
> > not sure is a problem of the Maven sdk since the same is working in
> VSCode
> >
> > The offending line is:
> >
> > The error is: command line Error: unable to open
> > '/themes/JewelTheme/src/main/resources/defaults.css'.
> >
> > The config in Moonshine is in TourDejewel.as3proj has this:
> >
> >  >
> >
> additional="-theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > -html-template=src/main/resources/jewel-example-index-template.html
> > -js-dynamic-access-unknown-members=true"/>
> >
> > So don't know how ${royalelib} is worked in Moonshine. Maybe is
> something I
> > don't have configured yet in Moonshine
> >
> > @Piotr, could you let me know if is something that I need to
> configure? can
> > you try to compile TDJ with Moonshine and the maven distribution too?
> >
> > The full output for the record is:
> >
> >
> > : Compiling TourDeJewel
> > : Command:
> > "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/bin/mxmlc"
> > -load-config+=obj/TourDeJewelConfig.xml -optimize=false
> > -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > -html-template=src/main/resources/jewel-example-index-template.html
> > -js-dynamic-access-unknown-members=true -debug=true -o
> bin-debug/App.swf
> > : SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > : Sending to mxmlc: export
> >
> ROYALE_HOME=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven;export
> > SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en"; export
> >
> >
> ROYALE_SWF_COMPILER_HOME=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven&&
> >
> "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> > -load-config+=obj/TourDeJewelConfig.xml -optimize=false
> > -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > -html-template=src/main/resources/jewel-example-index-template.html
> > -js-dynamic-access-unknown-members=true -debug=true -o
> bin-debug/App.swf
> > -compiler.targets=SWF
> > : Using Royale Compiler codebase:
> > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/../..
> > : Using Royale SDK:
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > : MXMLJSC
> > :
> >
> >
> +royalelib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks
> > :
> >
> >
> -sdk-js-lib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks/js/Royale/generated-sources
> > : -load-config+=obj/TourDeJewelConfig.xml
> > : -optimize=false
> > : -theme=/themes/JewelTheme/src/main/resources/defaults.css
> > : -html-template=src/main/resources/jewel-example-index-template.html
> > : -js-dynamic-access-unknown-members=true
> > : -debug=true
> > : -o
> > : bin-debug/App.swf
> > : -compiler.targets=SWF
> > : command line Error: unable to open
> > '/themes/JewelTheme/src/main/resources/defaults.css'.
> > : 0.676110556 seconds
> > : Compilation of TourDeJewel finished.
> >
> >
> > El jue., 26 mar. 2020 a las 18:20, Christofer Dutz (<
> > christofer.d...@c-ware.de>) escribió:
> >
> > > Hi all,
> > >
> > > Good to know it's now working.
> > >
> > > So what is still the difference between the Maven and the Ant
> > distribution?
> > >
> > > I'm asking cause I would love to make the maven distribution match
> the
> > Ant
> > > version and just use the one Maven created in the future.
> > >
> > > Chris
> > >
> > >
> > > Am 26.03.20, 17:58 schrieb "Carlos Rovira" <
> carlosrov...@apache.org>:
> > >
> > > Hi Piotr,
> 

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Ok,
hope Josh could let us know what could be missing and why VSCode is able to
get it. Probably will be more efficient than try to see ourselves.
Thanks!

El jue., 26 mar. 2020 a las 19:15, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Carlos,
>
> No you don't need to configure anything in Moonshine TDJ project, it should
> build with SDK right away - Remember I didn't try Maven SDK distribution
> with TDJ - I did try only with hello world, so your problem indicates that
> there is something which is missing.
>
> ${royalelib} -> This should be filled automatically by I'm not sure
> Language server ? Maybe Josh can shed some light I don't remember who
> filled that part, for sure not Moonshine itself. I do remember there were
> discussion about that variable on mailing list. :)
>
> Thanks,
> Piotr
>
> czw., 26 mar 2020 o 19:09 Carlos Rovira 
> napisał(a):
>
> > Hi Chris,
> >
> > not sure is a problem of the Maven sdk since the same is working in
> VSCode
> >
> > The offending line is:
> >
> > The error is: command line Error: unable to open
> > '/themes/JewelTheme/src/main/resources/defaults.css'.
> >
> > The config in Moonshine is in TourDejewel.as3proj has this:
> >
> >  >
> >
> additional="-theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > -html-template=src/main/resources/jewel-example-index-template.html
> > -js-dynamic-access-unknown-members=true"/>
> >
> > So don't know how ${royalelib} is worked in Moonshine. Maybe is
> something I
> > don't have configured yet in Moonshine
> >
> > @Piotr, could you let me know if is something that I need to configure?
> can
> > you try to compile TDJ with Moonshine and the maven distribution too?
> >
> > The full output for the record is:
> >
> >
> > : Compiling TourDeJewel
> > : Command:
> > "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/bin/mxmlc"
> > -load-config+=obj/TourDeJewelConfig.xml -optimize=false
> > -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > -html-template=src/main/resources/jewel-example-index-template.html
> > -js-dynamic-access-unknown-members=true -debug=true -o bin-debug/App.swf
> > : SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > : Sending to mxmlc: export
> >
> ROYALE_HOME=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven;export
> > SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en"; export
> >
> >
> ROYALE_SWF_COMPILER_HOME=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven&&
> > "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> > -load-config+=obj/TourDeJewelConfig.xml -optimize=false
> > -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > -html-template=src/main/resources/jewel-example-index-template.html
> > -js-dynamic-access-unknown-members=true -debug=true -o bin-debug/App.swf
> > -compiler.targets=SWF
> > : Using Royale Compiler codebase:
> > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/../..
> > : Using Royale SDK:
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > : MXMLJSC
> > :
> >
> >
> +royalelib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks
> > :
> >
> >
> -sdk-js-lib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks/js/Royale/generated-sources
> > : -load-config+=obj/TourDeJewelConfig.xml
> > : -optimize=false
> > : -theme=/themes/JewelTheme/src/main/resources/defaults.css
> > : -html-template=src/main/resources/jewel-example-index-template.html
> > : -js-dynamic-access-unknown-members=true
> > : -debug=true
> > : -o
> > : bin-debug/App.swf
> > : -compiler.targets=SWF
> > : command line Error: unable to open
> > '/themes/JewelTheme/src/main/resources/defaults.css'.
> > : 0.676110556 seconds
> > : Compilation of TourDeJewel finished.
> >
> >
> > El jue., 26 mar. 2020 a las 18:20, Christofer Dutz (<
> > christofer.d...@c-ware.de>) escribió:
> >
> > > Hi all,
> > >
> > > Good to know it's now working.
> > >
> > > So what is still the difference between the Maven and the Ant
> > distribution?
> > >
> > > I'm asking cause I would love to make the maven distribution match the
> > Ant
> > > version and just use the one Maven created in the future.
> > >
> > > Chris
> > >
> > >
> > > Am 26.03.20, 17:58 schrieb "Carlos Rovira" :
> > >
> > > Hi Piotr,
> > >
> > > just downloaded latest nightly and could finally compile the TDJ.
> > > Is failing due to some config issue, but that's an issue to solve
> in
> > > TDJ
> > > config
> > > Congrats y think I can at last use Moonshine and explore it! :)
> > >
> > >
> > >
> > > El jue., 26 mar. 2020 a las 12:44, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Carlos,
> > > >
> > > > Colleague from the Team was able to reproduce your problem with
> > > "Build
> > > > Project". It looks like he fixed that - you can download Nightly
> > > Build of
> > > > Moonshine and check.
> > > >
> > > 

Re: Maven Distribution SDK fixed and working for IDEs

[Christofer Dutz]

Hi all,

well it's probably easy to fix if someone tells me what the difference is.

Chris


Am 26.03.20, 19:15 schrieb "Piotr Zarzycki" :

Hi Carlos,

No you don't need to configure anything in Moonshine TDJ project, it should
build with SDK right away - Remember I didn't try Maven SDK distribution
with TDJ - I did try only with hello world, so your problem indicates that
there is something which is missing.

${royalelib} -> This should be filled automatically by I'm not sure
Language server ? Maybe Josh can shed some light I don't remember who
filled that part, for sure not Moonshine itself. I do remember there were
discussion about that variable on mailing list. :)

Thanks,
Piotr

czw., 26 mar 2020 o 19:09 Carlos Rovira 
napisał(a):

> Hi Chris,
>
> not sure is a problem of the Maven sdk since the same is working in VSCode
>
> The offending line is:
>
> The error is: command line Error: unable to open
> '/themes/JewelTheme/src/main/resources/defaults.css'.
>
> The config in Moonshine is in TourDejewel.as3proj has this:
>
> 
> 
additional="-theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> -html-template=src/main/resources/jewel-example-index-template.html
> -js-dynamic-access-unknown-members=true"/>
>
> So don't know how ${royalelib} is worked in Moonshine. Maybe is something 
I
> don't have configured yet in Moonshine
>
> @Piotr, could you let me know if is something that I need to configure? 
can
> you try to compile TDJ with Moonshine and the maven distribution too?
>
> The full output for the record is:
>
>
> : Compiling TourDeJewel
> : Command:
> "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/bin/mxmlc"
> -load-config+=obj/TourDeJewelConfig.xml -optimize=false
> -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> -html-template=src/main/resources/jewel-example-index-template.html
> -js-dynamic-access-unknown-members=true -debug=true -o bin-debug/App.swf
> : SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> : Sending to mxmlc: export
> ROYALE_HOME=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven;export
> SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en"; export
>
> 
ROYALE_SWF_COMPILER_HOME=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven&&
> "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> -load-config+=obj/TourDeJewelConfig.xml -optimize=false
> -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> -html-template=src/main/resources/jewel-example-index-template.html
> -js-dynamic-access-unknown-members=true -debug=true -o bin-debug/App.swf
> -compiler.targets=SWF
> : Using Royale Compiler codebase:
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/../..
> : Using Royale SDK: 
/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> : MXMLJSC
> :
>
> 
+royalelib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks
> :
>
> 
-sdk-js-lib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks/js/Royale/generated-sources
> : -load-config+=obj/TourDeJewelConfig.xml
> : -optimize=false
> : -theme=/themes/JewelTheme/src/main/resources/defaults.css
> : -html-template=src/main/resources/jewel-example-index-template.html
> : -js-dynamic-access-unknown-members=true
> : -debug=true
> : -o
> : bin-debug/App.swf
> : -compiler.targets=SWF
> : command line Error: unable to open
> '/themes/JewelTheme/src/main/resources/defaults.css'.
> : 0.676110556 seconds
> : Compilation of TourDeJewel finished.
>
>
> El jue., 26 mar. 2020 a las 18:20, Christofer Dutz (<
> christofer.d...@c-ware.de>) escribió:
>
> > Hi all,
> >
> > Good to know it's now working.
> >
> > So what is still the difference between the Maven and the Ant
> distribution?
> >
> > I'm asking cause I would love to make the maven distribution match the
> Ant
> > version and just use the one Maven created in the future.
> >
> > Chris
> >
> >
> > Am 26.03.20, 17:58 schrieb "Carlos Rovira" :
> >
> > Hi Piotr,
> >
> > just downloaded latest nightly and could finally compile the TDJ.
> > Is failing due to some config issue, but that's an issue to solve in
> > TDJ
> > config
> > Congrats y think I can at last use Moonshine and explore it! :)
> >
> >
> >
> > El jue., 26 mar. 2020 a las 12:44, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Hi Carlos,
> > >
> > > Colleague from the Team was able to reproduce your problem with
> > "Build
> > > 

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

Hi Carlos,

No you don't need to configure anything in Moonshine TDJ project, it should
build with SDK right away - Remember I didn't try Maven SDK distribution
with TDJ - I did try only with hello world, so your problem indicates that
there is something which is missing.

${royalelib} -> This should be filled automatically by I'm not sure
Language server ? Maybe Josh can shed some light I don't remember who
filled that part, for sure not Moonshine itself. I do remember there were
discussion about that variable on mailing list. :)

Thanks,
Piotr

czw., 26 mar 2020 o 19:09 Carlos Rovira 
napisał(a):

> Hi Chris,
>
> not sure is a problem of the Maven sdk since the same is working in VSCode
>
> The offending line is:
>
> The error is: command line Error: unable to open
> '/themes/JewelTheme/src/main/resources/defaults.css'.
>
> The config in Moonshine is in TourDejewel.as3proj has this:
>
> 
> additional="-theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> -html-template=src/main/resources/jewel-example-index-template.html
> -js-dynamic-access-unknown-members=true"/>
>
> So don't know how ${royalelib} is worked in Moonshine. Maybe is something I
> don't have configured yet in Moonshine
>
> @Piotr, could you let me know if is something that I need to configure? can
> you try to compile TDJ with Moonshine and the maven distribution too?
>
> The full output for the record is:
>
>
> : Compiling TourDeJewel
> : Command:
> "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/bin/mxmlc"
> -load-config+=obj/TourDeJewelConfig.xml -optimize=false
> -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> -html-template=src/main/resources/jewel-example-index-template.html
> -js-dynamic-access-unknown-members=true -debug=true -o bin-debug/App.swf
> : SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> : Sending to mxmlc: export
> ROYALE_HOME=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven;export
> SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en"; export
>
> ROYALE_SWF_COMPILER_HOME=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven&&
> "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> -load-config+=obj/TourDeJewelConfig.xml -optimize=false
> -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> -html-template=src/main/resources/jewel-example-index-template.html
> -js-dynamic-access-unknown-members=true -debug=true -o bin-debug/App.swf
> -compiler.targets=SWF
> : Using Royale Compiler codebase:
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/../..
> : Using Royale SDK: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> : MXMLJSC
> :
>
> +royalelib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks
> :
>
> -sdk-js-lib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks/js/Royale/generated-sources
> : -load-config+=obj/TourDeJewelConfig.xml
> : -optimize=false
> : -theme=/themes/JewelTheme/src/main/resources/defaults.css
> : -html-template=src/main/resources/jewel-example-index-template.html
> : -js-dynamic-access-unknown-members=true
> : -debug=true
> : -o
> : bin-debug/App.swf
> : -compiler.targets=SWF
> : command line Error: unable to open
> '/themes/JewelTheme/src/main/resources/defaults.css'.
> : 0.676110556 seconds
> : Compilation of TourDeJewel finished.
>
>
> El jue., 26 mar. 2020 a las 18:20, Christofer Dutz (<
> christofer.d...@c-ware.de>) escribió:
>
> > Hi all,
> >
> > Good to know it's now working.
> >
> > So what is still the difference between the Maven and the Ant
> distribution?
> >
> > I'm asking cause I would love to make the maven distribution match the
> Ant
> > version and just use the one Maven created in the future.
> >
> > Chris
> >
> >
> > Am 26.03.20, 17:58 schrieb "Carlos Rovira" :
> >
> > Hi Piotr,
> >
> > just downloaded latest nightly and could finally compile the TDJ.
> > Is failing due to some config issue, but that's an issue to solve in
> > TDJ
> > config
> > Congrats y think I can at last use Moonshine and explore it! :)
> >
> >
> >
> > El jue., 26 mar. 2020 a las 12:44, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Hi Carlos,
> > >
> > > Colleague from the Team was able to reproduce your problem with
> > "Build
> > > Project". It looks like he fixed that - you can download Nightly
> > Build of
> > > Moonshine and check.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > pon., 23 mar 2020 o 15:10 Carlos Rovira 
> > > napisał(a):
> > >
> > > > Yeah, hope someone on your team could know where we can start
> > looking :)
> > > > thanks!
> > > > Carlos
> > > >
> > > > El lun., 23 mar. 2020 a las 15:04, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > > > Next is reproduce your problem with Moonshine. ;)
> > > > >
> > > > > pon., 23 mar 2020 o 15:02 Carlos Rovira <

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi Chris,

not sure is a problem of the Maven sdk since the same is working in VSCode

The offending line is:

The error is: command line Error: unable to open
'/themes/JewelTheme/src/main/resources/defaults.css'.

The config in Moonshine is in TourDejewel.as3proj has this:



So don't know how ${royalelib} is worked in Moonshine. Maybe is something I
don't have configured yet in Moonshine

@Piotr, could you let me know if is something that I need to configure? can
you try to compile TDJ with Moonshine and the maven distribution too?

The full output for the record is:


: Compiling TourDeJewel
: Command:
"/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/bin/mxmlc"
-load-config+=obj/TourDeJewelConfig.xml -optimize=false
-theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
-html-template=src/main/resources/jewel-example-index-template.html
-js-dynamic-access-unknown-members=true -debug=true -o bin-debug/App.swf
: SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
: Sending to mxmlc: export
ROYALE_HOME=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven;export
SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en"; export
ROYALE_SWF_COMPILER_HOME=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven&&
"/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
-load-config+=obj/TourDeJewelConfig.xml -optimize=false
-theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
-html-template=src/main/resources/jewel-example-index-template.html
-js-dynamic-access-unknown-members=true -debug=true -o bin-debug/App.swf
-compiler.targets=SWF
: Using Royale Compiler codebase:
/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/../..
: Using Royale SDK: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
: MXMLJSC
:
+royalelib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks
:
-sdk-js-lib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks/js/Royale/generated-sources
: -load-config+=obj/TourDeJewelConfig.xml
: -optimize=false
: -theme=/themes/JewelTheme/src/main/resources/defaults.css
: -html-template=src/main/resources/jewel-example-index-template.html
: -js-dynamic-access-unknown-members=true
: -debug=true
: -o
: bin-debug/App.swf
: -compiler.targets=SWF
: command line Error: unable to open
'/themes/JewelTheme/src/main/resources/defaults.css'.
: 0.676110556 seconds
: Compilation of TourDeJewel finished.


El jue., 26 mar. 2020 a las 18:20, Christofer Dutz (<
christofer.d...@c-ware.de>) escribió:

> Hi all,
>
> Good to know it's now working.
>
> So what is still the difference between the Maven and the Ant distribution?
>
> I'm asking cause I would love to make the maven distribution match the Ant
> version and just use the one Maven created in the future.
>
> Chris
>
>
> Am 26.03.20, 17:58 schrieb "Carlos Rovira" :
>
> Hi Piotr,
>
> just downloaded latest nightly and could finally compile the TDJ.
> Is failing due to some config issue, but that's an issue to solve in
> TDJ
> config
> Congrats y think I can at last use Moonshine and explore it! :)
>
>
>
> El jue., 26 mar. 2020 a las 12:44, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Carlos,
> >
> > Colleague from the Team was able to reproduce your problem with
> "Build
> > Project". It looks like he fixed that - you can download Nightly
> Build of
> > Moonshine and check.
> >
> > Thanks,
> > Piotr
> >
> > pon., 23 mar 2020 o 15:10 Carlos Rovira 
> > napisał(a):
> >
> > > Yeah, hope someone on your team could know where we can start
> looking :)
> > > thanks!
> > > Carlos
> > >
> > > El lun., 23 mar. 2020 a las 15:04, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Next is reproduce your problem with Moonshine. ;)
> > > >
> > > > pon., 23 mar 2020 o 15:02 Carlos Rovira  >
> > > > napisał(a):
> > > >
> > > > > Very cool Piotr!
> > > > > seems we finally has Maven distribution sdk working! :)
> > > > >
> > > > > El lun., 23 mar. 2020 a las 14:44, Piotr Zarzycki (<
> > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > >
> > > > > > Hi Guys,
> > > > > >
> > > > > > I just checked Maven Distribution with Moonshine and I was
> able to
> > > > build
> > > > > > Jewel Hello World and TourDeJewel. :)
> > > > > >
> > > > > > Thanks,
> > > > > > Piotr
> > > > > >
> > > > > > niedz., 22 mar 2020 o 20:58 Carlos Rovira <
> carlosrov...@apache.org
> > >
> > > > > > napisał(a):
> > > > > >
> > > > > > > Hi Piotr,
> > > > > > >
> > > > > > > nothing happens or log is printed in the console, is like
> if I
> > > didn't
> > > > > > push
> > > > > > > the menu button.
> > > > > > > I ensured that I have the SDK setup, maybe something more
> is
> > > needed,
> > > > > and
> > > > > > > 

Re: Maven Distribution SDK fixed and working for IDEs

[Christofer Dutz]

Hi all, 

Good to know it's now working.

So what is still the difference between the Maven and the Ant distribution?

I'm asking cause I would love to make the maven distribution match the Ant 
version and just use the one Maven created in the future.

Chris


Am 26.03.20, 17:58 schrieb "Carlos Rovira" :

Hi Piotr,

just downloaded latest nightly and could finally compile the TDJ.
Is failing due to some config issue, but that's an issue to solve in TDJ
config
Congrats y think I can at last use Moonshine and explore it! :)



El jue., 26 mar. 2020 a las 12:44, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Carlos,
>
> Colleague from the Team was able to reproduce your problem with "Build
> Project". It looks like he fixed that - you can download Nightly Build of
> Moonshine and check.
>
> Thanks,
> Piotr
>
> pon., 23 mar 2020 o 15:10 Carlos Rovira 
> napisał(a):
>
> > Yeah, hope someone on your team could know where we can start looking :)
> > thanks!
> > Carlos
> >
> > El lun., 23 mar. 2020 a las 15:04, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Next is reproduce your problem with Moonshine. ;)
> > >
> > > pon., 23 mar 2020 o 15:02 Carlos Rovira 
> > > napisał(a):
> > >
> > > > Very cool Piotr!
> > > > seems we finally has Maven distribution sdk working! :)
> > > >
> > > > El lun., 23 mar. 2020 a las 14:44, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > > > Hi Guys,
> > > > >
> > > > > I just checked Maven Distribution with Moonshine and I was able to
> > > build
> > > > > Jewel Hello World and TourDeJewel. :)
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > niedz., 22 mar 2020 o 20:58 Carlos Rovira  >
> > > > > napisał(a):
> > > > >
> > > > > > Hi Piotr,
> > > > > >
> > > > > > nothing happens or log is printed in the console, is like if I
> > didn't
> > > > > push
> > > > > > the menu button.
> > > > > > I ensured that I have the SDK setup, maybe something more is
> > needed,
> > > > and
> > > > > > I'm missing something.
> > > > > > As well I understand that "Project > Build Project" is the right
> > > option
> > > > > in
> > > > > > the menu to push
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > El dom., 22 mar. 2020 a las 17:55, Piotr Zarzycki (<
> > > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > > >
> > > > > > > Carlos,
> > > > > > >
> > > > > > > By saying that nothing happens - you don't get any information
> on
> > > the
> > > > > > > console at all?
> > > > > > >
> > > > > > > On Sun, Mar 22, 2020, 5:34 PM Carlos Rovira <
> > > carlosrov...@apache.org
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Chris and Piotr,
> > > > > > > >
> > > > > > > > I was having the same issue. After latest PR from Chris, I
> can
> > > > > confirm
> > > > > > is
> > > > > > > > working ok :)
> > > > > > > > Piotr, please, a last attempt. I think you'll get working
> right
> > > now
> > > > > > from
> > > > > > > > Moonshine.
> > > > > > > >
> > > > > > > > As well I'm curious about how to build with IDE in 
Moonshine,
> > or
> > > > why
> > > > > > > >  Project > Build Project is not working for me
> > > > > > > > something I must have into account?
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > > Carlos
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > El dom., 22 mar. 2020 a las 17:04, Christofer Dutz (<
> > > > > > > > christofer.d...@c-ware.de>) escribió:
> > > > > > > >
> > > > > > > > > Yeah ... sorry for that.
> > > > > > > > >
> > > > > > > > > I noticed that I took care of the "SNAPSHOT" instead of 
the
> > > > > > Timestamp,
> > > > > > > > but
> > > > > > > > > I forgot to add the classifier ... will be in the next PR.
> > > > > > > > > Can you confirm that now the files have a "SNAPSHOT"
> instead
> > of
> > > > the
> > > > > > > > > Timestamp?
> > > > > > > > >
> > > > > > > > > Chris
> > > > > > > > >
> > > > > > > > > Am 22.03.20, 15:56 schrieb "Piotr Zarzycki" <
> > > > > > > piotrzarzyck...@gmail.com
> > > > > > > > >:
> > > > > > > > >
> > > > > > > > > Hi Chris,
> > > > > > > > >
> > > > > > > > > Nothing changed I have exactly same issue after 
pulling
> > all
> > > > > > changes
> > > > > > > > and
> > > > > > > > > rebuilding sdk.
> > > > > > > > >
> > > > > > > > > niedz., 22 mar 2020 o 12:15 Carlos Rovira <
> > > > > > carlosrov...@apache.org
> > > > > > > >
  

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi Piotr,

just downloaded latest nightly and could finally compile the TDJ.
Is failing due to some config issue, but that's an issue to solve in TDJ
config
Congrats y think I can at last use Moonshine and explore it! :)



El jue., 26 mar. 2020 a las 12:44, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Carlos,
>
> Colleague from the Team was able to reproduce your problem with "Build
> Project". It looks like he fixed that - you can download Nightly Build of
> Moonshine and check.
>
> Thanks,
> Piotr
>
> pon., 23 mar 2020 o 15:10 Carlos Rovira 
> napisał(a):
>
> > Yeah, hope someone on your team could know where we can start looking :)
> > thanks!
> > Carlos
> >
> > El lun., 23 mar. 2020 a las 15:04, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Next is reproduce your problem with Moonshine. ;)
> > >
> > > pon., 23 mar 2020 o 15:02 Carlos Rovira 
> > > napisał(a):
> > >
> > > > Very cool Piotr!
> > > > seems we finally has Maven distribution sdk working! :)
> > > >
> > > > El lun., 23 mar. 2020 a las 14:44, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > > > Hi Guys,
> > > > >
> > > > > I just checked Maven Distribution with Moonshine and I was able to
> > > build
> > > > > Jewel Hello World and TourDeJewel. :)
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > niedz., 22 mar 2020 o 20:58 Carlos Rovira  >
> > > > > napisał(a):
> > > > >
> > > > > > Hi Piotr,
> > > > > >
> > > > > > nothing happens or log is printed in the console, is like if I
> > didn't
> > > > > push
> > > > > > the menu button.
> > > > > > I ensured that I have the SDK setup, maybe something more is
> > needed,
> > > > and
> > > > > > I'm missing something.
> > > > > > As well I understand that "Project > Build Project" is the right
> > > option
> > > > > in
> > > > > > the menu to push
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > El dom., 22 mar. 2020 a las 17:55, Piotr Zarzycki (<
> > > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > > >
> > > > > > > Carlos,
> > > > > > >
> > > > > > > By saying that nothing happens - you don't get any information
> on
> > > the
> > > > > > > console at all?
> > > > > > >
> > > > > > > On Sun, Mar 22, 2020, 5:34 PM Carlos Rovira <
> > > carlosrov...@apache.org
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Chris and Piotr,
> > > > > > > >
> > > > > > > > I was having the same issue. After latest PR from Chris, I
> can
> > > > > confirm
> > > > > > is
> > > > > > > > working ok :)
> > > > > > > > Piotr, please, a last attempt. I think you'll get working
> right
> > > now
> > > > > > from
> > > > > > > > Moonshine.
> > > > > > > >
> > > > > > > > As well I'm curious about how to build with IDE in Moonshine,
> > or
> > > > why
> > > > > > > >  Project > Build Project is not working for me
> > > > > > > > something I must have into account?
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > > Carlos
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > El dom., 22 mar. 2020 a las 17:04, Christofer Dutz (<
> > > > > > > > christofer.d...@c-ware.de>) escribió:
> > > > > > > >
> > > > > > > > > Yeah ... sorry for that.
> > > > > > > > >
> > > > > > > > > I noticed that I took care of the "SNAPSHOT" instead of the
> > > > > > Timestamp,
> > > > > > > > but
> > > > > > > > > I forgot to add the classifier ... will be in the next PR.
> > > > > > > > > Can you confirm that now the files have a "SNAPSHOT"
> instead
> > of
> > > > the
> > > > > > > > > Timestamp?
> > > > > > > > >
> > > > > > > > > Chris
> > > > > > > > >
> > > > > > > > > Am 22.03.20, 15:56 schrieb "Piotr Zarzycki" <
> > > > > > > piotrzarzyck...@gmail.com
> > > > > > > > >:
> > > > > > > > >
> > > > > > > > > Hi Chris,
> > > > > > > > >
> > > > > > > > > Nothing changed I have exactly same issue after pulling
> > all
> > > > > > changes
> > > > > > > > and
> > > > > > > > > rebuilding sdk.
> > > > > > > > >
> > > > > > > > > niedz., 22 mar 2020 o 12:15 Carlos Rovira <
> > > > > > carlosrov...@apache.org
> > > > > > > >
> > > > > > > > > napisał(a):
> > > > > > > > >
> > > > > > > > > > Hi,
> > > > > > > > > >
> > > > > > > > > > Many thanks for the fix Chris.
> > > > > > > > > > Piotr, can you try again and confirm if all is ok
> now?
> > > > > > > > > >
> > > > > > > > > > thanks
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > El dom., 22 mar. 2020 a las 11:47, Christofer Dutz (<
> > > > > > > > > > christofer.d...@c-ware.de>) escribió:
> > > > > > > > > >
> > > > > > > > > > > Hi Piotr,
> > > > > > > > > > >
> > > > > > > > > > > I had a look and you are right ... even if this
> only
> > > > seems
> > > > > to
> > > > > > > > > happen if
> > > > > > > > > > > you haven't built the typedefs on your machine that
> > day
> > > > > > before
> > > > > > > > > building
> > > > > > > > > > 

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

Hi Carlos,

Colleague from the Team was able to reproduce your problem with "Build
Project". It looks like he fixed that - you can download Nightly Build of
Moonshine and check.

Thanks,
Piotr

pon., 23 mar 2020 o 15:10 Carlos Rovira 
napisał(a):

> Yeah, hope someone on your team could know where we can start looking :)
> thanks!
> Carlos
>
> El lun., 23 mar. 2020 a las 15:04, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Next is reproduce your problem with Moonshine. ;)
> >
> > pon., 23 mar 2020 o 15:02 Carlos Rovira 
> > napisał(a):
> >
> > > Very cool Piotr!
> > > seems we finally has Maven distribution sdk working! :)
> > >
> > > El lun., 23 mar. 2020 a las 14:44, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Guys,
> > > >
> > > > I just checked Maven Distribution with Moonshine and I was able to
> > build
> > > > Jewel Hello World and TourDeJewel. :)
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > niedz., 22 mar 2020 o 20:58 Carlos Rovira 
> > > > napisał(a):
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > nothing happens or log is printed in the console, is like if I
> didn't
> > > > push
> > > > > the menu button.
> > > > > I ensured that I have the SDK setup, maybe something more is
> needed,
> > > and
> > > > > I'm missing something.
> > > > > As well I understand that "Project > Build Project" is the right
> > option
> > > > in
> > > > > the menu to push
> > > > >
> > > > > Thanks
> > > > >
> > > > > El dom., 22 mar. 2020 a las 17:55, Piotr Zarzycki (<
> > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > >
> > > > > > Carlos,
> > > > > >
> > > > > > By saying that nothing happens - you don't get any information on
> > the
> > > > > > console at all?
> > > > > >
> > > > > > On Sun, Mar 22, 2020, 5:34 PM Carlos Rovira <
> > carlosrov...@apache.org
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Chris and Piotr,
> > > > > > >
> > > > > > > I was having the same issue. After latest PR from Chris, I can
> > > > confirm
> > > > > is
> > > > > > > working ok :)
> > > > > > > Piotr, please, a last attempt. I think you'll get working right
> > now
> > > > > from
> > > > > > > Moonshine.
> > > > > > >
> > > > > > > As well I'm curious about how to build with IDE in Moonshine,
> or
> > > why
> > > > > > >  Project > Build Project is not working for me
> > > > > > > something I must have into account?
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > Carlos
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > El dom., 22 mar. 2020 a las 17:04, Christofer Dutz (<
> > > > > > > christofer.d...@c-ware.de>) escribió:
> > > > > > >
> > > > > > > > Yeah ... sorry for that.
> > > > > > > >
> > > > > > > > I noticed that I took care of the "SNAPSHOT" instead of the
> > > > > Timestamp,
> > > > > > > but
> > > > > > > > I forgot to add the classifier ... will be in the next PR.
> > > > > > > > Can you confirm that now the files have a "SNAPSHOT" instead
> of
> > > the
> > > > > > > > Timestamp?
> > > > > > > >
> > > > > > > > Chris
> > > > > > > >
> > > > > > > > Am 22.03.20, 15:56 schrieb "Piotr Zarzycki" <
> > > > > > piotrzarzyck...@gmail.com
> > > > > > > >:
> > > > > > > >
> > > > > > > > Hi Chris,
> > > > > > > >
> > > > > > > > Nothing changed I have exactly same issue after pulling
> all
> > > > > changes
> > > > > > > and
> > > > > > > > rebuilding sdk.
> > > > > > > >
> > > > > > > > niedz., 22 mar 2020 o 12:15 Carlos Rovira <
> > > > > carlosrov...@apache.org
> > > > > > >
> > > > > > > > napisał(a):
> > > > > > > >
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > Many thanks for the fix Chris.
> > > > > > > > > Piotr, can you try again and confirm if all is ok now?
> > > > > > > > >
> > > > > > > > > thanks
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > El dom., 22 mar. 2020 a las 11:47, Christofer Dutz (<
> > > > > > > > > christofer.d...@c-ware.de>) escribió:
> > > > > > > > >
> > > > > > > > > > Hi Piotr,
> > > > > > > > > >
> > > > > > > > > > I had a look and you are right ... even if this only
> > > seems
> > > > to
> > > > > > > > happen if
> > > > > > > > > > you haven't built the typedefs on your machine that
> day
> > > > > before
> > > > > > > > building
> > > > > > > > > the
> > > > > > > > > > distribution. I just pushed a PR that should fix
> this.
> > > > > > > > > >
> > > > > > > > > > Chris
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Am 22.03.20, 10:59 schrieb "Piotr Zarzycki" <
> > > > > > > > piotrzarzyck...@gmail.com
> > > > > > > > > >:
> > > > > > > > > >
> > > > > > > > > > Hi Carlos,
> > > > > > > > > >
> > > > > > > > > > I've just build royale-asjs with following
> command:
> > > > > > > > > >
> > > > > > > > > > mvn clean install -P
> > > > > > > with-distribution,option-with-sass-compile
> > > 

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Yeah, hope someone on your team could know where we can start looking :)
thanks!
Carlos

El lun., 23 mar. 2020 a las 15:04, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Next is reproduce your problem with Moonshine. ;)
>
> pon., 23 mar 2020 o 15:02 Carlos Rovira 
> napisał(a):
>
> > Very cool Piotr!
> > seems we finally has Maven distribution sdk working! :)
> >
> > El lun., 23 mar. 2020 a las 14:44, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Hi Guys,
> > >
> > > I just checked Maven Distribution with Moonshine and I was able to
> build
> > > Jewel Hello World and TourDeJewel. :)
> > >
> > > Thanks,
> > > Piotr
> > >
> > > niedz., 22 mar 2020 o 20:58 Carlos Rovira 
> > > napisał(a):
> > >
> > > > Hi Piotr,
> > > >
> > > > nothing happens or log is printed in the console, is like if I didn't
> > > push
> > > > the menu button.
> > > > I ensured that I have the SDK setup, maybe something more is needed,
> > and
> > > > I'm missing something.
> > > > As well I understand that "Project > Build Project" is the right
> option
> > > in
> > > > the menu to push
> > > >
> > > > Thanks
> > > >
> > > > El dom., 22 mar. 2020 a las 17:55, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > > > Carlos,
> > > > >
> > > > > By saying that nothing happens - you don't get any information on
> the
> > > > > console at all?
> > > > >
> > > > > On Sun, Mar 22, 2020, 5:34 PM Carlos Rovira <
> carlosrov...@apache.org
> > >
> > > > > wrote:
> > > > >
> > > > > > Hi Chris and Piotr,
> > > > > >
> > > > > > I was having the same issue. After latest PR from Chris, I can
> > > confirm
> > > > is
> > > > > > working ok :)
> > > > > > Piotr, please, a last attempt. I think you'll get working right
> now
> > > > from
> > > > > > Moonshine.
> > > > > >
> > > > > > As well I'm curious about how to build with IDE in Moonshine, or
> > why
> > > > > >  Project > Build Project is not working for me
> > > > > > something I must have into account?
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Carlos
> > > > > >
> > > > > >
> > > > > >
> > > > > > El dom., 22 mar. 2020 a las 17:04, Christofer Dutz (<
> > > > > > christofer.d...@c-ware.de>) escribió:
> > > > > >
> > > > > > > Yeah ... sorry for that.
> > > > > > >
> > > > > > > I noticed that I took care of the "SNAPSHOT" instead of the
> > > > Timestamp,
> > > > > > but
> > > > > > > I forgot to add the classifier ... will be in the next PR.
> > > > > > > Can you confirm that now the files have a "SNAPSHOT" instead of
> > the
> > > > > > > Timestamp?
> > > > > > >
> > > > > > > Chris
> > > > > > >
> > > > > > > Am 22.03.20, 15:56 schrieb "Piotr Zarzycki" <
> > > > > piotrzarzyck...@gmail.com
> > > > > > >:
> > > > > > >
> > > > > > > Hi Chris,
> > > > > > >
> > > > > > > Nothing changed I have exactly same issue after pulling all
> > > > changes
> > > > > > and
> > > > > > > rebuilding sdk.
> > > > > > >
> > > > > > > niedz., 22 mar 2020 o 12:15 Carlos Rovira <
> > > > carlosrov...@apache.org
> > > > > >
> > > > > > > napisał(a):
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > Many thanks for the fix Chris.
> > > > > > > > Piotr, can you try again and confirm if all is ok now?
> > > > > > > >
> > > > > > > > thanks
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > El dom., 22 mar. 2020 a las 11:47, Christofer Dutz (<
> > > > > > > > christofer.d...@c-ware.de>) escribió:
> > > > > > > >
> > > > > > > > > Hi Piotr,
> > > > > > > > >
> > > > > > > > > I had a look and you are right ... even if this only
> > seems
> > > to
> > > > > > > happen if
> > > > > > > > > you haven't built the typedefs on your machine that day
> > > > before
> > > > > > > building
> > > > > > > > the
> > > > > > > > > distribution. I just pushed a PR that should fix this.
> > > > > > > > >
> > > > > > > > > Chris
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Am 22.03.20, 10:59 schrieb "Piotr Zarzycki" <
> > > > > > > piotrzarzyck...@gmail.com
> > > > > > > > >:
> > > > > > > > >
> > > > > > > > > Hi Carlos,
> > > > > > > > >
> > > > > > > > > I've just build royale-asjs with following command:
> > > > > > > > >
> > > > > > > > > mvn clean install -P
> > > > > > with-distribution,option-with-sass-compile
> > > > > > > > > -DdistributionTargetFolder=path
> > > > > > > > >
> > > > > > > > > Created new Royale Jewel project with latest
> nightly
> > > non
> > > > > > > sandbox
> > > > > > > > build
> > > > > > > > > of
> > > > > > > > > Moonshine and I got following result during build
> [1]
> > > > > > > > >
> > > > > > > > > [1] https://paste.apache.org/u5j0a
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Piotr
> > > > > > > > >
> > > > > > > > > sob., 21 mar 2020 o 

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

Next is reproduce your problem with Moonshine. ;)

pon., 23 mar 2020 o 15:02 Carlos Rovira 
napisał(a):

> Very cool Piotr!
> seems we finally has Maven distribution sdk working! :)
>
> El lun., 23 mar. 2020 a las 14:44, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Guys,
> >
> > I just checked Maven Distribution with Moonshine and I was able to build
> > Jewel Hello World and TourDeJewel. :)
> >
> > Thanks,
> > Piotr
> >
> > niedz., 22 mar 2020 o 20:58 Carlos Rovira 
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > nothing happens or log is printed in the console, is like if I didn't
> > push
> > > the menu button.
> > > I ensured that I have the SDK setup, maybe something more is needed,
> and
> > > I'm missing something.
> > > As well I understand that "Project > Build Project" is the right option
> > in
> > > the menu to push
> > >
> > > Thanks
> > >
> > > El dom., 22 mar. 2020 a las 17:55, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Carlos,
> > > >
> > > > By saying that nothing happens - you don't get any information on the
> > > > console at all?
> > > >
> > > > On Sun, Mar 22, 2020, 5:34 PM Carlos Rovira  >
> > > > wrote:
> > > >
> > > > > Hi Chris and Piotr,
> > > > >
> > > > > I was having the same issue. After latest PR from Chris, I can
> > confirm
> > > is
> > > > > working ok :)
> > > > > Piotr, please, a last attempt. I think you'll get working right now
> > > from
> > > > > Moonshine.
> > > > >
> > > > > As well I'm curious about how to build with IDE in Moonshine, or
> why
> > > > >  Project > Build Project is not working for me
> > > > > something I must have into account?
> > > > >
> > > > > Thanks
> > > > >
> > > > > Carlos
> > > > >
> > > > >
> > > > >
> > > > > El dom., 22 mar. 2020 a las 17:04, Christofer Dutz (<
> > > > > christofer.d...@c-ware.de>) escribió:
> > > > >
> > > > > > Yeah ... sorry for that.
> > > > > >
> > > > > > I noticed that I took care of the "SNAPSHOT" instead of the
> > > Timestamp,
> > > > > but
> > > > > > I forgot to add the classifier ... will be in the next PR.
> > > > > > Can you confirm that now the files have a "SNAPSHOT" instead of
> the
> > > > > > Timestamp?
> > > > > >
> > > > > > Chris
> > > > > >
> > > > > > Am 22.03.20, 15:56 schrieb "Piotr Zarzycki" <
> > > > piotrzarzyck...@gmail.com
> > > > > >:
> > > > > >
> > > > > > Hi Chris,
> > > > > >
> > > > > > Nothing changed I have exactly same issue after pulling all
> > > changes
> > > > > and
> > > > > > rebuilding sdk.
> > > > > >
> > > > > > niedz., 22 mar 2020 o 12:15 Carlos Rovira <
> > > carlosrov...@apache.org
> > > > >
> > > > > > napisał(a):
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > Many thanks for the fix Chris.
> > > > > > > Piotr, can you try again and confirm if all is ok now?
> > > > > > >
> > > > > > > thanks
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > El dom., 22 mar. 2020 a las 11:47, Christofer Dutz (<
> > > > > > > christofer.d...@c-ware.de>) escribió:
> > > > > > >
> > > > > > > > Hi Piotr,
> > > > > > > >
> > > > > > > > I had a look and you are right ... even if this only
> seems
> > to
> > > > > > happen if
> > > > > > > > you haven't built the typedefs on your machine that day
> > > before
> > > > > > building
> > > > > > > the
> > > > > > > > distribution. I just pushed a PR that should fix this.
> > > > > > > >
> > > > > > > > Chris
> > > > > > > >
> > > > > > > >
> > > > > > > > Am 22.03.20, 10:59 schrieb "Piotr Zarzycki" <
> > > > > > piotrzarzyck...@gmail.com
> > > > > > > >:
> > > > > > > >
> > > > > > > > Hi Carlos,
> > > > > > > >
> > > > > > > > I've just build royale-asjs with following command:
> > > > > > > >
> > > > > > > > mvn clean install -P
> > > > > with-distribution,option-with-sass-compile
> > > > > > > > -DdistributionTargetFolder=path
> > > > > > > >
> > > > > > > > Created new Royale Jewel project with latest nightly
> > non
> > > > > > sandbox
> > > > > > > build
> > > > > > > > of
> > > > > > > > Moonshine and I got following result during build [1]
> > > > > > > >
> > > > > > > > [1] https://paste.apache.org/u5j0a
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Piotr
> > > > > > > >
> > > > > > > > sob., 21 mar 2020 o 20:12 Carlos Rovira <
> > > > > > carlosrov...@apache.org>
> > > > > > > > napisał(a):
> > > > > > > >
> > > > > > > > > Hi Piotr,
> > > > > > > > >
> > > > > > > > > Chris, just made maven distribution mxmlc and compc
> > > > > > executables.
> > > > > > > > >
> > > > > > > > >- I test and VSCode works fine
> > > > > > > > >- command line worked too [1]
> > > > > > > > >- Moonshine:  I couldn't launch a compilation
> with
> > > > SDK.
> > > 

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Very cool Piotr!
seems we finally has Maven distribution sdk working! :)

El lun., 23 mar. 2020 a las 14:44, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Guys,
>
> I just checked Maven Distribution with Moonshine and I was able to build
> Jewel Hello World and TourDeJewel. :)
>
> Thanks,
> Piotr
>
> niedz., 22 mar 2020 o 20:58 Carlos Rovira 
> napisał(a):
>
> > Hi Piotr,
> >
> > nothing happens or log is printed in the console, is like if I didn't
> push
> > the menu button.
> > I ensured that I have the SDK setup, maybe something more is needed, and
> > I'm missing something.
> > As well I understand that "Project > Build Project" is the right option
> in
> > the menu to push
> >
> > Thanks
> >
> > El dom., 22 mar. 2020 a las 17:55, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Carlos,
> > >
> > > By saying that nothing happens - you don't get any information on the
> > > console at all?
> > >
> > > On Sun, Mar 22, 2020, 5:34 PM Carlos Rovira 
> > > wrote:
> > >
> > > > Hi Chris and Piotr,
> > > >
> > > > I was having the same issue. After latest PR from Chris, I can
> confirm
> > is
> > > > working ok :)
> > > > Piotr, please, a last attempt. I think you'll get working right now
> > from
> > > > Moonshine.
> > > >
> > > > As well I'm curious about how to build with IDE in Moonshine, or why
> > > >  Project > Build Project is not working for me
> > > > something I must have into account?
> > > >
> > > > Thanks
> > > >
> > > > Carlos
> > > >
> > > >
> > > >
> > > > El dom., 22 mar. 2020 a las 17:04, Christofer Dutz (<
> > > > christofer.d...@c-ware.de>) escribió:
> > > >
> > > > > Yeah ... sorry for that.
> > > > >
> > > > > I noticed that I took care of the "SNAPSHOT" instead of the
> > Timestamp,
> > > > but
> > > > > I forgot to add the classifier ... will be in the next PR.
> > > > > Can you confirm that now the files have a "SNAPSHOT" instead of the
> > > > > Timestamp?
> > > > >
> > > > > Chris
> > > > >
> > > > > Am 22.03.20, 15:56 schrieb "Piotr Zarzycki" <
> > > piotrzarzyck...@gmail.com
> > > > >:
> > > > >
> > > > > Hi Chris,
> > > > >
> > > > > Nothing changed I have exactly same issue after pulling all
> > changes
> > > > and
> > > > > rebuilding sdk.
> > > > >
> > > > > niedz., 22 mar 2020 o 12:15 Carlos Rovira <
> > carlosrov...@apache.org
> > > >
> > > > > napisał(a):
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > Many thanks for the fix Chris.
> > > > > > Piotr, can you try again and confirm if all is ok now?
> > > > > >
> > > > > > thanks
> > > > > >
> > > > > >
> > > > > >
> > > > > > El dom., 22 mar. 2020 a las 11:47, Christofer Dutz (<
> > > > > > christofer.d...@c-ware.de>) escribió:
> > > > > >
> > > > > > > Hi Piotr,
> > > > > > >
> > > > > > > I had a look and you are right ... even if this only seems
> to
> > > > > happen if
> > > > > > > you haven't built the typedefs on your machine that day
> > before
> > > > > building
> > > > > > the
> > > > > > > distribution. I just pushed a PR that should fix this.
> > > > > > >
> > > > > > > Chris
> > > > > > >
> > > > > > >
> > > > > > > Am 22.03.20, 10:59 schrieb "Piotr Zarzycki" <
> > > > > piotrzarzyck...@gmail.com
> > > > > > >:
> > > > > > >
> > > > > > > Hi Carlos,
> > > > > > >
> > > > > > > I've just build royale-asjs with following command:
> > > > > > >
> > > > > > > mvn clean install -P
> > > > with-distribution,option-with-sass-compile
> > > > > > > -DdistributionTargetFolder=path
> > > > > > >
> > > > > > > Created new Royale Jewel project with latest nightly
> non
> > > > > sandbox
> > > > > > build
> > > > > > > of
> > > > > > > Moonshine and I got following result during build [1]
> > > > > > >
> > > > > > > [1] https://paste.apache.org/u5j0a
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Piotr
> > > > > > >
> > > > > > > sob., 21 mar 2020 o 20:12 Carlos Rovira <
> > > > > carlosrov...@apache.org>
> > > > > > > napisał(a):
> > > > > > >
> > > > > > > > Hi Piotr,
> > > > > > > >
> > > > > > > > Chris, just made maven distribution mxmlc and compc
> > > > > executables.
> > > > > > > >
> > > > > > > >- I test and VSCode works fine
> > > > > > > >- command line worked too [1]
> > > > > > > >- Moonshine:  I couldn't launch a compilation with
> > > SDK.
> > > > > Just
> > > > > > > upgrade
> > > > > > > >to latest version as Moonshine requested me. I
> have
> > > the
> > > > > SDK
> > > > > > > configured to
> > > > > > > >the distribution created with Maven. Then with TDJ
> > > > project
> > > > > > loaded
> > > > > > > when to
> > > > > > > >Project > Build Project, but nothings happen
> > > > > > > >
> > > > >   

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

Hi Guys,

I just checked Maven Distribution with Moonshine and I was able to build
Jewel Hello World and TourDeJewel. :)

Thanks,
Piotr

niedz., 22 mar 2020 o 20:58 Carlos Rovira 
napisał(a):

> Hi Piotr,
>
> nothing happens or log is printed in the console, is like if I didn't push
> the menu button.
> I ensured that I have the SDK setup, maybe something more is needed, and
> I'm missing something.
> As well I understand that "Project > Build Project" is the right option in
> the menu to push
>
> Thanks
>
> El dom., 22 mar. 2020 a las 17:55, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Carlos,
> >
> > By saying that nothing happens - you don't get any information on the
> > console at all?
> >
> > On Sun, Mar 22, 2020, 5:34 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Chris and Piotr,
> > >
> > > I was having the same issue. After latest PR from Chris, I can confirm
> is
> > > working ok :)
> > > Piotr, please, a last attempt. I think you'll get working right now
> from
> > > Moonshine.
> > >
> > > As well I'm curious about how to build with IDE in Moonshine, or why
> > >  Project > Build Project is not working for me
> > > something I must have into account?
> > >
> > > Thanks
> > >
> > > Carlos
> > >
> > >
> > >
> > > El dom., 22 mar. 2020 a las 17:04, Christofer Dutz (<
> > > christofer.d...@c-ware.de>) escribió:
> > >
> > > > Yeah ... sorry for that.
> > > >
> > > > I noticed that I took care of the "SNAPSHOT" instead of the
> Timestamp,
> > > but
> > > > I forgot to add the classifier ... will be in the next PR.
> > > > Can you confirm that now the files have a "SNAPSHOT" instead of the
> > > > Timestamp?
> > > >
> > > > Chris
> > > >
> > > > Am 22.03.20, 15:56 schrieb "Piotr Zarzycki" <
> > piotrzarzyck...@gmail.com
> > > >:
> > > >
> > > > Hi Chris,
> > > >
> > > > Nothing changed I have exactly same issue after pulling all
> changes
> > > and
> > > > rebuilding sdk.
> > > >
> > > > niedz., 22 mar 2020 o 12:15 Carlos Rovira <
> carlosrov...@apache.org
> > >
> > > > napisał(a):
> > > >
> > > > > Hi,
> > > > >
> > > > > Many thanks for the fix Chris.
> > > > > Piotr, can you try again and confirm if all is ok now?
> > > > >
> > > > > thanks
> > > > >
> > > > >
> > > > >
> > > > > El dom., 22 mar. 2020 a las 11:47, Christofer Dutz (<
> > > > > christofer.d...@c-ware.de>) escribió:
> > > > >
> > > > > > Hi Piotr,
> > > > > >
> > > > > > I had a look and you are right ... even if this only seems to
> > > > happen if
> > > > > > you haven't built the typedefs on your machine that day
> before
> > > > building
> > > > > the
> > > > > > distribution. I just pushed a PR that should fix this.
> > > > > >
> > > > > > Chris
> > > > > >
> > > > > >
> > > > > > Am 22.03.20, 10:59 schrieb "Piotr Zarzycki" <
> > > > piotrzarzyck...@gmail.com
> > > > > >:
> > > > > >
> > > > > > Hi Carlos,
> > > > > >
> > > > > > I've just build royale-asjs with following command:
> > > > > >
> > > > > > mvn clean install -P
> > > with-distribution,option-with-sass-compile
> > > > > > -DdistributionTargetFolder=path
> > > > > >
> > > > > > Created new Royale Jewel project with latest nightly non
> > > > sandbox
> > > > > build
> > > > > > of
> > > > > > Moonshine and I got following result during build [1]
> > > > > >
> > > > > > [1] https://paste.apache.org/u5j0a
> > > > > >
> > > > > > Thanks,
> > > > > > Piotr
> > > > > >
> > > > > > sob., 21 mar 2020 o 20:12 Carlos Rovira <
> > > > carlosrov...@apache.org>
> > > > > > napisał(a):
> > > > > >
> > > > > > > Hi Piotr,
> > > > > > >
> > > > > > > Chris, just made maven distribution mxmlc and compc
> > > > executables.
> > > > > > >
> > > > > > >- I test and VSCode works fine
> > > > > > >- command line worked too [1]
> > > > > > >- Moonshine:  I couldn't launch a compilation with
> > SDK.
> > > > Just
> > > > > > upgrade
> > > > > > >to latest version as Moonshine requested me. I have
> > the
> > > > SDK
> > > > > > configured to
> > > > > > >the distribution created with Maven. Then with TDJ
> > > project
> > > > > loaded
> > > > > > when to
> > > > > > >Project > Build Project, but nothings happen
> > > > > > >
> > > > > > > So just need to see how to check Moonshine so we can
> > check
> > > > Maven
> > > > > > > distribution is completed at last. I want to have that
> > for
> > > > this
> > > > > > release
> > > > > > > 0.9.7
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > Carlos
> > > > > > >
> > > > > > > [1] output in command line for Tour de Jewel:
> > > > > > >
> > > > > > > 

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi Piotr,

nothing happens or log is printed in the console, is like if I didn't push
the menu button.
I ensured that I have the SDK setup, maybe something more is needed, and
I'm missing something.
As well I understand that "Project > Build Project" is the right option in
the menu to push

Thanks

El dom., 22 mar. 2020 a las 17:55, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Carlos,
>
> By saying that nothing happens - you don't get any information on the
> console at all?
>
> On Sun, Mar 22, 2020, 5:34 PM Carlos Rovira 
> wrote:
>
> > Hi Chris and Piotr,
> >
> > I was having the same issue. After latest PR from Chris, I can confirm is
> > working ok :)
> > Piotr, please, a last attempt. I think you'll get working right now from
> > Moonshine.
> >
> > As well I'm curious about how to build with IDE in Moonshine, or why
> >  Project > Build Project is not working for me
> > something I must have into account?
> >
> > Thanks
> >
> > Carlos
> >
> >
> >
> > El dom., 22 mar. 2020 a las 17:04, Christofer Dutz (<
> > christofer.d...@c-ware.de>) escribió:
> >
> > > Yeah ... sorry for that.
> > >
> > > I noticed that I took care of the "SNAPSHOT" instead of the Timestamp,
> > but
> > > I forgot to add the classifier ... will be in the next PR.
> > > Can you confirm that now the files have a "SNAPSHOT" instead of the
> > > Timestamp?
> > >
> > > Chris
> > >
> > > Am 22.03.20, 15:56 schrieb "Piotr Zarzycki" <
> piotrzarzyck...@gmail.com
> > >:
> > >
> > > Hi Chris,
> > >
> > > Nothing changed I have exactly same issue after pulling all changes
> > and
> > > rebuilding sdk.
> > >
> > > niedz., 22 mar 2020 o 12:15 Carlos Rovira  >
> > > napisał(a):
> > >
> > > > Hi,
> > > >
> > > > Many thanks for the fix Chris.
> > > > Piotr, can you try again and confirm if all is ok now?
> > > >
> > > > thanks
> > > >
> > > >
> > > >
> > > > El dom., 22 mar. 2020 a las 11:47, Christofer Dutz (<
> > > > christofer.d...@c-ware.de>) escribió:
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > I had a look and you are right ... even if this only seems to
> > > happen if
> > > > > you haven't built the typedefs on your machine that day before
> > > building
> > > > the
> > > > > distribution. I just pushed a PR that should fix this.
> > > > >
> > > > > Chris
> > > > >
> > > > >
> > > > > Am 22.03.20, 10:59 schrieb "Piotr Zarzycki" <
> > > piotrzarzyck...@gmail.com
> > > > >:
> > > > >
> > > > > Hi Carlos,
> > > > >
> > > > > I've just build royale-asjs with following command:
> > > > >
> > > > > mvn clean install -P
> > with-distribution,option-with-sass-compile
> > > > > -DdistributionTargetFolder=path
> > > > >
> > > > > Created new Royale Jewel project with latest nightly non
> > > sandbox
> > > > build
> > > > > of
> > > > > Moonshine and I got following result during build [1]
> > > > >
> > > > > [1] https://paste.apache.org/u5j0a
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > sob., 21 mar 2020 o 20:12 Carlos Rovira <
> > > carlosrov...@apache.org>
> > > > > napisał(a):
> > > > >
> > > > > > Hi Piotr,
> > > > > >
> > > > > > Chris, just made maven distribution mxmlc and compc
> > > executables.
> > > > > >
> > > > > >- I test and VSCode works fine
> > > > > >- command line worked too [1]
> > > > > >- Moonshine:  I couldn't launch a compilation with
> SDK.
> > > Just
> > > > > upgrade
> > > > > >to latest version as Moonshine requested me. I have
> the
> > > SDK
> > > > > configured to
> > > > > >the distribution created with Maven. Then with TDJ
> > project
> > > > loaded
> > > > > when to
> > > > > >Project > Build Project, but nothings happen
> > > > > >
> > > > > > So just need to see how to check Moonshine so we can
> check
> > > Maven
> > > > > > distribution is completed at last. I want to have that
> for
> > > this
> > > > > release
> > > > > > 0.9.7
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Carlos
> > > > > >
> > > > > > [1] output in command line for Tour de Jewel:
> > > > > >
> > > > > > macbookpro:TourDeJewel carlosrovira$
> > > > > >
> > > >
> > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc
> > > > > > -load-config+=obj/TourDeJewelConfig.xml -debug=true
> > > > -source-map=true
> > > > > > -compiler.targets=JSRoyale
> > > > > >
> > > > >
> > > >
> > >
> >
> -js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary
> > > > > >
> > > > > > >
> > > > > >
> > > > > > 

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

Carlos,

By saying that nothing happens - you don't get any information on the
console at all?

On Sun, Mar 22, 2020, 5:34 PM Carlos Rovira  wrote:

> Hi Chris and Piotr,
>
> I was having the same issue. After latest PR from Chris, I can confirm is
> working ok :)
> Piotr, please, a last attempt. I think you'll get working right now from
> Moonshine.
>
> As well I'm curious about how to build with IDE in Moonshine, or why
>  Project > Build Project is not working for me
> something I must have into account?
>
> Thanks
>
> Carlos
>
>
>
> El dom., 22 mar. 2020 a las 17:04, Christofer Dutz (<
> christofer.d...@c-ware.de>) escribió:
>
> > Yeah ... sorry for that.
> >
> > I noticed that I took care of the "SNAPSHOT" instead of the Timestamp,
> but
> > I forgot to add the classifier ... will be in the next PR.
> > Can you confirm that now the files have a "SNAPSHOT" instead of the
> > Timestamp?
> >
> > Chris
> >
> > Am 22.03.20, 15:56 schrieb "Piotr Zarzycki"  >:
> >
> > Hi Chris,
> >
> > Nothing changed I have exactly same issue after pulling all changes
> and
> > rebuilding sdk.
> >
> > niedz., 22 mar 2020 o 12:15 Carlos Rovira 
> > napisał(a):
> >
> > > Hi,
> > >
> > > Many thanks for the fix Chris.
> > > Piotr, can you try again and confirm if all is ok now?
> > >
> > > thanks
> > >
> > >
> > >
> > > El dom., 22 mar. 2020 a las 11:47, Christofer Dutz (<
> > > christofer.d...@c-ware.de>) escribió:
> > >
> > > > Hi Piotr,
> > > >
> > > > I had a look and you are right ... even if this only seems to
> > happen if
> > > > you haven't built the typedefs on your machine that day before
> > building
> > > the
> > > > distribution. I just pushed a PR that should fix this.
> > > >
> > > > Chris
> > > >
> > > >
> > > > Am 22.03.20, 10:59 schrieb "Piotr Zarzycki" <
> > piotrzarzyck...@gmail.com
> > > >:
> > > >
> > > > Hi Carlos,
> > > >
> > > > I've just build royale-asjs with following command:
> > > >
> > > > mvn clean install -P
> with-distribution,option-with-sass-compile
> > > > -DdistributionTargetFolder=path
> > > >
> > > > Created new Royale Jewel project with latest nightly non
> > sandbox
> > > build
> > > > of
> > > > Moonshine and I got following result during build [1]
> > > >
> > > > [1] https://paste.apache.org/u5j0a
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > sob., 21 mar 2020 o 20:12 Carlos Rovira <
> > carlosrov...@apache.org>
> > > > napisał(a):
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > Chris, just made maven distribution mxmlc and compc
> > executables.
> > > > >
> > > > >- I test and VSCode works fine
> > > > >- command line worked too [1]
> > > > >- Moonshine:  I couldn't launch a compilation with SDK.
> > Just
> > > > upgrade
> > > > >to latest version as Moonshine requested me. I have the
> > SDK
> > > > configured to
> > > > >the distribution created with Maven. Then with TDJ
> project
> > > loaded
> > > > when to
> > > > >Project > Build Project, but nothings happen
> > > > >
> > > > > So just need to see how to check Moonshine so we can check
> > Maven
> > > > > distribution is completed at last. I want to have that for
> > this
> > > > release
> > > > > 0.9.7
> > > > >
> > > > > Thanks
> > > > >
> > > > > Carlos
> > > > >
> > > > > [1] output in command line for Tour de Jewel:
> > > > >
> > > > > macbookpro:TourDeJewel carlosrovira$
> > > > >
> > >
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc
> > > > > -load-config+=obj/TourDeJewelConfig.xml -debug=true
> > > -source-map=true
> > > > > -compiler.targets=JSRoyale
> > > > >
> > > >
> > >
> >
> -js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary
> > > > >
> > > > > >
> > > > >
> > > > > macbookpro:TourDeJewel carlosrovira$
> > > > >
> > >
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc
> > > > > -load-config+=obj/TourDeJewelConfig.xml -debug=true
> > > -source-map=true
> > > > > -compiler.targets=JSRoyale
> > > > >
> > > >
> > >
> >
> -js-output=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary
> > > > >
> > > > > Using Royale Compiler codebase:
> > > > > /Users/carlosrovira/Dev/Royale/Source/royale-compiler
> > > > >
> > > > > Using Royale SDK:
> > > > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > > > >
> > > > > MXMLJSC
> > > > >
> >   

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi Chris and Piotr,

I was having the same issue. After latest PR from Chris, I can confirm is
working ok :)
Piotr, please, a last attempt. I think you'll get working right now from
Moonshine.

As well I'm curious about how to build with IDE in Moonshine, or why
 Project > Build Project is not working for me
something I must have into account?

Thanks

Carlos



El dom., 22 mar. 2020 a las 17:04, Christofer Dutz (<
christofer.d...@c-ware.de>) escribió:

> Yeah ... sorry for that.
>
> I noticed that I took care of the "SNAPSHOT" instead of the Timestamp, but
> I forgot to add the classifier ... will be in the next PR.
> Can you confirm that now the files have a "SNAPSHOT" instead of the
> Timestamp?
>
> Chris
>
> Am 22.03.20, 15:56 schrieb "Piotr Zarzycki" :
>
> Hi Chris,
>
> Nothing changed I have exactly same issue after pulling all changes and
> rebuilding sdk.
>
> niedz., 22 mar 2020 o 12:15 Carlos Rovira 
> napisał(a):
>
> > Hi,
> >
> > Many thanks for the fix Chris.
> > Piotr, can you try again and confirm if all is ok now?
> >
> > thanks
> >
> >
> >
> > El dom., 22 mar. 2020 a las 11:47, Christofer Dutz (<
> > christofer.d...@c-ware.de>) escribió:
> >
> > > Hi Piotr,
> > >
> > > I had a look and you are right ... even if this only seems to
> happen if
> > > you haven't built the typedefs on your machine that day before
> building
> > the
> > > distribution. I just pushed a PR that should fix this.
> > >
> > > Chris
> > >
> > >
> > > Am 22.03.20, 10:59 schrieb "Piotr Zarzycki" <
> piotrzarzyck...@gmail.com
> > >:
> > >
> > > Hi Carlos,
> > >
> > > I've just build royale-asjs with following command:
> > >
> > > mvn clean install -P with-distribution,option-with-sass-compile
> > > -DdistributionTargetFolder=path
> > >
> > > Created new Royale Jewel project with latest nightly non
> sandbox
> > build
> > > of
> > > Moonshine and I got following result during build [1]
> > >
> > > [1] https://paste.apache.org/u5j0a
> > >
> > > Thanks,
> > > Piotr
> > >
> > > sob., 21 mar 2020 o 20:12 Carlos Rovira <
> carlosrov...@apache.org>
> > > napisał(a):
> > >
> > > > Hi Piotr,
> > > >
> > > > Chris, just made maven distribution mxmlc and compc
> executables.
> > > >
> > > >- I test and VSCode works fine
> > > >- command line worked too [1]
> > > >- Moonshine:  I couldn't launch a compilation with SDK.
> Just
> > > upgrade
> > > >to latest version as Moonshine requested me. I have the
> SDK
> > > configured to
> > > >the distribution created with Maven. Then with TDJ project
> > loaded
> > > when to
> > > >Project > Build Project, but nothings happen
> > > >
> > > > So just need to see how to check Moonshine so we can check
> Maven
> > > > distribution is completed at last. I want to have that for
> this
> > > release
> > > > 0.9.7
> > > >
> > > > Thanks
> > > >
> > > > Carlos
> > > >
> > > > [1] output in command line for Tour de Jewel:
> > > >
> > > > macbookpro:TourDeJewel carlosrovira$
> > > >
> > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc
> > > > -load-config+=obj/TourDeJewelConfig.xml -debug=true
> > -source-map=true
> > > > -compiler.targets=JSRoyale
> > > >
> > >
> >
> -js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary
> > > >
> > > > >
> > > >
> > > > macbookpro:TourDeJewel carlosrovira$
> > > >
> > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc
> > > > -load-config+=obj/TourDeJewelConfig.xml -debug=true
> > -source-map=true
> > > > -compiler.targets=JSRoyale
> > > >
> > >
> >
> -js-output=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary
> > > >
> > > > Using Royale Compiler codebase:
> > > > /Users/carlosrovira/Dev/Royale/Source/royale-compiler
> > > >
> > > > Using Royale SDK:
> > > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > > >
> > > > MXMLJSC
> > > >
> > > >
> > > >
> > >
> >
> +royalelib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks
> > > >
> > > >
> > > >
> > >
> >
> -sdk-js-lib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks/js/Royale/generated-sources
> > > >
> > > > -load-config+=obj/TourDeJewelConfig.xml
> > > >
> > > > -debug=true
> > > >
> > > > 

Re: Maven Distribution SDK fixed and working for IDEs

[Christofer Dutz]

Yeah ... sorry for that. 

I noticed that I took care of the "SNAPSHOT" instead of the Timestamp, but I 
forgot to add the classifier ... will be in the next PR.
Can you confirm that now the files have a "SNAPSHOT" instead of the Timestamp?

Chris

Am 22.03.20, 15:56 schrieb "Piotr Zarzycki" :

Hi Chris,

Nothing changed I have exactly same issue after pulling all changes and
rebuilding sdk.

niedz., 22 mar 2020 o 12:15 Carlos Rovira 
napisał(a):

> Hi,
>
> Many thanks for the fix Chris.
> Piotr, can you try again and confirm if all is ok now?
>
> thanks
>
>
>
> El dom., 22 mar. 2020 a las 11:47, Christofer Dutz (<
> christofer.d...@c-ware.de>) escribió:
>
> > Hi Piotr,
> >
> > I had a look and you are right ... even if this only seems to happen if
> > you haven't built the typedefs on your machine that day before building
> the
> > distribution. I just pushed a PR that should fix this.
> >
> > Chris
> >
> >
> > Am 22.03.20, 10:59 schrieb "Piotr Zarzycki"  >:
> >
> > Hi Carlos,
> >
> > I've just build royale-asjs with following command:
> >
> > mvn clean install -P with-distribution,option-with-sass-compile
> > -DdistributionTargetFolder=path
> >
> > Created new Royale Jewel project with latest nightly non sandbox
> build
> > of
> > Moonshine and I got following result during build [1]
> >
> > [1] https://paste.apache.org/u5j0a
> >
> > Thanks,
> > Piotr
> >
> > sob., 21 mar 2020 o 20:12 Carlos Rovira 
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > Chris, just made maven distribution mxmlc and compc executables.
> > >
> > >- I test and VSCode works fine
> > >- command line worked too [1]
> > >- Moonshine:  I couldn't launch a compilation with SDK. Just
> > upgrade
> > >to latest version as Moonshine requested me. I have the SDK
> > configured to
> > >the distribution created with Maven. Then with TDJ project
> loaded
> > when to
> > >Project > Build Project, but nothings happen
> > >
> > > So just need to see how to check Moonshine so we can check Maven
> > > distribution is completed at last. I want to have that for this
> > release
> > > 0.9.7
> > >
> > > Thanks
> > >
> > > Carlos
> > >
> > > [1] output in command line for Tour de Jewel:
> > >
> > > macbookpro:TourDeJewel carlosrovira$
> > >
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc
> > > -load-config+=obj/TourDeJewelConfig.xml -debug=true
> -source-map=true
> > > -compiler.targets=JSRoyale
> > >
> >
> 
-js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary
> > >
> > > >
> > >
> > > macbookpro:TourDeJewel carlosrovira$
> > >
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc
> > > -load-config+=obj/TourDeJewelConfig.xml -debug=true
> -source-map=true
> > > -compiler.targets=JSRoyale
> > >
> >
> 
-js-output=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary
> > >
> > > Using Royale Compiler codebase:
> > > /Users/carlosrovira/Dev/Royale/Source/royale-compiler
> > >
> > > Using Royale SDK:
> > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > >
> > > MXMLJSC
> > >
> > >
> > >
> >
> 
+royalelib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks
> > >
> > >
> > >
> >
> 
-sdk-js-lib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks/js/Royale/generated-sources
> > >
> > > -load-config+=obj/TourDeJewelConfig.xml
> > >
> > > -debug=true
> > >
> > > -source-map=true
> > >
> > > -compiler.targets=JSRoyale
> > >
> > >
> > >
> >
> 
-js-output=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary
> > >
> > > The project 'App' has been successfully compiled.
> > >
> > > 7.080432099 seconds
> > >
> > > El lun., 10 feb. 2020 a las 18:19, Carlos Rovira (<
> > carlosrov...@apache.org>)
> > > escribió:
> > >
> > >> Ok Josh,
> > >> understood, will take into account as I check what's going on 
with
> > latest
> > >> fails
> > >> thanks
> > >>
> > >> El lun., 10 feb. 2020 a las 17:16, Josh Tynjala (<
> > >> joshtynj...@bowlerhat.dev>) escribió:

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi,

Many thanks for the fix Chris.
Piotr, can you try again and confirm if all is ok now?

thanks



El dom., 22 mar. 2020 a las 11:47, Christofer Dutz (<
christofer.d...@c-ware.de>) escribió:

> Hi Piotr,
>
> I had a look and you are right ... even if this only seems to happen if
> you haven't built the typedefs on your machine that day before building the
> distribution. I just pushed a PR that should fix this.
>
> Chris
>
>
> Am 22.03.20, 10:59 schrieb "Piotr Zarzycki" :
>
> Hi Carlos,
>
> I've just build royale-asjs with following command:
>
> mvn clean install -P with-distribution,option-with-sass-compile
> -DdistributionTargetFolder=path
>
> Created new Royale Jewel project with latest nightly non sandbox build
> of
> Moonshine and I got following result during build [1]
>
> [1] https://paste.apache.org/u5j0a
>
> Thanks,
> Piotr
>
> sob., 21 mar 2020 o 20:12 Carlos Rovira 
> napisał(a):
>
> > Hi Piotr,
> >
> > Chris, just made maven distribution mxmlc and compc executables.
> >
> >- I test and VSCode works fine
> >- command line worked too [1]
> >- Moonshine:  I couldn't launch a compilation with SDK. Just
> upgrade
> >to latest version as Moonshine requested me. I have the SDK
> configured to
> >the distribution created with Maven. Then with TDJ project loaded
> when to
> >Project > Build Project, but nothings happen
> >
> > So just need to see how to check Moonshine so we can check Maven
> > distribution is completed at last. I want to have that for this
> release
> > 0.9.7
> >
> > Thanks
> >
> > Carlos
> >
> > [1] output in command line for Tour de Jewel:
> >
> > macbookpro:TourDeJewel carlosrovira$
> > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc
> > -load-config+=obj/TourDeJewelConfig.xml -debug=true -source-map=true
> > -compiler.targets=JSRoyale
> >
> -js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary
> >
> > >
> >
> > macbookpro:TourDeJewel carlosrovira$
> > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc
> > -load-config+=obj/TourDeJewelConfig.xml -debug=true -source-map=true
> > -compiler.targets=JSRoyale
> >
> -js-output=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary
> >
> > Using Royale Compiler codebase:
> > /Users/carlosrovira/Dev/Royale/Source/royale-compiler
> >
> > Using Royale SDK:
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> >
> > MXMLJSC
> >
> >
> >
> +royalelib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks
> >
> >
> >
> -sdk-js-lib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks/js/Royale/generated-sources
> >
> > -load-config+=obj/TourDeJewelConfig.xml
> >
> > -debug=true
> >
> > -source-map=true
> >
> > -compiler.targets=JSRoyale
> >
> >
> >
> -js-output=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary
> >
> > The project 'App' has been successfully compiled.
> >
> > 7.080432099 seconds
> >
> > El lun., 10 feb. 2020 a las 18:19, Carlos Rovira (<
> carlosrov...@apache.org>)
> > escribió:
> >
> >> Ok Josh,
> >> understood, will take into account as I check what's going on with
> latest
> >> fails
> >> thanks
> >>
> >> El lun., 10 feb. 2020 a las 17:16, Josh Tynjala (<
> >> joshtynj...@bowlerhat.dev>) escribió:
> >>
> >>> VSCode happens to run the JAR files directly with Java, and
> doesn't run
> >>> anything in js/bin. If the contents of js/bin do not have the
> correct
> >>> exectuable permissions, it wouldn't affect VSCode. However, fixing
> those
> >>> permissions would still be a problem that should be addressed to
> have a
> >>> proper distribution. Moonshine is not doing anything out of the
> ordinary
> >>> by
> >>> running js/bin/mxmlc (and that's what someone compiling from the
> command
> >>> line without Maven or Ant would use too). If anything, it's VSCode
> that
> >>> is
> >>> not doing things in the ordinary way.
> >>>
> >>> --
> >>> Josh Tynjala
> >>> Bowler Hat LLC 
> >>>
> >>>
> >>> On Mon, Feb 10, 2020 at 12:48 AM Carlos Rovira <
> carlosrov...@apache.org>
> >>> wrote:
> >>>
> >>> > Hi,
> >>> >
> >>> > @Piotr Zarzycki  I was over the big
> button
> >>> to
> >>> > nightly builds, since you told me to download that. So from the
> big
> >>> button
> >>> > I choosed "other downloads" and choosed non sandbox one. Both
> url goes
> >>> to
> >>> > the same link: Moonshine_Signed_NonSandbox.pkg
> >>> > <
> >>> >
> >>>
> 

Re: Maven Distribution SDK fixed and working for IDEs

[Christofer Dutz]

Hi Piotr,

I had a look and you are right ... even if this only seems to happen if you 
haven't built the typedefs on your machine that day before building the 
distribution. I just pushed a PR that should fix this.

Chris


Am 22.03.20, 10:59 schrieb "Piotr Zarzycki" :

Hi Carlos,

I've just build royale-asjs with following command:

mvn clean install -P with-distribution,option-with-sass-compile
-DdistributionTargetFolder=path

Created new Royale Jewel project with latest nightly non sandbox build of
Moonshine and I got following result during build [1]

[1] https://paste.apache.org/u5j0a

Thanks,
Piotr

sob., 21 mar 2020 o 20:12 Carlos Rovira 
napisał(a):

> Hi Piotr,
>
> Chris, just made maven distribution mxmlc and compc executables.
>
>- I test and VSCode works fine
>- command line worked too [1]
>- Moonshine:  I couldn't launch a compilation with SDK. Just upgrade
>to latest version as Moonshine requested me. I have the SDK configured 
to
>the distribution created with Maven. Then with TDJ project loaded when 
to
>Project > Build Project, but nothings happen
>
> So just need to see how to check Moonshine so we can check Maven
> distribution is completed at last. I want to have that for this release
> 0.9.7
>
> Thanks
>
> Carlos
>
> [1] output in command line for Tour de Jewel:
>
> macbookpro:TourDeJewel carlosrovira$
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc
> -load-config+=obj/TourDeJewelConfig.xml -debug=true -source-map=true
> -compiler.targets=JSRoyale
> 
-js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary
>
> >
>
> macbookpro:TourDeJewel carlosrovira$
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc
> -load-config+=obj/TourDeJewelConfig.xml -debug=true -source-map=true
> -compiler.targets=JSRoyale
> 
-js-output=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary
>
> Using Royale Compiler codebase:
> /Users/carlosrovira/Dev/Royale/Source/royale-compiler
>
> Using Royale SDK: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
>
> MXMLJSC
>
>
> 
+royalelib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks
>
>
> 
-sdk-js-lib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks/js/Royale/generated-sources
>
> -load-config+=obj/TourDeJewelConfig.xml
>
> -debug=true
>
> -source-map=true
>
> -compiler.targets=JSRoyale
>
>
> 
-js-output=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary
>
> The project 'App' has been successfully compiled.
>
> 7.080432099 seconds
>
> El lun., 10 feb. 2020 a las 18:19, Carlos Rovira 
()
> escribió:
>
>> Ok Josh,
>> understood, will take into account as I check what's going on with latest
>> fails
>> thanks
>>
>> El lun., 10 feb. 2020 a las 17:16, Josh Tynjala (<
>> joshtynj...@bowlerhat.dev>) escribió:
>>
>>> VSCode happens to run the JAR files directly with Java, and doesn't run
>>> anything in js/bin. If the contents of js/bin do not have the correct
>>> exectuable permissions, it wouldn't affect VSCode. However, fixing those
>>> permissions would still be a problem that should be addressed to have a
>>> proper distribution. Moonshine is not doing anything out of the ordinary
>>> by
>>> running js/bin/mxmlc (and that's what someone compiling from the command
>>> line without Maven or Ant would use too). If anything, it's VSCode that
>>> is
>>> not doing things in the ordinary way.
>>>
>>> --
>>> Josh Tynjala
>>> Bowler Hat LLC 
>>>
>>>
>>> On Mon, Feb 10, 2020 at 12:48 AM Carlos Rovira 
>>> wrote:
>>>
>>> > Hi,
>>> >
>>> > @Piotr Zarzycki  I was over the big button
>>> to
>>> > nightly builds, since you told me to download that. So from the big
>>> button
>>> > I choosed "other downloads" and choosed non sandbox one. Both url goes
>>> to
>>> > the same link: Moonshine_Signed_NonSandbox.pkg
>>> > <
>>> >
>>> 
https://moonshine-ide.com/downloads/releases/dev/macos/Moonshine_Signed_NonSandbox.pkg
>>> > >
>>> > 07-Feb-2020 21:11 156571205
>>> >
>>> > About the permissions: My guess is that is something related to
>>> Moonshine,
>>> > not to user or maven, since VSCode is dealing with the same SDK 
without
>>> > complain. I can give permissions to try this, but I suggest the
>>> moonshine
>>> > team could look to how VSCode work with user files and mimic that to
>>> > avoid this kind of problem.
>>> >

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi Piotr,

Chris, just made maven distribution mxmlc and compc executables.

   - I test and VSCode works fine
   - command line worked too [1]
   - Moonshine:  I couldn't launch a compilation with SDK. Just upgrade to
   latest version as Moonshine requested me. I have the SDK configured to the
   distribution created with Maven. Then with TDJ project loaded when to
   Project > Build Project, but nothings happen

So just need to see how to check Moonshine so we can check Maven
distribution is completed at last. I want to have that for this release
0.9.7

Thanks

Carlos

[1] output in command line for Tour de Jewel:

macbookpro:TourDeJewel carlosrovira$
/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc
-load-config+=obj/TourDeJewelConfig.xml -debug=true -source-map=true
-compiler.targets=JSRoyale
-js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary

>

macbookpro:TourDeJewel carlosrovira$
/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc
-load-config+=obj/TourDeJewelConfig.xml -debug=true -source-map=true
-compiler.targets=JSRoyale
-js-output=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary

Using Royale Compiler codebase:
/Users/carlosrovira/Dev/Royale/Source/royale-compiler

Using Royale SDK: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven

MXMLJSC

+royalelib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks

-sdk-js-lib=/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks/js/Royale/generated-sources

-load-config+=obj/TourDeJewelConfig.xml

-debug=true

-source-map=true

-compiler.targets=JSRoyale

-js-output=/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/binary

The project 'App' has been successfully compiled.

7.080432099 seconds

El lun., 10 feb. 2020 a las 18:19, Carlos Rovira ()
escribió:

> Ok Josh,
> understood, will take into account as I check what's going on with latest
> fails
> thanks
>
> El lun., 10 feb. 2020 a las 17:16, Josh Tynjala (<
> joshtynj...@bowlerhat.dev>) escribió:
>
>> VSCode happens to run the JAR files directly with Java, and doesn't run
>> anything in js/bin. If the contents of js/bin do not have the correct
>> exectuable permissions, it wouldn't affect VSCode. However, fixing those
>> permissions would still be a problem that should be addressed to have a
>> proper distribution. Moonshine is not doing anything out of the ordinary
>> by
>> running js/bin/mxmlc (and that's what someone compiling from the command
>> line without Maven or Ant would use too). If anything, it's VSCode that is
>> not doing things in the ordinary way.
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC 
>>
>>
>> On Mon, Feb 10, 2020 at 12:48 AM Carlos Rovira 
>> wrote:
>>
>> > Hi,
>> >
>> > @Piotr Zarzycki  I was over the big button
>> to
>> > nightly builds, since you told me to download that. So from the big
>> button
>> > I choosed "other downloads" and choosed non sandbox one. Both url goes
>> to
>> > the same link: Moonshine_Signed_NonSandbox.pkg
>> > <
>> >
>> https://moonshine-ide.com/downloads/releases/dev/macos/Moonshine_Signed_NonSandbox.pkg
>> > >
>> > 07-Feb-2020 21:11 156571205
>> >
>> > About the permissions: My guess is that is something related to
>> Moonshine,
>> > not to user or maven, since VSCode is dealing with the same SDK without
>> > complain. I can give permissions to try this, but I suggest the
>> moonshine
>> > team could look to how VSCode work with user files and mimic that to
>> > avoid this kind of problem.
>> >
>> > Thanks
>> >
>> >
>> > El lun., 10 feb. 2020 a las 5:50, Alex Harui (> >)
>> > escribió:
>> >
>> > > IMO, the Maven commands that build the Distribution SDK should change
>> the
>> > > permissions.
>> > >
>> > > My 2 cents,
>> > > -Alex
>> > >
>> > > On 2/9/20, 11:04 AM, "Piotr Zarzycki" 
>> > wrote:
>> > >
>> > > Permission to "mxmlc" file in SDK. - You have to add permission
>> for
>> > > usage
>> > > manually to that file.
>> > >
>> > > I will explain you more on Monday if you won't figure it out your
>> > self,
>> > > what is all about.
>> > >
>> > > You can literally paste in Google last sentence from stack trace
>> > error
>> > > and
>> > > add: How to add permission to file on Mac.
>> > >
>> > >
>> > >
>> > > On Sun, Feb 9, 2020, 7:09 PM Carlos Rovira <
>> carlosrov...@apache.org>
>> > > wrote:
>> > >
>> > > > Hi Piotr,
>> > > >
>> > > > but what kind of permission? to the moonshine executable?
>> > > >
>> > > > El dom., 9 feb. 2020 a las 17:49, Piotr Zarzycki (<
>> > > > piotrzarzyck...@gmail.com>)
>> > > > escribió:
>> > > >
>> > > > > If you are using your own SDK (not downloaded trough Moonshine
>> > > getting
>> > > > > started) you have to add permission to mxmlc file. There is a
>> > > command on
>> > > > > Mac chmod - try to search using that command on a Google.
>> > 

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Ok Josh,
understood, will take into account as I check what's going on with latest
fails
thanks

El lun., 10 feb. 2020 a las 17:16, Josh Tynjala ()
escribió:

> VSCode happens to run the JAR files directly with Java, and doesn't run
> anything in js/bin. If the contents of js/bin do not have the correct
> exectuable permissions, it wouldn't affect VSCode. However, fixing those
> permissions would still be a problem that should be addressed to have a
> proper distribution. Moonshine is not doing anything out of the ordinary by
> running js/bin/mxmlc (and that's what someone compiling from the command
> line without Maven or Ant would use too). If anything, it's VSCode that is
> not doing things in the ordinary way.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Mon, Feb 10, 2020 at 12:48 AM Carlos Rovira 
> wrote:
>
> > Hi,
> >
> > @Piotr Zarzycki  I was over the big button to
> > nightly builds, since you told me to download that. So from the big
> button
> > I choosed "other downloads" and choosed non sandbox one. Both url goes to
> > the same link: Moonshine_Signed_NonSandbox.pkg
> > <
> >
> https://moonshine-ide.com/downloads/releases/dev/macos/Moonshine_Signed_NonSandbox.pkg
> > >
> > 07-Feb-2020 21:11 156571205
> >
> > About the permissions: My guess is that is something related to
> Moonshine,
> > not to user or maven, since VSCode is dealing with the same SDK without
> > complain. I can give permissions to try this, but I suggest the moonshine
> > team could look to how VSCode work with user files and mimic that to
> > avoid this kind of problem.
> >
> > Thanks
> >
> >
> > El lun., 10 feb. 2020 a las 5:50, Alex Harui ( >)
> > escribió:
> >
> > > IMO, the Maven commands that build the Distribution SDK should change
> the
> > > permissions.
> > >
> > > My 2 cents,
> > > -Alex
> > >
> > > On 2/9/20, 11:04 AM, "Piotr Zarzycki" 
> > wrote:
> > >
> > > Permission to "mxmlc" file in SDK. - You have to add permission for
> > > usage
> > > manually to that file.
> > >
> > > I will explain you more on Monday if you won't figure it out your
> > self,
> > > what is all about.
> > >
> > > You can literally paste in Google last sentence from stack trace
> > error
> > > and
> > > add: How to add permission to file on Mac.
> > >
> > >
> > >
> > > On Sun, Feb 9, 2020, 7:09 PM Carlos Rovira <
> carlosrov...@apache.org>
> > > wrote:
> > >
> > > > Hi Piotr,
> > > >
> > > > but what kind of permission? to the moonshine executable?
> > > >
> > > > El dom., 9 feb. 2020 a las 17:49, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>)
> > > > escribió:
> > > >
> > > > > If you are using your own SDK (not downloaded trough Moonshine
> > > getting
> > > > > started) you have to add permission to mxmlc file. There is a
> > > command on
> > > > > Mac chmod - try to search using that command on a Google.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > On Sun, Feb 9, 2020, 5:29 PM Carlos Rovira <
> > > carlosrov...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I installed latest Moonshine nightly. After configuring
> initial
> > > things
> > > > > > loaded TDJ project. I'm getting Permission denied:
> > > > > >
> > > > > > : Moonshine IDE™ 2.5.0
> > > > > > : Copyright © Prominic.NET, Inc. All rights reserved.
> > > > > > : Source code is under Apache License, Version 2.0
> > > > > > :
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fprominic%2FMoonshine-IDEdata=02%7C01%7Caharui%40adobe.com%7C978f7b2983214ea95d7408d7ad92dcc5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637168718639009927sdata=9zd56GJARnqI0KhVKJ%2BCzChzlveojwAONlyaXBL144c%3Dreserved=0
> > > > > > : Uses as3abc (LGPL), as3swf (MIT), fzip (ZLIB), asblocks
> > (Apache
> > > > License
> > > > > > 2.0), NativeApplicationUpdater (LGPL)
> > > > > > : Running on Adobe AIR 28.0.0.125
> > > > > > : Compiling TourDeJewel
> > > > > > : SDK path:
> > > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > > > > > : Sending to mxmlx: export
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > > > > >
> > > ROYALE_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"
> > > > &&
> > > > > > export
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > > > > > SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en" &&
> export
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> ROYALE_COMPILER_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"&&
> > > > > >
> > > "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> > > > > 

Re: Maven Distribution SDK fixed and working for IDEs

[Josh Tynjala]

VSCode happens to run the JAR files directly with Java, and doesn't run
anything in js/bin. If the contents of js/bin do not have the correct
exectuable permissions, it wouldn't affect VSCode. However, fixing those
permissions would still be a problem that should be addressed to have a
proper distribution. Moonshine is not doing anything out of the ordinary by
running js/bin/mxmlc (and that's what someone compiling from the command
line without Maven or Ant would use too). If anything, it's VSCode that is
not doing things in the ordinary way.

--
Josh Tynjala
Bowler Hat LLC 


On Mon, Feb 10, 2020 at 12:48 AM Carlos Rovira 
wrote:

> Hi,
>
> @Piotr Zarzycki  I was over the big button to
> nightly builds, since you told me to download that. So from the big button
> I choosed "other downloads" and choosed non sandbox one. Both url goes to
> the same link: Moonshine_Signed_NonSandbox.pkg
> <
> https://moonshine-ide.com/downloads/releases/dev/macos/Moonshine_Signed_NonSandbox.pkg
> >
> 07-Feb-2020 21:11 156571205
>
> About the permissions: My guess is that is something related to Moonshine,
> not to user or maven, since VSCode is dealing with the same SDK without
> complain. I can give permissions to try this, but I suggest the moonshine
> team could look to how VSCode work with user files and mimic that to
> avoid this kind of problem.
>
> Thanks
>
>
> El lun., 10 feb. 2020 a las 5:50, Alex Harui ()
> escribió:
>
> > IMO, the Maven commands that build the Distribution SDK should change the
> > permissions.
> >
> > My 2 cents,
> > -Alex
> >
> > On 2/9/20, 11:04 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Permission to "mxmlc" file in SDK. - You have to add permission for
> > usage
> > manually to that file.
> >
> > I will explain you more on Monday if you won't figure it out your
> self,
> > what is all about.
> >
> > You can literally paste in Google last sentence from stack trace
> error
> > and
> > add: How to add permission to file on Mac.
> >
> >
> >
> > On Sun, Feb 9, 2020, 7:09 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Piotr,
> > >
> > > but what kind of permission? to the moonshine executable?
> > >
> > > El dom., 9 feb. 2020 a las 17:49, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>)
> > > escribió:
> > >
> > > > If you are using your own SDK (not downloaded trough Moonshine
> > getting
> > > > started) you have to add permission to mxmlc file. There is a
> > command on
> > > > Mac chmod - try to search using that command on a Google.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Sun, Feb 9, 2020, 5:29 PM Carlos Rovira <
> > carlosrov...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I installed latest Moonshine nightly. After configuring initial
> > things
> > > > > loaded TDJ project. I'm getting Permission denied:
> > > > >
> > > > > : Moonshine IDE™ 2.5.0
> > > > > : Copyright © Prominic.NET, Inc. All rights reserved.
> > > > > : Source code is under Apache License, Version 2.0
> > > > > :
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fprominic%2FMoonshine-IDEdata=02%7C01%7Caharui%40adobe.com%7C978f7b2983214ea95d7408d7ad92dcc5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637168718639009927sdata=9zd56GJARnqI0KhVKJ%2BCzChzlveojwAONlyaXBL144c%3Dreserved=0
> > > > > : Uses as3abc (LGPL), as3swf (MIT), fzip (ZLIB), asblocks
> (Apache
> > > License
> > > > > 2.0), NativeApplicationUpdater (LGPL)
> > > > > : Running on Adobe AIR 28.0.0.125
> > > > > : Compiling TourDeJewel
> > > > > : SDK path:
> > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > > > > : Sending to mxmlx: export
> > > > >
> > > > >
> > > >
> > >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > > > >
> > ROYALE_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"
> > > &&
> > > > > export
> > > > >
> > > > >
> > > >
> > >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > > > > SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en" && export
> > > > >
> > > > >
> > > >
> > >
> >
> ROYALE_COMPILER_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"&&
> > > > >
> > "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> > > > > -load-config+=obj/TourDeJewelConfig.xml
> > > > >
> > -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > > > >
> > -html-template=src/main/resources/jewel-example-index-template.html
> > > > > -js-dynamic-access-unknown-members=true
> > -compiler.targets=JSRoyale
> > > > >
> > > > >
> > > >
> > >
> >
> -js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel"
> > > > > : /bin/bash:

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

Thanks! Good luck!

pon., 10 lut 2020 o 15:22 Carlos Rovira 
napisał(a):

> Hi Piotr,
>
> trying now in command line and VSCode is failing. So I need to check latest
> commits since something is wrong.
> I'll track this as I get some available time to see what changed since my
> latest successful test.
>
>
>
> El lun., 10 feb. 2020 a las 12:51, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > I do revisit all of your points - in fact I'm on it right now and it
> takes
> > couple of days. However the question is - did you try reproduce problem
> in
> > console ?
> >
> > pon., 10 lut 2020 o 12:31 Carlos Rovira 
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > one thing I see is that Moonshine generates a folder obj with an .xml
> > file.
> > > In TDJ it's TourDeJewelConfig.xmlm, with this content that is pointing
> to
> > > Flash Player 20.0.0:
> > >
> > > 
> > > 
> > > 
> > > 
> > > 20.0.0
> > > 
> > > 
> > > 
> > >
> > >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/src/main/royale
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/src/main/royale/App.mxml
> > > 
> > > 
> > > #FF
> > > 60
> > > 
> > > 800
> > > 600
> > > 
> > > 
> > >
> > > Could this be interfering? I think Moonshine should revise the
> requisites
> > > needed to compile a project since VSCode does not need to do things
> like
> > > this, and we are using a JS-only SDK that does not know anything about
> > > flash player and air.
> > >
> > > My point is: If VSCode can handle it, then Moonshine should do it as
> > well,
> > > isn't it?
> > >
> > > Let me know if I could be wrong.
> > >
> > > Thanks
> > >
> > >
> > > El lun., 10 feb. 2020 a las 10:50, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Carlos,
> > > >
> > > > I told you to download Nightly build, but I didn't said how. It looks
> > > like
> > > > it's not an obvious from our website fully how to get it, but I'm not
> > > sure
> > > > whether it actually should be. Anyway I'm happy that you was able to
> > > > download it finally.
> > > >
> > > > Apart of issues with Moonshine do you have some thought about our
> main
> > > > issue with distribution ? It doesn't work still with that IDE, but
> > issue
> > > is
> > > > not related to IDE itself - you should be able reproduce it trough
> > > console
> > > > as well.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > >
> > > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi Piotr,

trying now in command line and VSCode is failing. So I need to check latest
commits since something is wrong.
I'll track this as I get some available time to see what changed since my
latest successful test.



El lun., 10 feb. 2020 a las 12:51, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> I do revisit all of your points - in fact I'm on it right now and it takes
> couple of days. However the question is - did you try reproduce problem in
> console ?
>
> pon., 10 lut 2020 o 12:31 Carlos Rovira 
> napisał(a):
>
> > Hi Piotr,
> >
> > one thing I see is that Moonshine generates a folder obj with an .xml
> file.
> > In TDJ it's TourDeJewelConfig.xmlm, with this content that is pointing to
> > Flash Player 20.0.0:
> >
> > 
> > 
> > 
> > 
> > 20.0.0
> > 
> > 
> > 
> >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/src/main/royale
> > 
> > 
> > 
> > 
> > 
> >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/src/main/royale/App.mxml
> > 
> > 
> > #FF
> > 60
> > 
> > 800
> > 600
> > 
> > 
> >
> > Could this be interfering? I think Moonshine should revise the requisites
> > needed to compile a project since VSCode does not need to do things like
> > this, and we are using a JS-only SDK that does not know anything about
> > flash player and air.
> >
> > My point is: If VSCode can handle it, then Moonshine should do it as
> well,
> > isn't it?
> >
> > Let me know if I could be wrong.
> >
> > Thanks
> >
> >
> > El lun., 10 feb. 2020 a las 10:50, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > Hi Carlos,
> > >
> > > I told you to download Nightly build, but I didn't said how. It looks
> > like
> > > it's not an obvious from our website fully how to get it, but I'm not
> > sure
> > > whether it actually should be. Anyway I'm happy that you was able to
> > > download it finally.
> > >
> > > Apart of issues with Moonshine do you have some thought about our main
> > > issue with distribution ? It doesn't work still with that IDE, but
> issue
> > is
> > > not related to IDE itself - you should be able reproduce it trough
> > console
> > > as well.
> > >
> > > Thanks,
> > > Piotr
> > >
> > >
> > > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


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

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

I do revisit all of your points - in fact I'm on it right now and it takes
couple of days. However the question is - did you try reproduce problem in
console ?

pon., 10 lut 2020 o 12:31 Carlos Rovira 
napisał(a):

> Hi Piotr,
>
> one thing I see is that Moonshine generates a folder obj with an .xml file.
> In TDJ it's TourDeJewelConfig.xmlm, with this content that is pointing to
> Flash Player 20.0.0:
>
> 
> 
> 
> 
> 20.0.0
> 
> 
> 
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/src/main/royale
> 
> 
> 
> 
> 
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/src/main/royale/App.mxml
> 
> 
> #FF
> 60
> 
> 800
> 600
> 
> 
>
> Could this be interfering? I think Moonshine should revise the requisites
> needed to compile a project since VSCode does not need to do things like
> this, and we are using a JS-only SDK that does not know anything about
> flash player and air.
>
> My point is: If VSCode can handle it, then Moonshine should do it as well,
> isn't it?
>
> Let me know if I could be wrong.
>
> Thanks
>
>
> El lun., 10 feb. 2020 a las 10:50, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Carlos,
> >
> > I told you to download Nightly build, but I didn't said how. It looks
> like
> > it's not an obvious from our website fully how to get it, but I'm not
> sure
> > whether it actually should be. Anyway I'm happy that you was able to
> > download it finally.
> >
> > Apart of issues with Moonshine do you have some thought about our main
> > issue with distribution ? It doesn't work still with that IDE, but issue
> is
> > not related to IDE itself - you should be able reproduce it trough
> console
> > as well.
> >
> > Thanks,
> > Piotr
> >
> >
> > --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi Piotr,

one thing I see is that Moonshine generates a folder obj with an .xml file.
In TDJ it's TourDeJewelConfig.xmlm, with this content that is pointing to
Flash Player 20.0.0:





20.0.0



/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/src/main/royale





/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel/src/main/royale/App.mxml


#FF
60

800
600



Could this be interfering? I think Moonshine should revise the requisites
needed to compile a project since VSCode does not need to do things like
this, and we are using a JS-only SDK that does not know anything about
flash player and air.

My point is: If VSCode can handle it, then Moonshine should do it as well,
isn't it?

Let me know if I could be wrong.

Thanks


El lun., 10 feb. 2020 a las 10:50, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Carlos,
>
> I told you to download Nightly build, but I didn't said how. It looks like
> it's not an obvious from our website fully how to get it, but I'm not sure
> whether it actually should be. Anyway I'm happy that you was able to
> download it finally.
>
> Apart of issues with Moonshine do you have some thought about our main
> issue with distribution ? It doesn't work still with that IDE, but issue is
> not related to IDE itself - you should be able reproduce it trough console
> as well.
>
> Thanks,
> Piotr
>
>
> --
Carlos Rovira
http://about.me/carlosrovira

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

Hi Carlos,

I told you to download Nightly build, but I didn't said how. It looks like
it's not an obvious from our website fully how to get it, but I'm not sure
whether it actually should be. Anyway I'm happy that you was able to
download it finally.

Apart of issues with Moonshine do you have some thought about our main
issue with distribution ? It doesn't work still with that IDE, but issue is
not related to IDE itself - you should be able reproduce it trough console
as well.

Thanks,
Piotr

pon., 10 lut 2020 o 09:48 Carlos Rovira 
napisał(a):

> Hi,
>
> @Piotr Zarzycki  I was over the big button to
> nightly builds, since you told me to download that. So from the big button
> I choosed "other downloads" and choosed non sandbox one. Both url goes to
> the same link: Moonshine_Signed_NonSandbox.pkg
> 
> 07-Feb-2020 21:11 156571205
>
> About the permissions: My guess is that is something related to Moonshine,
> not to user or maven, since VSCode is dealing with the same SDK without
> complain. I can give permissions to try this, but I suggest the moonshine
> team could look to how VSCode work with user files and mimic that to
> avoid this kind of problem.
>
> Thanks
>
>
> El lun., 10 feb. 2020 a las 5:50, Alex Harui ()
> escribió:
>
>> IMO, the Maven commands that build the Distribution SDK should change the
>> permissions.
>>
>> My 2 cents,
>> -Alex
>>
>> On 2/9/20, 11:04 AM, "Piotr Zarzycki"  wrote:
>>
>> Permission to "mxmlc" file in SDK. - You have to add permission for
>> usage
>> manually to that file.
>>
>> I will explain you more on Monday if you won't figure it out your
>> self,
>> what is all about.
>>
>> You can literally paste in Google last sentence from stack trace
>> error and
>> add: How to add permission to file on Mac.
>>
>>
>>
>> On Sun, Feb 9, 2020, 7:09 PM Carlos Rovira 
>> wrote:
>>
>> > Hi Piotr,
>> >
>> > but what kind of permission? to the moonshine executable?
>> >
>> > El dom., 9 feb. 2020 a las 17:49, Piotr Zarzycki (<
>> > piotrzarzyck...@gmail.com>)
>> > escribió:
>> >
>> > > If you are using your own SDK (not downloaded trough Moonshine
>> getting
>> > > started) you have to add permission to mxmlc file. There is a
>> command on
>> > > Mac chmod - try to search using that command on a Google.
>> > >
>> > > Thanks,
>> > > Piotr
>> > >
>> > > On Sun, Feb 9, 2020, 5:29 PM Carlos Rovira <
>> carlosrov...@apache.org>
>> > > wrote:
>> > >
>> > > > Hi,
>> > > >
>> > > > I installed latest Moonshine nightly. After configuring initial
>> things
>> > > > loaded TDJ project. I'm getting Permission denied:
>> > > >
>> > > > : Moonshine IDE™ 2.5.0
>> > > > : Copyright © Prominic.NET, Inc. All rights reserved.
>> > > > : Source code is under Apache License, Version 2.0
>> > > > :
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fprominic%2FMoonshine-IDEdata=02%7C01%7Caharui%40adobe.com%7C978f7b2983214ea95d7408d7ad92dcc5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637168718639009927sdata=9zd56GJARnqI0KhVKJ%2BCzChzlveojwAONlyaXBL144c%3Dreserved=0
>> > > > : Uses as3abc (LGPL), as3swf (MIT), fzip (ZLIB), asblocks
>> (Apache
>> > License
>> > > > 2.0), NativeApplicationUpdater (LGPL)
>> > > > : Running on Adobe AIR 28.0.0.125
>> > > > : Compiling TourDeJewel
>> > > > : SDK path:
>> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
>> > > > : Sending to mxmlx: export
>> > > >
>> > > >
>> > >
>> >
>> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
>> > > >
>> ROYALE_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"
>> > &&
>> > > > export
>> > > >
>> > > >
>> > >
>> >
>> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
>> > > > SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en" && export
>> > > >
>> > > >
>> > >
>> >
>> ROYALE_COMPILER_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"&&
>> > > >
>> "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
>> > > > -load-config+=obj/TourDeJewelConfig.xml
>> > > >
>> -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
>> > > >
>> -html-template=src/main/resources/jewel-example-index-template.html
>> > > > -js-dynamic-access-unknown-members=true
>> -compiler.targets=JSRoyale
>> > > >
>> > > >
>> > >
>> >
>> -js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel"
>> > > > : /bin/bash:
>> > > >
>> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc:
>> > > > Permission denied
>> > > >
>> > > > How can I fix it?
>> > > >
>> > > > Thanks
>> > > >
>> > > >
>>

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi,

@Piotr Zarzycki  I was over the big button to
nightly builds, since you told me to download that. So from the big button
I choosed "other downloads" and choosed non sandbox one. Both url goes to
the same link: Moonshine_Signed_NonSandbox.pkg

07-Feb-2020 21:11 156571205

About the permissions: My guess is that is something related to Moonshine,
not to user or maven, since VSCode is dealing with the same SDK without
complain. I can give permissions to try this, but I suggest the moonshine
team could look to how VSCode work with user files and mimic that to
avoid this kind of problem.

Thanks


El lun., 10 feb. 2020 a las 5:50, Alex Harui ()
escribió:

> IMO, the Maven commands that build the Distribution SDK should change the
> permissions.
>
> My 2 cents,
> -Alex
>
> On 2/9/20, 11:04 AM, "Piotr Zarzycki"  wrote:
>
> Permission to "mxmlc" file in SDK. - You have to add permission for
> usage
> manually to that file.
>
> I will explain you more on Monday if you won't figure it out your self,
> what is all about.
>
> You can literally paste in Google last sentence from stack trace error
> and
> add: How to add permission to file on Mac.
>
>
>
> On Sun, Feb 9, 2020, 7:09 PM Carlos Rovira 
> wrote:
>
> > Hi Piotr,
> >
> > but what kind of permission? to the moonshine executable?
> >
> > El dom., 9 feb. 2020 a las 17:49, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>)
> > escribió:
> >
> > > If you are using your own SDK (not downloaded trough Moonshine
> getting
> > > started) you have to add permission to mxmlc file. There is a
> command on
> > > Mac chmod - try to search using that command on a Google.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > On Sun, Feb 9, 2020, 5:29 PM Carlos Rovira <
> carlosrov...@apache.org>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I installed latest Moonshine nightly. After configuring initial
> things
> > > > loaded TDJ project. I'm getting Permission denied:
> > > >
> > > > : Moonshine IDE™ 2.5.0
> > > > : Copyright © Prominic.NET, Inc. All rights reserved.
> > > > : Source code is under Apache License, Version 2.0
> > > > :
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fprominic%2FMoonshine-IDEdata=02%7C01%7Caharui%40adobe.com%7C978f7b2983214ea95d7408d7ad92dcc5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637168718639009927sdata=9zd56GJARnqI0KhVKJ%2BCzChzlveojwAONlyaXBL144c%3Dreserved=0
> > > > : Uses as3abc (LGPL), as3swf (MIT), fzip (ZLIB), asblocks (Apache
> > License
> > > > 2.0), NativeApplicationUpdater (LGPL)
> > > > : Running on Adobe AIR 28.0.0.125
> > > > : Compiling TourDeJewel
> > > > : SDK path:
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > > > : Sending to mxmlx: export
> > > >
> > > >
> > >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > > >
> ROYALE_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"
> > &&
> > > > export
> > > >
> > > >
> > >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > > > SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en" && export
> > > >
> > > >
> > >
> >
> ROYALE_COMPILER_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"&&
> > > >
> "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> > > > -load-config+=obj/TourDeJewelConfig.xml
> > > >
> -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > > >
> -html-template=src/main/resources/jewel-example-index-template.html
> > > > -js-dynamic-access-unknown-members=true
> -compiler.targets=JSRoyale
> > > >
> > > >
> > >
> >
> -js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel"
> > > > : /bin/bash:
> > > >
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc:
> > > > Permission denied
> > > >
> > > > How can I fix it?
> > > >
> > > > Thanks
> > > >
> > > >
> > > > El jue., 6 feb. 2020 a las 17:24, Josh Tynjala (<
> > > joshtynj...@bowlerhat.dev
> > > > >)
> > > > escribió:
> > > >
> > > > > Yeah, I don't see why Moonshine is reporting those errors, but
> VSCode
> > > > does
> > > > > not. If royale-config.xml is referencing SWCs that don't
> exist, that
> > > > should
> > > > > affect both IDEs.
> > > > >
> > > > > Regardless, like you explained, the same issue should
> reproduce when
> > > > > compiling from a terminal without Moonshine.
> > > > >
> > > > > --
> > > > > Josh Tynjala
> > > > > Bowler Hat LLC <
> 

Re: Maven Distribution SDK fixed and working for IDEs

[Alex Harui]

IMO, the Maven commands that build the Distribution SDK should change the 
permissions.

My 2 cents,
-Alex

On 2/9/20, 11:04 AM, "Piotr Zarzycki"  wrote:

Permission to "mxmlc" file in SDK. - You have to add permission for usage
manually to that file.

I will explain you more on Monday if you won't figure it out your self,
what is all about.

You can literally paste in Google last sentence from stack trace error and
add: How to add permission to file on Mac.



On Sun, Feb 9, 2020, 7:09 PM Carlos Rovira  wrote:

> Hi Piotr,
>
> but what kind of permission? to the moonshine executable?
>
> El dom., 9 feb. 2020 a las 17:49, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > If you are using your own SDK (not downloaded trough Moonshine getting
> > started) you have to add permission to mxmlc file. There is a command on
> > Mac chmod - try to search using that command on a Google.
> >
> > Thanks,
> > Piotr
> >
> > On Sun, Feb 9, 2020, 5:29 PM Carlos Rovira 
> > wrote:
> >
> > > Hi,
> > >
> > > I installed latest Moonshine nightly. After configuring initial things
> > > loaded TDJ project. I'm getting Permission denied:
> > >
> > > : Moonshine IDE™ 2.5.0
> > > : Copyright © Prominic.NET, Inc. All rights reserved.
> > > : Source code is under Apache License, Version 2.0
> > > : 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fprominic%2FMoonshine-IDEdata=02%7C01%7Caharui%40adobe.com%7C978f7b2983214ea95d7408d7ad92dcc5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637168718639009927sdata=9zd56GJARnqI0KhVKJ%2BCzChzlveojwAONlyaXBL144c%3Dreserved=0
> > > : Uses as3abc (LGPL), as3swf (MIT), fzip (ZLIB), asblocks (Apache
> License
> > > 2.0), NativeApplicationUpdater (LGPL)
> > > : Running on Adobe AIR 28.0.0.125
> > > : Compiling TourDeJewel
> > > : SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > > : Sending to mxmlx: export
> > >
> > >
> >
> 
royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > > ROYALE_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"
> &&
> > > export
> > >
> > >
> >
> 
royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > > SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en" && export
> > >
> > >
> >
> 
ROYALE_COMPILER_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"&&
> > > "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> > > -load-config+=obj/TourDeJewelConfig.xml
> > > -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > > -html-template=src/main/resources/jewel-example-index-template.html
> > > -js-dynamic-access-unknown-members=true -compiler.targets=JSRoyale
> > >
> > >
> >
> 
-js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel"
> > > : /bin/bash:
> > > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc:
> > > Permission denied
> > >
> > > How can I fix it?
> > >
> > > Thanks
> > >
> > >
> > > El jue., 6 feb. 2020 a las 17:24, Josh Tynjala (<
> > joshtynj...@bowlerhat.dev
> > > >)
> > > escribió:
> > >
> > > > Yeah, I don't see why Moonshine is reporting those errors, but 
VSCode
> > > does
> > > > not. If royale-config.xml is referencing SWCs that don't exist, that
> > > should
> > > > affect both IDEs.
> > > >
> > > > Regardless, like you explained, the same issue should reproduce when
> > > > compiling from a terminal without Moonshine.
> > > >
> > > > --
> > > > Josh Tynjala
> > > > Bowler Hat LLC 

> > > >
> > > >
> > > > On Thu, Feb 6, 2020 at 5:10 AM Piotr Zarzycki <
> > piotrzarzyck...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > Hi Carlos,
> > > > >
> > > > > Yeah it would be pretty great if you could setup Moonshine, but 
you
> > > don't
> > > > > have to do that actually to reproduce the issue. Command which I
> have
> > > > > pasted in this thread can be copy and used in Terminal with small
> > path
> > > > > adjustment. Try it on any project you have using distribution 
build
> > and
> > > > for
> > > > > sure you will get the error.
> > > > >
> > > > > In case of Moonshine we have freez code for commits and prepare 
for
> > > > > release, we have some internal problems with 

Re: Maven Distribution SDK fixed and working for IDEs

[Takeshita Shoichiro]

Carlos

The strongest one is

chmod 777 mxmlc


2020年2月10日(月) 4:04 Piotr Zarzycki :

> Permission to "mxmlc" file in SDK. - You have to add permission for usage
> manually to that file.
>
> I will explain you more on Monday if you won't figure it out your self,
> what is all about.
>
> You can literally paste in Google last sentence from stack trace error and
> add: How to add permission to file on Mac.
>
>
>
> On Sun, Feb 9, 2020, 7:09 PM Carlos Rovira 
> wrote:
>
> > Hi Piotr,
> >
> > but what kind of permission? to the moonshine executable?
> >
> > El dom., 9 feb. 2020 a las 17:49, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>)
> > escribió:
> >
> > > If you are using your own SDK (not downloaded trough Moonshine getting
> > > started) you have to add permission to mxmlc file. There is a command
> on
> > > Mac chmod - try to search using that command on a Google.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > On Sun, Feb 9, 2020, 5:29 PM Carlos Rovira 
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I installed latest Moonshine nightly. After configuring initial
> things
> > > > loaded TDJ project. I'm getting Permission denied:
> > > >
> > > > : Moonshine IDE™ 2.5.0
> > > > : Copyright © Prominic.NET, Inc. All rights reserved.
> > > > : Source code is under Apache License, Version 2.0
> > > > : https://github.com/prominic/Moonshine-IDE
> > > > : Uses as3abc (LGPL), as3swf (MIT), fzip (ZLIB), asblocks (Apache
> > License
> > > > 2.0), NativeApplicationUpdater (LGPL)
> > > > : Running on Adobe AIR 28.0.0.125
> > > > : Compiling TourDeJewel
> > > > : SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > > > : Sending to mxmlx: export
> > > >
> > > >
> > >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > > > ROYALE_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"
> > &&
> > > > export
> > > >
> > > >
> > >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > > > SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en" && export
> > > >
> > > >
> > >
> >
> ROYALE_COMPILER_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"&&
> > > >
> "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> > > > -load-config+=obj/TourDeJewelConfig.xml
> > > > -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > > > -html-template=src/main/resources/jewel-example-index-template.html
> > > > -js-dynamic-access-unknown-members=true -compiler.targets=JSRoyale
> > > >
> > > >
> > >
> >
> -js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel"
> > > > : /bin/bash:
> > > > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc:
> > > > Permission denied
> > > >
> > > > How can I fix it?
> > > >
> > > > Thanks
> > > >
> > > >
> > > > El jue., 6 feb. 2020 a las 17:24, Josh Tynjala (<
> > > joshtynj...@bowlerhat.dev
> > > > >)
> > > > escribió:
> > > >
> > > > > Yeah, I don't see why Moonshine is reporting those errors, but
> VSCode
> > > > does
> > > > > not. If royale-config.xml is referencing SWCs that don't exist,
> that
> > > > should
> > > > > affect both IDEs.
> > > > >
> > > > > Regardless, like you explained, the same issue should reproduce
> when
> > > > > compiling from a terminal without Moonshine.
> > > > >
> > > > > --
> > > > > Josh Tynjala
> > > > > Bowler Hat LLC 
> > > > >
> > > > >
> > > > > On Thu, Feb 6, 2020 at 5:10 AM Piotr Zarzycki <
> > > piotrzarzyck...@gmail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Hi Carlos,
> > > > > >
> > > > > > Yeah it would be pretty great if you could setup Moonshine, but
> you
> > > > don't
> > > > > > have to do that actually to reproduce the issue. Command which I
> > have
> > > > > > pasted in this thread can be copy and used in Terminal with small
> > > path
> > > > > > adjustment. Try it on any project you have using distribution
> build
> > > and
> > > > > for
> > > > > > sure you will get the error.
> > > > > >
> > > > > > In case of Moonshine we have freez code for commits and prepare
> for
> > > > > > release, we have some internal problems with bamboo build - if it
> > > will
> > > > > get
> > > > > > resolved we should have release early next week. You can always
> try
> > > > > Nightly
> > > > > > build.
> > > > > >
> > > > > > I'm really surprised that VSCode do not throwing the same error -
> > > What
> > > > > > could be the case Josh? The only difference is that we are using
> > > mxmlc
> > > > > file
> > > > > > and VSCode is probably using jar file, but playerglobal.swc
> doesn't
> > > > > exists
> > > > > > so both should report same issue.
> > > > > >
> > > > > > Thanks,
> > > > > > Piotr
> > > > > >
> > > > > > czw., 6 lut 2020 o 13:02 Carlos Rovira 
> > > > > > napisał(a):
> > > > > >
> > > > > > > Hi Piotr,
> > > > > > >
> > > > > > > so I think you're a bit closer (not farther ;)), since compiler
> > was
> > > > > > found.
> > 

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

Permission to "mxmlc" file in SDK. - You have to add permission for usage
manually to that file.

I will explain you more on Monday if you won't figure it out your self,
what is all about.

You can literally paste in Google last sentence from stack trace error and
add: How to add permission to file on Mac.



On Sun, Feb 9, 2020, 7:09 PM Carlos Rovira  wrote:

> Hi Piotr,
>
> but what kind of permission? to the moonshine executable?
>
> El dom., 9 feb. 2020 a las 17:49, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > If you are using your own SDK (not downloaded trough Moonshine getting
> > started) you have to add permission to mxmlc file. There is a command on
> > Mac chmod - try to search using that command on a Google.
> >
> > Thanks,
> > Piotr
> >
> > On Sun, Feb 9, 2020, 5:29 PM Carlos Rovira 
> > wrote:
> >
> > > Hi,
> > >
> > > I installed latest Moonshine nightly. After configuring initial things
> > > loaded TDJ project. I'm getting Permission denied:
> > >
> > > : Moonshine IDE™ 2.5.0
> > > : Copyright © Prominic.NET, Inc. All rights reserved.
> > > : Source code is under Apache License, Version 2.0
> > > : https://github.com/prominic/Moonshine-IDE
> > > : Uses as3abc (LGPL), as3swf (MIT), fzip (ZLIB), asblocks (Apache
> License
> > > 2.0), NativeApplicationUpdater (LGPL)
> > > : Running on Adobe AIR 28.0.0.125
> > > : Compiling TourDeJewel
> > > : SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > > : Sending to mxmlx: export
> > >
> > >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > > ROYALE_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"
> &&
> > > export
> > >
> > >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > > SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en" && export
> > >
> > >
> >
> ROYALE_COMPILER_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"&&
> > > "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> > > -load-config+=obj/TourDeJewelConfig.xml
> > > -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > > -html-template=src/main/resources/jewel-example-index-template.html
> > > -js-dynamic-access-unknown-members=true -compiler.targets=JSRoyale
> > >
> > >
> >
> -js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel"
> > > : /bin/bash:
> > > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc:
> > > Permission denied
> > >
> > > How can I fix it?
> > >
> > > Thanks
> > >
> > >
> > > El jue., 6 feb. 2020 a las 17:24, Josh Tynjala (<
> > joshtynj...@bowlerhat.dev
> > > >)
> > > escribió:
> > >
> > > > Yeah, I don't see why Moonshine is reporting those errors, but VSCode
> > > does
> > > > not. If royale-config.xml is referencing SWCs that don't exist, that
> > > should
> > > > affect both IDEs.
> > > >
> > > > Regardless, like you explained, the same issue should reproduce when
> > > > compiling from a terminal without Moonshine.
> > > >
> > > > --
> > > > Josh Tynjala
> > > > Bowler Hat LLC 
> > > >
> > > >
> > > > On Thu, Feb 6, 2020 at 5:10 AM Piotr Zarzycki <
> > piotrzarzyck...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > Hi Carlos,
> > > > >
> > > > > Yeah it would be pretty great if you could setup Moonshine, but you
> > > don't
> > > > > have to do that actually to reproduce the issue. Command which I
> have
> > > > > pasted in this thread can be copy and used in Terminal with small
> > path
> > > > > adjustment. Try it on any project you have using distribution build
> > and
> > > > for
> > > > > sure you will get the error.
> > > > >
> > > > > In case of Moonshine we have freez code for commits and prepare for
> > > > > release, we have some internal problems with bamboo build - if it
> > will
> > > > get
> > > > > resolved we should have release early next week. You can always try
> > > > Nightly
> > > > > build.
> > > > >
> > > > > I'm really surprised that VSCode do not throwing the same error -
> > What
> > > > > could be the case Josh? The only difference is that we are using
> > mxmlc
> > > > file
> > > > > and VSCode is probably using jar file, but playerglobal.swc doesn't
> > > > exists
> > > > > so both should report same issue.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > czw., 6 lut 2020 o 13:02 Carlos Rovira 
> > > > > napisał(a):
> > > > >
> > > > > > Hi Piotr,
> > > > > >
> > > > > > so I think you're a bit closer (not farther ;)), since compiler
> was
> > > > > found.
> > > > > > Now is a matter to find what's missing.
> > > > > > What's curious for me is VSCode recognizes but Moonshine not. I
> > think
> > > > the
> > > > > > problem is each IDE is looking at different things to match a
> valid
> > > > SDK,
> > > > > > and maybe even we could be setting duplicate artifacts in the SDK
> > so
> > > > > VSCode
> > > > > > finds all but Moonshine not.
> > > > > > I'll be 

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

Carlos,

When you go to Moonshine website there is Big Download button - near that
button is arrow with drop down menu - Do you see it?

Choose non sandbox version for Mac.

Thanks,
Piotr

On Sun, Feb 9, 2020, 7:08 PM Carlos Rovira  wrote:

> Hi Piotr,
>
> link I use is this [1], and from there I downloaded this [2]
>
> [1] Nightly (Sandbox and Non-sandbox)
> 
> [2] Moonshine_Signed_NonSandbox.pkg
> <
> https://moonshine-ide.com/downloads/releases/dev/macos/Moonshine_Signed_NonSandbox.pkg
> >
>
> El dom., 9 feb. 2020 a las 17:40, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Hi Carlos,
> >
> > From the logs it doesn't looks like Nightly build, but official release,
> > unless there is something wrong with the logs.
> >
> > You'd should have in logs Moonshine 2.6.0 instead 2.5.0.
> >
> > On Sun, Feb 9, 2020, 5:29 PM Carlos Rovira 
> > wrote:
> >
> > > Hi,
> > >
> > > I installed latest Moonshine nightly. After configuring initial things
> > > loaded TDJ project. I'm getting Permission denied:
> > >
> > > : Moonshine IDE™ 2.5.0
> > > : Copyright © Prominic.NET, Inc. All rights reserved.
> > > : Source code is under Apache License, Version 2.0
> > > : https://github.com/prominic/Moonshine-IDE
> > > : Uses as3abc (LGPL), as3swf (MIT), fzip (ZLIB), asblocks (Apache
> License
> > > 2.0), NativeApplicationUpdater (LGPL)
> > > : Running on Adobe AIR 28.0.0.125
> > > : Compiling TourDeJewel
> > > : SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > > : Sending to mxmlx: export
> > >
> > >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > > ROYALE_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"
> &&
> > > export
> > >
> > >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > > SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en" && export
> > >
> > >
> >
> ROYALE_COMPILER_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"&&
> > > "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> > > -load-config+=obj/TourDeJewelConfig.xml
> > > -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > > -html-template=src/main/resources/jewel-example-index-template.html
> > > -js-dynamic-access-unknown-members=true -compiler.targets=JSRoyale
> > >
> > >
> >
> -js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel"
> > > : /bin/bash:
> > > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc:
> > > Permission denied
> > >
> > > How can I fix it?
> > >
> > > Thanks
> > >
> > >
> > > El jue., 6 feb. 2020 a las 17:24, Josh Tynjala (<
> > joshtynj...@bowlerhat.dev
> > > >)
> > > escribió:
> > >
> > > > Yeah, I don't see why Moonshine is reporting those errors, but VSCode
> > > does
> > > > not. If royale-config.xml is referencing SWCs that don't exist, that
> > > should
> > > > affect both IDEs.
> > > >
> > > > Regardless, like you explained, the same issue should reproduce when
> > > > compiling from a terminal without Moonshine.
> > > >
> > > > --
> > > > Josh Tynjala
> > > > Bowler Hat LLC 
> > > >
> > > >
> > > > On Thu, Feb 6, 2020 at 5:10 AM Piotr Zarzycki <
> > piotrzarzyck...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > Hi Carlos,
> > > > >
> > > > > Yeah it would be pretty great if you could setup Moonshine, but you
> > > don't
> > > > > have to do that actually to reproduce the issue. Command which I
> have
> > > > > pasted in this thread can be copy and used in Terminal with small
> > path
> > > > > adjustment. Try it on any project you have using distribution build
> > and
> > > > for
> > > > > sure you will get the error.
> > > > >
> > > > > In case of Moonshine we have freez code for commits and prepare for
> > > > > release, we have some internal problems with bamboo build - if it
> > will
> > > > get
> > > > > resolved we should have release early next week. You can always try
> > > > Nightly
> > > > > build.
> > > > >
> > > > > I'm really surprised that VSCode do not throwing the same error -
> > What
> > > > > could be the case Josh? The only difference is that we are using
> > mxmlc
> > > > file
> > > > > and VSCode is probably using jar file, but playerglobal.swc doesn't
> > > > exists
> > > > > so both should report same issue.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > czw., 6 lut 2020 o 13:02 Carlos Rovira 
> > > > > napisał(a):
> > > > >
> > > > > > Hi Piotr,
> > > > > >
> > > > > > so I think you're a bit closer (not farther ;)), since compiler
> was
> > > > > found.
> > > > > > Now is a matter to find what's missing.
> > > > > > What's curious for me is VSCode recognizes but Moonshine not. I
> > think
> > > > the
> > > > > > problem is each IDE is looking at different things to match a
> valid
> > > > SDK,
> > > > > > and maybe even we could be setting duplicate artifacts in 

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi Piotr,

but what kind of permission? to the moonshine executable?

El dom., 9 feb. 2020 a las 17:49, Piotr Zarzycki ()
escribió:

> If you are using your own SDK (not downloaded trough Moonshine getting
> started) you have to add permission to mxmlc file. There is a command on
> Mac chmod - try to search using that command on a Google.
>
> Thanks,
> Piotr
>
> On Sun, Feb 9, 2020, 5:29 PM Carlos Rovira 
> wrote:
>
> > Hi,
> >
> > I installed latest Moonshine nightly. After configuring initial things
> > loaded TDJ project. I'm getting Permission denied:
> >
> > : Moonshine IDE™ 2.5.0
> > : Copyright © Prominic.NET, Inc. All rights reserved.
> > : Source code is under Apache License, Version 2.0
> > : https://github.com/prominic/Moonshine-IDE
> > : Uses as3abc (LGPL), as3swf (MIT), fzip (ZLIB), asblocks (Apache License
> > 2.0), NativeApplicationUpdater (LGPL)
> > : Running on Adobe AIR 28.0.0.125
> > : Compiling TourDeJewel
> > : SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > : Sending to mxmlx: export
> >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > ROYALE_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven" &&
> > export
> >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en" && export
> >
> >
> ROYALE_COMPILER_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"&&
> > "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> > -load-config+=obj/TourDeJewelConfig.xml
> > -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > -html-template=src/main/resources/jewel-example-index-template.html
> > -js-dynamic-access-unknown-members=true -compiler.targets=JSRoyale
> >
> >
> -js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel"
> > : /bin/bash:
> > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc:
> > Permission denied
> >
> > How can I fix it?
> >
> > Thanks
> >
> >
> > El jue., 6 feb. 2020 a las 17:24, Josh Tynjala (<
> joshtynj...@bowlerhat.dev
> > >)
> > escribió:
> >
> > > Yeah, I don't see why Moonshine is reporting those errors, but VSCode
> > does
> > > not. If royale-config.xml is referencing SWCs that don't exist, that
> > should
> > > affect both IDEs.
> > >
> > > Regardless, like you explained, the same issue should reproduce when
> > > compiling from a terminal without Moonshine.
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC 
> > >
> > >
> > > On Thu, Feb 6, 2020 at 5:10 AM Piotr Zarzycki <
> piotrzarzyck...@gmail.com
> > >
> > > wrote:
> > >
> > > > Hi Carlos,
> > > >
> > > > Yeah it would be pretty great if you could setup Moonshine, but you
> > don't
> > > > have to do that actually to reproduce the issue. Command which I have
> > > > pasted in this thread can be copy and used in Terminal with small
> path
> > > > adjustment. Try it on any project you have using distribution build
> and
> > > for
> > > > sure you will get the error.
> > > >
> > > > In case of Moonshine we have freez code for commits and prepare for
> > > > release, we have some internal problems with bamboo build - if it
> will
> > > get
> > > > resolved we should have release early next week. You can always try
> > > Nightly
> > > > build.
> > > >
> > > > I'm really surprised that VSCode do not throwing the same error -
> What
> > > > could be the case Josh? The only difference is that we are using
> mxmlc
> > > file
> > > > and VSCode is probably using jar file, but playerglobal.swc doesn't
> > > exists
> > > > so both should report same issue.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > czw., 6 lut 2020 o 13:02 Carlos Rovira 
> > > > napisał(a):
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > so I think you're a bit closer (not farther ;)), since compiler was
> > > > found.
> > > > > Now is a matter to find what's missing.
> > > > > What's curious for me is VSCode recognizes but Moonshine not. I
> think
> > > the
> > > > > problem is each IDE is looking at different things to match a valid
> > > SDK,
> > > > > and maybe even we could be setting duplicate artifacts in the SDK
> so
> > > > VSCode
> > > > > finds all but Moonshine not.
> > > > > I'll be setup Moonshine as I have time to try it.
> > > > > I think you plan to launch a new one soon right? should I wait for
> > it?
> > > > >
> > > > > Thanks
> > > > >
> > > > >
> > > > > El jue., 6 feb. 2020 a las 7:53, Piotr Zarzycki (<
> > > > > piotrzarzyck...@gmail.com>)
> > > > > escribió:
> > > > >
> > > > > > Hi Carlos,
> > > > > >
> > > > > > I just tried your changes and I'm a bit farther. Now I'm getting
> > > > > following
> > > > > > errors. It's throwing that errors cause in JS only binaries
> > prepared
> > > by
> > > > > ant
> > > > > > we have in following location
> > > > > > /frameworks/libs/player/{playerbersion}/playerglobal.swc fake
> > > > > > 

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi Piotr,

link I use is this [1], and from there I downloaded this [2]

[1] Nightly (Sandbox and Non-sandbox)

[2] Moonshine_Signed_NonSandbox.pkg


El dom., 9 feb. 2020 a las 17:40, Piotr Zarzycki ()
escribió:

> Hi Carlos,
>
> From the logs it doesn't looks like Nightly build, but official release,
> unless there is something wrong with the logs.
>
> You'd should have in logs Moonshine 2.6.0 instead 2.5.0.
>
> On Sun, Feb 9, 2020, 5:29 PM Carlos Rovira 
> wrote:
>
> > Hi,
> >
> > I installed latest Moonshine nightly. After configuring initial things
> > loaded TDJ project. I'm getting Permission denied:
> >
> > : Moonshine IDE™ 2.5.0
> > : Copyright © Prominic.NET, Inc. All rights reserved.
> > : Source code is under Apache License, Version 2.0
> > : https://github.com/prominic/Moonshine-IDE
> > : Uses as3abc (LGPL), as3swf (MIT), fzip (ZLIB), asblocks (Apache License
> > 2.0), NativeApplicationUpdater (LGPL)
> > : Running on Adobe AIR 28.0.0.125
> > : Compiling TourDeJewel
> > : SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> > : Sending to mxmlx: export
> >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > ROYALE_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven" &&
> > export
> >
> >
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> > SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en" && export
> >
> >
> ROYALE_COMPILER_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"&&
> > "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> > -load-config+=obj/TourDeJewelConfig.xml
> > -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> > -html-template=src/main/resources/jewel-example-index-template.html
> > -js-dynamic-access-unknown-members=true -compiler.targets=JSRoyale
> >
> >
> -js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel"
> > : /bin/bash:
> > /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc:
> > Permission denied
> >
> > How can I fix it?
> >
> > Thanks
> >
> >
> > El jue., 6 feb. 2020 a las 17:24, Josh Tynjala (<
> joshtynj...@bowlerhat.dev
> > >)
> > escribió:
> >
> > > Yeah, I don't see why Moonshine is reporting those errors, but VSCode
> > does
> > > not. If royale-config.xml is referencing SWCs that don't exist, that
> > should
> > > affect both IDEs.
> > >
> > > Regardless, like you explained, the same issue should reproduce when
> > > compiling from a terminal without Moonshine.
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC 
> > >
> > >
> > > On Thu, Feb 6, 2020 at 5:10 AM Piotr Zarzycki <
> piotrzarzyck...@gmail.com
> > >
> > > wrote:
> > >
> > > > Hi Carlos,
> > > >
> > > > Yeah it would be pretty great if you could setup Moonshine, but you
> > don't
> > > > have to do that actually to reproduce the issue. Command which I have
> > > > pasted in this thread can be copy and used in Terminal with small
> path
> > > > adjustment. Try it on any project you have using distribution build
> and
> > > for
> > > > sure you will get the error.
> > > >
> > > > In case of Moonshine we have freez code for commits and prepare for
> > > > release, we have some internal problems with bamboo build - if it
> will
> > > get
> > > > resolved we should have release early next week. You can always try
> > > Nightly
> > > > build.
> > > >
> > > > I'm really surprised that VSCode do not throwing the same error -
> What
> > > > could be the case Josh? The only difference is that we are using
> mxmlc
> > > file
> > > > and VSCode is probably using jar file, but playerglobal.swc doesn't
> > > exists
> > > > so both should report same issue.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > czw., 6 lut 2020 o 13:02 Carlos Rovira 
> > > > napisał(a):
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > so I think you're a bit closer (not farther ;)), since compiler was
> > > > found.
> > > > > Now is a matter to find what's missing.
> > > > > What's curious for me is VSCode recognizes but Moonshine not. I
> think
> > > the
> > > > > problem is each IDE is looking at different things to match a valid
> > > SDK,
> > > > > and maybe even we could be setting duplicate artifacts in the SDK
> so
> > > > VSCode
> > > > > finds all but Moonshine not.
> > > > > I'll be setup Moonshine as I have time to try it.
> > > > > I think you plan to launch a new one soon right? should I wait for
> > it?
> > > > >
> > > > > Thanks
> > > > >
> > > > >
> > > > > El jue., 6 feb. 2020 a las 7:53, Piotr Zarzycki (<
> > > > > piotrzarzyck...@gmail.com>)
> > > > > escribió:
> > > > >
> > > > > > Hi Carlos,
> > > > > >
> > > > > > I just tried your changes and I'm a bit farther. Now I'm getting
> > > > > following
> > > > > > errors. It's throwing that errors 

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

If you are using your own SDK (not downloaded trough Moonshine getting
started) you have to add permission to mxmlc file. There is a command on
Mac chmod - try to search using that command on a Google.

Thanks,
Piotr

On Sun, Feb 9, 2020, 5:29 PM Carlos Rovira  wrote:

> Hi,
>
> I installed latest Moonshine nightly. After configuring initial things
> loaded TDJ project. I'm getting Permission denied:
>
> : Moonshine IDE™ 2.5.0
> : Copyright © Prominic.NET, Inc. All rights reserved.
> : Source code is under Apache License, Version 2.0
> : https://github.com/prominic/Moonshine-IDE
> : Uses as3abc (LGPL), as3swf (MIT), fzip (ZLIB), asblocks (Apache License
> 2.0), NativeApplicationUpdater (LGPL)
> : Running on Adobe AIR 28.0.0.125
> : Compiling TourDeJewel
> : SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> : Sending to mxmlx: export
>
>  
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> ROYALE_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven" &&
> export
>
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en" && export
>
> ROYALE_COMPILER_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"&&
> "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> -load-config+=obj/TourDeJewelConfig.xml
> -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> -html-template=src/main/resources/jewel-example-index-template.html
> -js-dynamic-access-unknown-members=true -compiler.targets=JSRoyale
>
> -js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel"
> : /bin/bash:
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc:
> Permission denied
>
> How can I fix it?
>
> Thanks
>
>
> El jue., 6 feb. 2020 a las 17:24, Josh Tynjala ( >)
> escribió:
>
> > Yeah, I don't see why Moonshine is reporting those errors, but VSCode
> does
> > not. If royale-config.xml is referencing SWCs that don't exist, that
> should
> > affect both IDEs.
> >
> > Regardless, like you explained, the same issue should reproduce when
> > compiling from a terminal without Moonshine.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Thu, Feb 6, 2020 at 5:10 AM Piotr Zarzycki  >
> > wrote:
> >
> > > Hi Carlos,
> > >
> > > Yeah it would be pretty great if you could setup Moonshine, but you
> don't
> > > have to do that actually to reproduce the issue. Command which I have
> > > pasted in this thread can be copy and used in Terminal with small path
> > > adjustment. Try it on any project you have using distribution build and
> > for
> > > sure you will get the error.
> > >
> > > In case of Moonshine we have freez code for commits and prepare for
> > > release, we have some internal problems with bamboo build - if it will
> > get
> > > resolved we should have release early next week. You can always try
> > Nightly
> > > build.
> > >
> > > I'm really surprised that VSCode do not throwing the same error - What
> > > could be the case Josh? The only difference is that we are using mxmlc
> > file
> > > and VSCode is probably using jar file, but playerglobal.swc doesn't
> > exists
> > > so both should report same issue.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > czw., 6 lut 2020 o 13:02 Carlos Rovira 
> > > napisał(a):
> > >
> > > > Hi Piotr,
> > > >
> > > > so I think you're a bit closer (not farther ;)), since compiler was
> > > found.
> > > > Now is a matter to find what's missing.
> > > > What's curious for me is VSCode recognizes but Moonshine not. I think
> > the
> > > > problem is each IDE is looking at different things to match a valid
> > SDK,
> > > > and maybe even we could be setting duplicate artifacts in the SDK so
> > > VSCode
> > > > finds all but Moonshine not.
> > > > I'll be setup Moonshine as I have time to try it.
> > > > I think you plan to launch a new one soon right? should I wait for
> it?
> > > >
> > > > Thanks
> > > >
> > > >
> > > > El jue., 6 feb. 2020 a las 7:53, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>)
> > > > escribió:
> > > >
> > > > > Hi Carlos,
> > > > >
> > > > > I just tried your changes and I'm a bit farther. Now I'm getting
> > > > following
> > > > > errors. It's throwing that errors cause in JS only binaries
> prepared
> > by
> > > > ant
> > > > > we have in following location
> > > > > /frameworks/libs/player/{playerbersion}/playerglobal.swc fake
> > > > > playerglobal.swc, so distribution should probably have the same.
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/bin/mxmlc"
> > > > > > -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml
> -debug=true
> > > > > > -source-map=true -compiler.targets=JSRoyale
> > > > > >
> > -js-output="/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject"
> > > > > > : Using Royale Compiler codebase:
> > > > > >
> 

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

Hi Carlos,

>From the logs it doesn't looks like Nightly build, but official release,
unless there is something wrong with the logs.

You'd should have in logs Moonshine 2.6.0 instead 2.5.0.

On Sun, Feb 9, 2020, 5:29 PM Carlos Rovira  wrote:

> Hi,
>
> I installed latest Moonshine nightly. After configuring initial things
> loaded TDJ project. I'm getting Permission denied:
>
> : Moonshine IDE™ 2.5.0
> : Copyright © Prominic.NET, Inc. All rights reserved.
> : Source code is under Apache License, Version 2.0
> : https://github.com/prominic/Moonshine-IDE
> : Uses as3abc (LGPL), as3swf (MIT), fzip (ZLIB), asblocks (Apache License
> 2.0), NativeApplicationUpdater (LGPL)
> : Running on Adobe AIR 28.0.0.125
> : Compiling TourDeJewel
> : SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
> : Sending to mxmlx: export
>
>  
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> ROYALE_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven" &&
> export
>
> royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
> SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en" && export
>
> ROYALE_COMPILER_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"&&
> "/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
> -load-config+=obj/TourDeJewelConfig.xml
> -theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
> -html-template=src/main/resources/jewel-example-index-template.html
> -js-dynamic-access-unknown-members=true -compiler.targets=JSRoyale
>
> -js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel"
> : /bin/bash:
> /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc:
> Permission denied
>
> How can I fix it?
>
> Thanks
>
>
> El jue., 6 feb. 2020 a las 17:24, Josh Tynjala ( >)
> escribió:
>
> > Yeah, I don't see why Moonshine is reporting those errors, but VSCode
> does
> > not. If royale-config.xml is referencing SWCs that don't exist, that
> should
> > affect both IDEs.
> >
> > Regardless, like you explained, the same issue should reproduce when
> > compiling from a terminal without Moonshine.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Thu, Feb 6, 2020 at 5:10 AM Piotr Zarzycki  >
> > wrote:
> >
> > > Hi Carlos,
> > >
> > > Yeah it would be pretty great if you could setup Moonshine, but you
> don't
> > > have to do that actually to reproduce the issue. Command which I have
> > > pasted in this thread can be copy and used in Terminal with small path
> > > adjustment. Try it on any project you have using distribution build and
> > for
> > > sure you will get the error.
> > >
> > > In case of Moonshine we have freez code for commits and prepare for
> > > release, we have some internal problems with bamboo build - if it will
> > get
> > > resolved we should have release early next week. You can always try
> > Nightly
> > > build.
> > >
> > > I'm really surprised that VSCode do not throwing the same error - What
> > > could be the case Josh? The only difference is that we are using mxmlc
> > file
> > > and VSCode is probably using jar file, but playerglobal.swc doesn't
> > exists
> > > so both should report same issue.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > czw., 6 lut 2020 o 13:02 Carlos Rovira 
> > > napisał(a):
> > >
> > > > Hi Piotr,
> > > >
> > > > so I think you're a bit closer (not farther ;)), since compiler was
> > > found.
> > > > Now is a matter to find what's missing.
> > > > What's curious for me is VSCode recognizes but Moonshine not. I think
> > the
> > > > problem is each IDE is looking at different things to match a valid
> > SDK,
> > > > and maybe even we could be setting duplicate artifacts in the SDK so
> > > VSCode
> > > > finds all but Moonshine not.
> > > > I'll be setup Moonshine as I have time to try it.
> > > > I think you plan to launch a new one soon right? should I wait for
> it?
> > > >
> > > > Thanks
> > > >
> > > >
> > > > El jue., 6 feb. 2020 a las 7:53, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>)
> > > > escribió:
> > > >
> > > > > Hi Carlos,
> > > > >
> > > > > I just tried your changes and I'm a bit farther. Now I'm getting
> > > > following
> > > > > errors. It's throwing that errors cause in JS only binaries
> prepared
> > by
> > > > ant
> > > > > we have in following location
> > > > > /frameworks/libs/player/{playerbersion}/playerglobal.swc fake
> > > > > playerglobal.swc, so distribution should probably have the same.
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/bin/mxmlc"
> > > > > > -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml
> -debug=true
> > > > > > -source-map=true -compiler.targets=JSRoyale
> > > > > >
> > -js-output="/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject"
> > > > > > : Using Royale Compiler codebase:
> > > > > >
> 

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi,

I installed latest Moonshine nightly. After configuring initial things
loaded TDJ project. I'm getting Permission denied:

: Moonshine IDE™ 2.5.0
: Copyright © Prominic.NET, Inc. All rights reserved.
: Source code is under Apache License, Version 2.0
: https://github.com/prominic/Moonshine-IDE
: Uses as3abc (LGPL), as3swf (MIT), fzip (ZLIB), asblocks (Apache License
2.0), NativeApplicationUpdater (LGPL)
: Running on Adobe AIR 28.0.0.125
: Compiling TourDeJewel
: SDK path: /Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven
: Sending to mxmlx: export
 royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
ROYALE_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven" &&
export
royalelib="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/frameworks"
SETUP_SH_VMARGS="-Duser.language=en -Duser.region=en" && export
ROYALE_COMPILER_HOME="/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven"&&
"/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc"
-load-config+=obj/TourDeJewelConfig.xml
-theme=${royalelib}/themes/JewelTheme/src/main/resources/defaults.css
-html-template=src/main/resources/jewel-example-index-template.html
-js-dynamic-access-unknown-members=true -compiler.targets=JSRoyale
-js-output="/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/TourDeJewel"
: /bin/bash:
/Users/carlosrovira/Dev/Royale/Sdks/apache-royale-maven/js/bin/mxmlc:
Permission denied

How can I fix it?

Thanks


El jue., 6 feb. 2020 a las 17:24, Josh Tynjala ()
escribió:

> Yeah, I don't see why Moonshine is reporting those errors, but VSCode does
> not. If royale-config.xml is referencing SWCs that don't exist, that should
> affect both IDEs.
>
> Regardless, like you explained, the same issue should reproduce when
> compiling from a terminal without Moonshine.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Thu, Feb 6, 2020 at 5:10 AM Piotr Zarzycki 
> wrote:
>
> > Hi Carlos,
> >
> > Yeah it would be pretty great if you could setup Moonshine, but you don't
> > have to do that actually to reproduce the issue. Command which I have
> > pasted in this thread can be copy and used in Terminal with small path
> > adjustment. Try it on any project you have using distribution build and
> for
> > sure you will get the error.
> >
> > In case of Moonshine we have freez code for commits and prepare for
> > release, we have some internal problems with bamboo build - if it will
> get
> > resolved we should have release early next week. You can always try
> Nightly
> > build.
> >
> > I'm really surprised that VSCode do not throwing the same error - What
> > could be the case Josh? The only difference is that we are using mxmlc
> file
> > and VSCode is probably using jar file, but playerglobal.swc doesn't
> exists
> > so both should report same issue.
> >
> > Thanks,
> > Piotr
> >
> > czw., 6 lut 2020 o 13:02 Carlos Rovira 
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > so I think you're a bit closer (not farther ;)), since compiler was
> > found.
> > > Now is a matter to find what's missing.
> > > What's curious for me is VSCode recognizes but Moonshine not. I think
> the
> > > problem is each IDE is looking at different things to match a valid
> SDK,
> > > and maybe even we could be setting duplicate artifacts in the SDK so
> > VSCode
> > > finds all but Moonshine not.
> > > I'll be setup Moonshine as I have time to try it.
> > > I think you plan to launch a new one soon right? should I wait for it?
> > >
> > > Thanks
> > >
> > >
> > > El jue., 6 feb. 2020 a las 7:53, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>)
> > > escribió:
> > >
> > > > Hi Carlos,
> > > >
> > > > I just tried your changes and I'm a bit farther. Now I'm getting
> > > following
> > > > errors. It's throwing that errors cause in JS only binaries prepared
> by
> > > ant
> > > > we have in following location
> > > > /frameworks/libs/player/{playerbersion}/playerglobal.swc fake
> > > > playerglobal.swc, so distribution should probably have the same.
> > > >
> > > >
> > > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/bin/mxmlc"
> > > > > -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml -debug=true
> > > > > -source-map=true -compiler.targets=JSRoyale
> > > > >
> -js-output="/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject"
> > > > > : Using Royale Compiler codebase:
> > > > > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > > > > : Using Royale SDK:
> > > > > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > > > > : MXMLJSC
> > > > > :
> > > > >
> > > >
> > >
> >
> +royalelib=/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks
> > > > > :
> > > > >
> > > >
> > >
> >
> -sdk-js-lib=/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/js/Royale/generated-sources
> > > > > : 

Re: Maven Distribution SDK fixed and working for IDEs

[Josh Tynjala]

Yeah, I don't see why Moonshine is reporting those errors, but VSCode does
not. If royale-config.xml is referencing SWCs that don't exist, that should
affect both IDEs.

Regardless, like you explained, the same issue should reproduce when
compiling from a terminal without Moonshine.

--
Josh Tynjala
Bowler Hat LLC 


On Thu, Feb 6, 2020 at 5:10 AM Piotr Zarzycki 
wrote:

> Hi Carlos,
>
> Yeah it would be pretty great if you could setup Moonshine, but you don't
> have to do that actually to reproduce the issue. Command which I have
> pasted in this thread can be copy and used in Terminal with small path
> adjustment. Try it on any project you have using distribution build and for
> sure you will get the error.
>
> In case of Moonshine we have freez code for commits and prepare for
> release, we have some internal problems with bamboo build - if it will get
> resolved we should have release early next week. You can always try Nightly
> build.
>
> I'm really surprised that VSCode do not throwing the same error - What
> could be the case Josh? The only difference is that we are using mxmlc file
> and VSCode is probably using jar file, but playerglobal.swc doesn't exists
> so both should report same issue.
>
> Thanks,
> Piotr
>
> czw., 6 lut 2020 o 13:02 Carlos Rovira 
> napisał(a):
>
> > Hi Piotr,
> >
> > so I think you're a bit closer (not farther ;)), since compiler was
> found.
> > Now is a matter to find what's missing.
> > What's curious for me is VSCode recognizes but Moonshine not. I think the
> > problem is each IDE is looking at different things to match a valid SDK,
> > and maybe even we could be setting duplicate artifacts in the SDK so
> VSCode
> > finds all but Moonshine not.
> > I'll be setup Moonshine as I have time to try it.
> > I think you plan to launch a new one soon right? should I wait for it?
> >
> > Thanks
> >
> >
> > El jue., 6 feb. 2020 a las 7:53, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>)
> > escribió:
> >
> > > Hi Carlos,
> > >
> > > I just tried your changes and I'm a bit farther. Now I'm getting
> > following
> > > errors. It's throwing that errors cause in JS only binaries prepared by
> > ant
> > > we have in following location
> > > /frameworks/libs/player/{playerbersion}/playerglobal.swc fake
> > > playerglobal.swc, so distribution should probably have the same.
> > >
> > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/bin/mxmlc"
> > > > -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml -debug=true
> > > > -source-map=true -compiler.targets=JSRoyale
> > > > -js-output="/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject"
> > > > : Using Royale Compiler codebase:
> > > > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > > > : Using Royale SDK:
> > > > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > > > : MXMLJSC
> > > > :
> > > >
> > >
> >
> +royalelib=/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks
> > > > :
> > > >
> > >
> >
> -sdk-js-lib=/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/js/Royale/generated-sources
> > > > : -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml
> > > > : -debug=true
> > > > : -source-map=true
> > > > : -compiler.targets=JSRoyale
> > > > : -js-output=/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject
> > > > :
> > > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(74):
> > > > col: 0 Error: unable to open
> > > >
> > >
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/libs/player/20.0/playerglobal.swc'.
> > > > :
> > > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > > > (line: 74)
> > > > :   
> > > > :
> > > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(81):
> > > > col: 0 Error: unable to open
> > > >
> > >
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/libs/royale-typedefs-js-0.9.7-SNAPSHOT-typedefs.swc'.
> > > > :
> > > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > > > (line: 81)
> > > > :   
> > > > :
> > > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(81):
> > > > col: 0 Error: unable to open
> > > >
> > >
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/libs/royale-typedefs-gcl-0.9.7-SNAPSHOT-typedefs.swc'.
> > > > :
> > > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > > > (line: 81)
> > > > :   
> > > > :
> > > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(99):
> > > > col: 0 Error: 

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

Hi Carlos,

Yeah it would be pretty great if you could setup Moonshine, but you don't
have to do that actually to reproduce the issue. Command which I have
pasted in this thread can be copy and used in Terminal with small path
adjustment. Try it on any project you have using distribution build and for
sure you will get the error.

In case of Moonshine we have freez code for commits and prepare for
release, we have some internal problems with bamboo build - if it will get
resolved we should have release early next week. You can always try Nightly
build.

I'm really surprised that VSCode do not throwing the same error - What
could be the case Josh? The only difference is that we are using mxmlc file
and VSCode is probably using jar file, but playerglobal.swc doesn't exists
so both should report same issue.

Thanks,
Piotr

czw., 6 lut 2020 o 13:02 Carlos Rovira  napisał(a):

> Hi Piotr,
>
> so I think you're a bit closer (not farther ;)), since compiler was found.
> Now is a matter to find what's missing.
> What's curious for me is VSCode recognizes but Moonshine not. I think the
> problem is each IDE is looking at different things to match a valid SDK,
> and maybe even we could be setting duplicate artifacts in the SDK so VSCode
> finds all but Moonshine not.
> I'll be setup Moonshine as I have time to try it.
> I think you plan to launch a new one soon right? should I wait for it?
>
> Thanks
>
>
> El jue., 6 feb. 2020 a las 7:53, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Hi Carlos,
> >
> > I just tried your changes and I'm a bit farther. Now I'm getting
> following
> > errors. It's throwing that errors cause in JS only binaries prepared by
> ant
> > we have in following location
> > /frameworks/libs/player/{playerbersion}/playerglobal.swc fake
> > playerglobal.swc, so distribution should probably have the same.
> >
> >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/bin/mxmlc"
> > > -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml -debug=true
> > > -source-map=true -compiler.targets=JSRoyale
> > > -js-output="/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject"
> > > : Using Royale Compiler codebase:
> > > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > > : Using Royale SDK:
> > > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > > : MXMLJSC
> > > :
> > >
> >
> +royalelib=/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks
> > > :
> > >
> >
> -sdk-js-lib=/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/js/Royale/generated-sources
> > > : -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml
> > > : -debug=true
> > > : -source-map=true
> > > : -compiler.targets=JSRoyale
> > > : -js-output=/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject
> > > :
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(74):
> > > col: 0 Error: unable to open
> > >
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/libs/player/20.0/playerglobal.swc'.
> > > :
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > > (line: 74)
> > > :   
> > > :
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(81):
> > > col: 0 Error: unable to open
> > >
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/libs/royale-typedefs-js-0.9.7-SNAPSHOT-typedefs.swc'.
> > > :
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > > (line: 81)
> > > :   
> > > :
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(81):
> > > col: 0 Error: unable to open
> > >
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/libs/royale-typedefs-gcl-0.9.7-SNAPSHOT-typedefs.swc'.
> > > :
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > > (line: 81)
> > > :   
> > > :
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(99):
> > > col: 0 Error: unable to open
> > >
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/libs/player/20.0'.
> > > :
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > > (line: 99)
> > > :   
> > > : 1.034449561 seconds
> >
> >
> > Thanks,
> > Piotr
> >
> > czw., 6 lut 2020 o 00:43 Carlos Rovira 
> > napisał(a):
> >
> > > Thanks Josh for pointing that out I think I got it.
> > >
> > > @Piotr Zarzycki  please try with my latest
> > > commit. I couldn't test myself, but I think it should work now for
> > > Moonshine.
> > > VSCode still work with this changes.
> > >
> > > Thanks
> > >

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi Piotr,

so I think you're a bit closer (not farther ;)), since compiler was found.
Now is a matter to find what's missing.
What's curious for me is VSCode recognizes but Moonshine not. I think the
problem is each IDE is looking at different things to match a valid SDK,
and maybe even we could be setting duplicate artifacts in the SDK so VSCode
finds all but Moonshine not.
I'll be setup Moonshine as I have time to try it.
I think you plan to launch a new one soon right? should I wait for it?

Thanks


El jue., 6 feb. 2020 a las 7:53, Piotr Zarzycki ()
escribió:

> Hi Carlos,
>
> I just tried your changes and I'm a bit farther. Now I'm getting following
> errors. It's throwing that errors cause in JS only binaries prepared by ant
> we have in following location
> /frameworks/libs/player/{playerbersion}/playerglobal.swc fake
> playerglobal.swc, so distribution should probably have the same.
>
>
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/bin/mxmlc"
> > -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml -debug=true
> > -source-map=true -compiler.targets=JSRoyale
> > -js-output="/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject"
> > : Using Royale Compiler codebase:
> > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > : Using Royale SDK:
> > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > : MXMLJSC
> > :
> >
> +royalelib=/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks
> > :
> >
> -sdk-js-lib=/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/js/Royale/generated-sources
> > : -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml
> > : -debug=true
> > : -source-map=true
> > : -compiler.targets=JSRoyale
> > : -js-output=/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(74):
> > col: 0 Error: unable to open
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/libs/player/20.0/playerglobal.swc'.
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > (line: 74)
> > :   
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(81):
> > col: 0 Error: unable to open
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/libs/royale-typedefs-js-0.9.7-SNAPSHOT-typedefs.swc'.
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > (line: 81)
> > :   
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(81):
> > col: 0 Error: unable to open
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/libs/royale-typedefs-gcl-0.9.7-SNAPSHOT-typedefs.swc'.
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > (line: 81)
> > :   
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(99):
> > col: 0 Error: unable to open
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/libs/player/20.0'.
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > (line: 99)
> > :   
> > : 1.034449561 seconds
>
>
> Thanks,
> Piotr
>
> czw., 6 lut 2020 o 00:43 Carlos Rovira 
> napisał(a):
>
> > Thanks Josh for pointing that out I think I got it.
> >
> > @Piotr Zarzycki  please try with my latest
> > commit. I couldn't test myself, but I think it should work now for
> > Moonshine.
> > VSCode still work with this changes.
> >
> > Thanks
> >
> > Carlos
> >
> >
> >
> > El mié., 5 feb. 2020 a las 19:43, Josh Tynjala (<
> joshtynj...@bowlerhat.dev>)
> > escribió:
> >
> >> If I had to guess, this classpath is wrong:
> >>
> >> args4j.jar org.json.jar compiler-jx-0.9.7-SNAPSHOT.jar >> Class-Path>
> >>
> >>
> >>
> https://github.com/apache/royale-asjs/blob/develop/distribution/jars/compiler-mxmljsc/pom.xml
> >>
> >> I think that the names of those JAR files all include a version number
> in
> >> the Maven distribution.
> >>
> >> --
> >> Josh Tynjala
> >> Bowler Hat LLC 
> >>
> >>
> >> On Wed, Feb 5, 2020 at 10:17 AM Carlos Rovira 
> >> wrote:
> >>
> >> > ok didn't notice.
> >> > So maybe is a classpath problem?
> >> > It's clear that VSCode goes to the same place and find it since mxmlc
> >> is a
> >> > dummy jar that has exactly that class, but Moonshine goes and didn't
> >> find
> >> > it.
> >> > If not any clue what could be happening?
> >> > Thanks
> >> >
> >> > El mié., 5 feb. 2020 a las 16:53, Piotr Zarzycki (<
> >> > piotrzarzyck...@gmail.com>)
> >> > escribió:
> >> >
> >> > > Exactly and I can confirm that mxmlc is in place.
> >> > >
> >> > > śr., 5 lut 

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Hi Alex,

a part from files, there could be differences with MANIFEST in jar files.
In the other hand, I lack the knowledge of how to use the reproducible
feature or how to do that comparison.
Anyway, I think it's a matter of solve little things at this point.

Thanks
Carlos


El jue., 6 feb. 2020 a las 9:41, Alex Harui ()
escribió:

> A reminder that because we have reproducible binaries, it is theoretically
> possible to diff the maven vs ant folders instead of making guesses as to
> when the maven version is correct.
>
> HTH,
> -Alex
>
> On 2/5/20, 10:53 PM, "Piotr Zarzycki"  wrote:
>
> Hi Carlos,
>
> I just tried your changes and I'm a bit farther. Now I'm getting
> following
> errors. It's throwing that errors cause in JS only binaries prepared
> by ant
> we have in following location
> /frameworks/libs/player/{playerbersion}/playerglobal.swc fake
> playerglobal.swc, so distribution should probably have the same.
>
>
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/bin/mxmlc"
> > -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml -debug=true
> > -source-map=true -compiler.targets=JSRoyale
> > -js-output="/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject"
> > : Using Royale Compiler codebase:
> > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > : Using Royale SDK:
> > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > : MXMLJSC
> > :
> >
> +royalelib=/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks
> > :
> >
> -sdk-js-lib=/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/js/Royale/generated-sources
> > : -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml
> > : -debug=true
> > : -source-map=true
> > : -compiler.targets=JSRoyale
> > : -js-output=/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(74):
> > col: 0 Error: unable to open
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/libs/player/20.0/playerglobal.swc'.
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > (line: 74)
> > :   
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(81):
> > col: 0 Error: unable to open
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/libs/royale-typedefs-js-0.9.7-SNAPSHOT-typedefs.swc'.
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > (line: 81)
> > :   
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(81):
> > col: 0 Error: unable to open
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/libs/royale-typedefs-gcl-0.9.7-SNAPSHOT-typedefs.swc'.
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > (line: 81)
> > :   
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(99):
> > col: 0 Error: unable to open
> >
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/libs/player/20.0'.
> > :
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> > (line: 99)
> > :   
> > : 1.034449561 seconds
>
>
> Thanks,
> Piotr
>
> czw., 6 lut 2020 o 00:43 Carlos Rovira 
> napisał(a):
>
> > Thanks Josh for pointing that out I think I got it.
> >
> > @Piotr Zarzycki  please try with my
> latest
> > commit. I couldn't test myself, but I think it should work now for
> > Moonshine.
> > VSCode still work with this changes.
> >
> > Thanks
> >
> > Carlos
> >
> >
> >
> > El mié., 5 feb. 2020 a las 19:43, Josh Tynjala (<
> joshtynj...@bowlerhat.dev>)
> > escribió:
> >
> >> If I had to guess, this classpath is wrong:
> >>
> >> args4j.jar org.json.jar compiler-jx-0.9.7-SNAPSHOT.jar >> Class-Path>
> >>
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Fdevelop%2Fdistribution%2Fjars%2Fcompiler-mxmljsc%2Fpom.xmldata=02%7C01%7Caharui%40adobe.com%7C0d6a5b01d34e4f49d84508d7aad15558%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637165688375141803sdata=25d%2FJXF5cAHZsPoJ9iGBDowK26hTcgLrZoPSCYOsxLA%3Dreserved=0
> >>
> >> I think that the names of those JAR files all include a version
> number in
> >> the Maven distribution.
> >>
> >> --
> >> Josh 

Re: Maven Distribution SDK fixed and working for IDEs

[Alex Harui]

A reminder that because we have reproducible binaries, it is theoretically 
possible to diff the maven vs ant folders instead of making guesses as to when 
the maven version is correct.

HTH,
-Alex

On 2/5/20, 10:53 PM, "Piotr Zarzycki"  wrote:

Hi Carlos,

I just tried your changes and I'm a bit farther. Now I'm getting following
errors. It's throwing that errors cause in JS only binaries prepared by ant
we have in following location
/frameworks/libs/player/{playerbersion}/playerglobal.swc fake
playerglobal.swc, so distribution should probably have the same.


/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/bin/mxmlc"
> -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml -debug=true
> -source-map=true -compiler.targets=JSRoyale
> -js-output="/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject"
> : Using Royale Compiler codebase:
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> : Using Royale SDK:
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> : MXMLJSC
> :
> 
+royalelib=/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks
> :
> 
-sdk-js-lib=/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/js/Royale/generated-sources
> : -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml
> : -debug=true
> : -source-map=true
> : -compiler.targets=JSRoyale
> : -js-output=/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject
> :
> 
/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(74):
> col: 0 Error: unable to open
> 
'/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/libs/player/20.0/playerglobal.swc'.
> :
> 
/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> (line: 74)
> :   
> :
> 
/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(81):
> col: 0 Error: unable to open
> 
'/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/libs/royale-typedefs-js-0.9.7-SNAPSHOT-typedefs.swc'.
> :
> 
/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> (line: 81)
> :   
> :
> 
/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(81):
> col: 0 Error: unable to open
> 
'/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/libs/royale-typedefs-gcl-0.9.7-SNAPSHOT-typedefs.swc'.
> :
> 
/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> (line: 81)
> :   
> :
> 
/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(99):
> col: 0 Error: unable to open
> 
'/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/libs/player/20.0'.
> :
> 
/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> (line: 99)
> :   
> : 1.034449561 seconds


Thanks,
Piotr

czw., 6 lut 2020 o 00:43 Carlos Rovira  napisał(a):

> Thanks Josh for pointing that out I think I got it.
>
> @Piotr Zarzycki  please try with my latest
> commit. I couldn't test myself, but I think it should work now for
> Moonshine.
> VSCode still work with this changes.
>
> Thanks
>
> Carlos
>
>
>
> El mié., 5 feb. 2020 a las 19:43, Josh Tynjala 
()
> escribió:
>
>> If I had to guess, this classpath is wrong:
>>
>> args4j.jar org.json.jar compiler-jx-0.9.7-SNAPSHOT.jar> Class-Path>
>>
>>
>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Fdevelop%2Fdistribution%2Fjars%2Fcompiler-mxmljsc%2Fpom.xmldata=02%7C01%7Caharui%40adobe.com%7C0d6a5b01d34e4f49d84508d7aad15558%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637165688375141803sdata=25d%2FJXF5cAHZsPoJ9iGBDowK26hTcgLrZoPSCYOsxLA%3Dreserved=0
>>
>> I think that the names of those JAR files all include a version number in
>> the Maven distribution.
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC 

>>
>>
>> On Wed, Feb 5, 2020 at 10:17 AM Carlos Rovira 
>> wrote:
>>
>> > ok didn't notice.
>> > So maybe is a classpath problem?
>> > It's clear that VSCode goes to the same place and find it since mxmlc
>> is a
>> > 

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

Hi Carlos,

I just tried your changes and I'm a bit farther. Now I'm getting following
errors. It's throwing that errors cause in JS only binaries prepared by ant
we have in following location
/frameworks/libs/player/{playerbersion}/playerglobal.swc fake
playerglobal.swc, so distribution should probably have the same.

/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/bin/mxmlc"
> -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml -debug=true
> -source-map=true -compiler.targets=JSRoyale
> -js-output="/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject"
> : Using Royale Compiler codebase:
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> : Using Royale SDK:
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> : MXMLJSC
> :
> +royalelib=/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks
> :
> -sdk-js-lib=/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/js/Royale/generated-sources
> : -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml
> : -debug=true
> : -source-map=true
> : -compiler.targets=JSRoyale
> : -js-output=/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject
> :
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(74):
> col: 0 Error: unable to open
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/libs/player/20.0/playerglobal.swc'.
> :
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> (line: 74)
> :   
> :
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(81):
> col: 0 Error: unable to open
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/libs/royale-typedefs-js-0.9.7-SNAPSHOT-typedefs.swc'.
> :
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> (line: 81)
> :   
> :
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(81):
> col: 0 Error: unable to open
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/libs/royale-typedefs-gcl-0.9.7-SNAPSHOT-typedefs.swc'.
> :
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> (line: 81)
> :   
> :
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml(99):
> col: 0 Error: unable to open
> '/Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/libs/player/20.0'.
> :
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/frameworks/royale-config.xml
> (line: 99)
> :   
> : 1.034449561 seconds


Thanks,
Piotr

czw., 6 lut 2020 o 00:43 Carlos Rovira  napisał(a):

> Thanks Josh for pointing that out I think I got it.
>
> @Piotr Zarzycki  please try with my latest
> commit. I couldn't test myself, but I think it should work now for
> Moonshine.
> VSCode still work with this changes.
>
> Thanks
>
> Carlos
>
>
>
> El mié., 5 feb. 2020 a las 19:43, Josh Tynjala ()
> escribió:
>
>> If I had to guess, this classpath is wrong:
>>
>> args4j.jar org.json.jar compiler-jx-0.9.7-SNAPSHOT.jar> Class-Path>
>>
>>
>> https://github.com/apache/royale-asjs/blob/develop/distribution/jars/compiler-mxmljsc/pom.xml
>>
>> I think that the names of those JAR files all include a version number in
>> the Maven distribution.
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC 
>>
>>
>> On Wed, Feb 5, 2020 at 10:17 AM Carlos Rovira 
>> wrote:
>>
>> > ok didn't notice.
>> > So maybe is a classpath problem?
>> > It's clear that VSCode goes to the same place and find it since mxmlc
>> is a
>> > dummy jar that has exactly that class, but Moonshine goes and didn't
>> find
>> > it.
>> > If not any clue what could be happening?
>> > Thanks
>> >
>> > El mié., 5 feb. 2020 a las 16:53, Piotr Zarzycki (<
>> > piotrzarzyck...@gmail.com>)
>> > escribió:
>> >
>> > > Exactly and I can confirm that mxmlc is in place.
>> > >
>> > > śr., 5 lut 2020 o 16:49 Josh Tynjala 
>> > > napisał(a):
>> > >
>> > > > You can see from the output that Moonshine is calling the command
>> line
>> > > > scripts in js/bin.
>> > > >
>> > > > --
>> > > > Josh Tynjala
>> > > > Bowler Hat LLC 
>> > > >
>> > > >
>> > > > On Wed, Feb 5, 2020 at 7:45 AM Carlos Rovira <
>> carlosrov...@apache.org>
>> > > > wrote:
>> > > >
>> > > > > Hi Piotr,
>> > > > >
>> > > > > That was a problem I had with VSCode when started to work on fix
>> SDK
>> > > for
>> > > > > IDE.
>> > > > > Josh told me that VSCode tries to find that class in
>> > /js/lib/mxmlc.jar
>> > > > > it needs /js/lib/mxmlc.jar too
>> > > > >
>> > > > > Maybe Moonshine is looking in other path?
>> > > > >
>> > > > > Thanks
>> > > > >
>> > > > > El mar., 4 feb. 2020 a las 14:43, Piotr Zarzycki (<
>> > > > > piotrzarzyck...@gmail.com>)
>> > > > > 

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

Thanks Josh for pointing that out I think I got it.

@Piotr Zarzycki  please try with my latest
commit. I couldn't test myself, but I think it should work now for
Moonshine.
VSCode still work with this changes.

Thanks

Carlos



El mié., 5 feb. 2020 a las 19:43, Josh Tynjala ()
escribió:

> If I had to guess, this classpath is wrong:
>
> args4j.jar org.json.jar compiler-jx-0.9.7-SNAPSHOT.jar Class-Path>
>
>
> https://github.com/apache/royale-asjs/blob/develop/distribution/jars/compiler-mxmljsc/pom.xml
>
> I think that the names of those JAR files all include a version number in
> the Maven distribution.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Wed, Feb 5, 2020 at 10:17 AM Carlos Rovira 
> wrote:
>
> > ok didn't notice.
> > So maybe is a classpath problem?
> > It's clear that VSCode goes to the same place and find it since mxmlc is
> a
> > dummy jar that has exactly that class, but Moonshine goes and didn't find
> > it.
> > If not any clue what could be happening?
> > Thanks
> >
> > El mié., 5 feb. 2020 a las 16:53, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>)
> > escribió:
> >
> > > Exactly and I can confirm that mxmlc is in place.
> > >
> > > śr., 5 lut 2020 o 16:49 Josh Tynjala 
> > > napisał(a):
> > >
> > > > You can see from the output that Moonshine is calling the command
> line
> > > > scripts in js/bin.
> > > >
> > > > --
> > > > Josh Tynjala
> > > > Bowler Hat LLC 
> > > >
> > > >
> > > > On Wed, Feb 5, 2020 at 7:45 AM Carlos Rovira <
> carlosrov...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > That was a problem I had with VSCode when started to work on fix
> SDK
> > > for
> > > > > IDE.
> > > > > Josh told me that VSCode tries to find that class in
> > /js/lib/mxmlc.jar
> > > > > it needs /js/lib/mxmlc.jar too
> > > > >
> > > > > Maybe Moonshine is looking in other path?
> > > > >
> > > > > Thanks
> > > > >
> > > > > El mar., 4 feb. 2020 a las 14:43, Piotr Zarzycki (<
> > > > > piotrzarzyck...@gmail.com>)
> > > > > escribió:
> > > > >
> > > > > > Hi Carlos,
> > > > > >
> > > > > > I have build on my Mac SDK and tried in Nightly Build of
> > Moonshine. I
> > > > > > cannot build Hello World. I'm getting following error:
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/bin/mxmlc
> > > > > > -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml
> -debug=true
> > > > > > -source-map=true -compiler.targets=JSRoyale
> > > > > >
> > -js-output="/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject"
> > > > > > : Using Royale Compiler codebase:
> > > > > >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > > > > > : Using Royale SDK:
> > > > > >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > > > > > : Error: Could not find or load main class
> > > > > > org.apache.royale.compiler.clients.MXMLJSC
> > > > > >
> > > > > >
> > > > > >
> > > > > > czw., 23 sty 2020 o 16:26 Carlos Rovira  >
> > > > > > napisał(a):
> > > > > >
> > > > > > > Hi Piotr,
> > > > > > >
> > > > > > > right, are simplified too and does not have any profile or
> > > variable.
> > > > > > >
> > > > > > > "-U clean install" is standard maven commands, nothing to do
> with
> > > us
> > > > in
> > > > > > > particular, so you can left that
> > > > > > > "-P main,utils" are not needed anymore, since now there's no
> > > > > > > differentiation between a "first build" against rest of builds.
> > > > > > >
> > > > > > >
> > > > > > > El jue., 23 ene. 2020 a las 15:32, Piotr Zarzycki (<
> > > > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > > > >
> > > > > > > > Hi Carlos,
> > > > > > > >
> > > > > > > > Builds for framework is updated. What about compiler and
> > > typedefs ?
> > > > > For
> > > > > > > > compiler on the server we have:
> > > > > > > >
> > > > > > > > -U clean install
> > > > > > > > -P -main,utils
> > > > > > > >
> > > > > > > > It looks like that those profiles also deprecated - can you
> > > > confirm ?
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Piotr
> > > > > > > >
> > > > > > > > śr., 22 sty 2020 o 18:37 Carlos Rovira <
> > carlosrov...@apache.org>
> > > > > > > > napisał(a):
> > > > > > > >
> > > > > > > > > Hi Piotr,
> > > > > > > > >
> > > > > > > > > it surprise me that due all the changes done in maven
> > > builds.a.o
> > > > > was
> > > > > > > not
> > > > > > > > > failing. I've even didn't repare that will need to be
> > updated.
> > > > > > > > >
> > > > > > > > > These profiles does not exist anymore:
> > > > > > > > >
> > > > > > >
> > > > >
> > >
> generate-swf,generate-swcs-for-swf,main,build-distribution,build-examples
> > > > > > > > >
> > > > > > > > > Here's the updated doc for maven simplified [1]
> > > > > > > > >
> > > > > > > > > In sort:
> > > > > > > > >
> > > > > > > > > 1.- Only env var needed in Maven now is
> FLASHPLAYER_DEBUGGER
> > > > > > > > 

Re: Maven Distribution SDK fixed and working for IDEs

[Josh Tynjala]

If I had to guess, this classpath is wrong:

args4j.jar org.json.jar compiler-jx-0.9.7-SNAPSHOT.jar

https://github.com/apache/royale-asjs/blob/develop/distribution/jars/compiler-mxmljsc/pom.xml

I think that the names of those JAR files all include a version number in
the Maven distribution.

--
Josh Tynjala
Bowler Hat LLC 


On Wed, Feb 5, 2020 at 10:17 AM Carlos Rovira 
wrote:

> ok didn't notice.
> So maybe is a classpath problem?
> It's clear that VSCode goes to the same place and find it since mxmlc is a
> dummy jar that has exactly that class, but Moonshine goes and didn't find
> it.
> If not any clue what could be happening?
> Thanks
>
> El mié., 5 feb. 2020 a las 16:53, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Exactly and I can confirm that mxmlc is in place.
> >
> > śr., 5 lut 2020 o 16:49 Josh Tynjala 
> > napisał(a):
> >
> > > You can see from the output that Moonshine is calling the command line
> > > scripts in js/bin.
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC 
> > >
> > >
> > > On Wed, Feb 5, 2020 at 7:45 AM Carlos Rovira 
> > > wrote:
> > >
> > > > Hi Piotr,
> > > >
> > > > That was a problem I had with VSCode when started to work on fix SDK
> > for
> > > > IDE.
> > > > Josh told me that VSCode tries to find that class in
> /js/lib/mxmlc.jar
> > > > it needs /js/lib/mxmlc.jar too
> > > >
> > > > Maybe Moonshine is looking in other path?
> > > >
> > > > Thanks
> > > >
> > > > El mar., 4 feb. 2020 a las 14:43, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>)
> > > > escribió:
> > > >
> > > > > Hi Carlos,
> > > > >
> > > > > I have build on my Mac SDK and tried in Nightly Build of
> Moonshine. I
> > > > > cannot build Hello World. I'm getting following error:
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/bin/mxmlc
> > > > > -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml -debug=true
> > > > > -source-map=true -compiler.targets=JSRoyale
> > > > >
> -js-output="/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject"
> > > > > : Using Royale Compiler codebase:
> > > > > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > > > > : Using Royale SDK:
> > > > > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > > > > : Error: Could not find or load main class
> > > > > org.apache.royale.compiler.clients.MXMLJSC
> > > > >
> > > > >
> > > > >
> > > > > czw., 23 sty 2020 o 16:26 Carlos Rovira 
> > > > > napisał(a):
> > > > >
> > > > > > Hi Piotr,
> > > > > >
> > > > > > right, are simplified too and does not have any profile or
> > variable.
> > > > > >
> > > > > > "-U clean install" is standard maven commands, nothing to do with
> > us
> > > in
> > > > > > particular, so you can left that
> > > > > > "-P main,utils" are not needed anymore, since now there's no
> > > > > > differentiation between a "first build" against rest of builds.
> > > > > >
> > > > > >
> > > > > > El jue., 23 ene. 2020 a las 15:32, Piotr Zarzycki (<
> > > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > > >
> > > > > > > Hi Carlos,
> > > > > > >
> > > > > > > Builds for framework is updated. What about compiler and
> > typedefs ?
> > > > For
> > > > > > > compiler on the server we have:
> > > > > > >
> > > > > > > -U clean install
> > > > > > > -P -main,utils
> > > > > > >
> > > > > > > It looks like that those profiles also deprecated - can you
> > > confirm ?
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Piotr
> > > > > > >
> > > > > > > śr., 22 sty 2020 o 18:37 Carlos Rovira <
> carlosrov...@apache.org>
> > > > > > > napisał(a):
> > > > > > >
> > > > > > > > Hi Piotr,
> > > > > > > >
> > > > > > > > it surprise me that due all the changes done in maven
> > builds.a.o
> > > > was
> > > > > > not
> > > > > > > > failing. I've even didn't repare that will need to be
> updated.
> > > > > > > >
> > > > > > > > These profiles does not exist anymore:
> > > > > > > >
> > > > > >
> > > >
> > generate-swf,generate-swcs-for-swf,main,build-distribution,build-examples
> > > > > > > >
> > > > > > > > Here's the updated doc for maven simplified [1]
> > > > > > > >
> > > > > > > > In sort:
> > > > > > > >
> > > > > > > > 1.- Only env var needed in Maven now is FLASHPLAYER_DEBUGGER
> > > > > > > > 2.- Build from an empty repo is now more reliable (something
> > that
> > > > > was a
> > > > > > > > real headache)
> > > > > > > > 3.- Profiles are reduced to:
> > > > > > > >
> > > > > > > >
> > > > > > > >- with-ui-testsuite
> > > > > > > >- option-with-swf
> > > > > > > >- with-examples
> > > > > > > >- with-distribution
> > > > > > > >
> > > > > > > > Can you upgrade builds.a.o to use this profiles?
> > > > > > > >
> > > > > > > > [1]
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven
> > > > > > > >
> > > > > > > >
> 

Re: Maven Distribution SDK fixed and working for IDEs

[Carlos Rovira]

ok didn't notice.
So maybe is a classpath problem?
It's clear that VSCode goes to the same place and find it since mxmlc is a
dummy jar that has exactly that class, but Moonshine goes and didn't find
it.
If not any clue what could be happening?
Thanks

El mié., 5 feb. 2020 a las 16:53, Piotr Zarzycki ()
escribió:

> Exactly and I can confirm that mxmlc is in place.
>
> śr., 5 lut 2020 o 16:49 Josh Tynjala 
> napisał(a):
>
> > You can see from the output that Moonshine is calling the command line
> > scripts in js/bin.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Wed, Feb 5, 2020 at 7:45 AM Carlos Rovira 
> > wrote:
> >
> > > Hi Piotr,
> > >
> > > That was a problem I had with VSCode when started to work on fix SDK
> for
> > > IDE.
> > > Josh told me that VSCode tries to find that class in /js/lib/mxmlc.jar
> > > it needs /js/lib/mxmlc.jar too
> > >
> > > Maybe Moonshine is looking in other path?
> > >
> > > Thanks
> > >
> > > El mar., 4 feb. 2020 a las 14:43, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>)
> > > escribió:
> > >
> > > > Hi Carlos,
> > > >
> > > > I have build on my Mac SDK and tried in Nightly Build of Moonshine. I
> > > > cannot build Hello World. I'm getting following error:
> > > >
> > > >
> > > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/bin/mxmlc
> > > > -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml -debug=true
> > > > -source-map=true -compiler.targets=JSRoyale
> > > > -js-output="/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject"
> > > > : Using Royale Compiler codebase:
> > > > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > > > : Using Royale SDK:
> > > > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > > > : Error: Could not find or load main class
> > > > org.apache.royale.compiler.clients.MXMLJSC
> > > >
> > > >
> > > >
> > > > czw., 23 sty 2020 o 16:26 Carlos Rovira 
> > > > napisał(a):
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > right, are simplified too and does not have any profile or
> variable.
> > > > >
> > > > > "-U clean install" is standard maven commands, nothing to do with
> us
> > in
> > > > > particular, so you can left that
> > > > > "-P main,utils" are not needed anymore, since now there's no
> > > > > differentiation between a "first build" against rest of builds.
> > > > >
> > > > >
> > > > > El jue., 23 ene. 2020 a las 15:32, Piotr Zarzycki (<
> > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > >
> > > > > > Hi Carlos,
> > > > > >
> > > > > > Builds for framework is updated. What about compiler and
> typedefs ?
> > > For
> > > > > > compiler on the server we have:
> > > > > >
> > > > > > -U clean install
> > > > > > -P -main,utils
> > > > > >
> > > > > > It looks like that those profiles also deprecated - can you
> > confirm ?
> > > > > >
> > > > > > Thanks,
> > > > > > Piotr
> > > > > >
> > > > > > śr., 22 sty 2020 o 18:37 Carlos Rovira 
> > > > > > napisał(a):
> > > > > >
> > > > > > > Hi Piotr,
> > > > > > >
> > > > > > > it surprise me that due all the changes done in maven
> builds.a.o
> > > was
> > > > > not
> > > > > > > failing. I've even didn't repare that will need to be updated.
> > > > > > >
> > > > > > > These profiles does not exist anymore:
> > > > > > >
> > > > >
> > >
> generate-swf,generate-swcs-for-swf,main,build-distribution,build-examples
> > > > > > >
> > > > > > > Here's the updated doc for maven simplified [1]
> > > > > > >
> > > > > > > In sort:
> > > > > > >
> > > > > > > 1.- Only env var needed in Maven now is FLASHPLAYER_DEBUGGER
> > > > > > > 2.- Build from an empty repo is now more reliable (something
> that
> > > > was a
> > > > > > > real headache)
> > > > > > > 3.- Profiles are reduced to:
> > > > > > >
> > > > > > >
> > > > > > >- with-ui-testsuite
> > > > > > >- option-with-swf
> > > > > > >- with-examples
> > > > > > >- with-distribution
> > > > > > >
> > > > > > > Can you upgrade builds.a.o to use this profiles?
> > > > > > >
> > > > > > > [1]
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > El mié., 22 ene. 2020 a las 17:40, Piotr Zarzycki (<
> > > > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > > > >
> > > > > > > > Carlos,
> > > > > > > >
> > > > > > > > What has change more in case of Maven build for framework? On
> > > > > > builds.a.o
> > > > > > > we
> > > > > > > > have following command which running royale-asjs. It looks
> like
> > > > > > something
> > > > > > > > is missing, cause I have removed locally my org.apache.royale
> > > > folder
> > > > > > from
> > > > > > > > .m2 and start building PureMVC to swc. [1] - It throws
> > exception
> > > > now.
> > > > > > > >
> > > > > > > > Could not resolve dependencies for project
> > > > > > > >
> > > > >
> > 

Re: Maven Distribution SDK fixed and working for IDEs

[Piotr Zarzycki]

Exactly and I can confirm that mxmlc is in place.

śr., 5 lut 2020 o 16:49 Josh Tynjala  napisał(a):

> You can see from the output that Moonshine is calling the command line
> scripts in js/bin.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Wed, Feb 5, 2020 at 7:45 AM Carlos Rovira 
> wrote:
>
> > Hi Piotr,
> >
> > That was a problem I had with VSCode when started to work on fix SDK for
> > IDE.
> > Josh told me that VSCode tries to find that class in /js/lib/mxmlc.jar
> > it needs /js/lib/mxmlc.jar too
> >
> > Maybe Moonshine is looking in other path?
> >
> > Thanks
> >
> > El mar., 4 feb. 2020 a las 14:43, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>)
> > escribió:
> >
> > > Hi Carlos,
> > >
> > > I have build on my Mac SDK and tried in Nightly Build of Moonshine. I
> > > cannot build Hello World. I'm getting following error:
> > >
> > >
> > >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/bin/mxmlc
> > > -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml -debug=true
> > > -source-map=true -compiler.targets=JSRoyale
> > > -js-output="/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject"
> > > : Using Royale Compiler codebase:
> > > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > > : Using Royale SDK:
> > > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > > : Error: Could not find or load main class
> > > org.apache.royale.compiler.clients.MXMLJSC
> > >
> > >
> > >
> > > czw., 23 sty 2020 o 16:26 Carlos Rovira 
> > > napisał(a):
> > >
> > > > Hi Piotr,
> > > >
> > > > right, are simplified too and does not have any profile or variable.
> > > >
> > > > "-U clean install" is standard maven commands, nothing to do with us
> in
> > > > particular, so you can left that
> > > > "-P main,utils" are not needed anymore, since now there's no
> > > > differentiation between a "first build" against rest of builds.
> > > >
> > > >
> > > > El jue., 23 ene. 2020 a las 15:32, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > > > Hi Carlos,
> > > > >
> > > > > Builds for framework is updated. What about compiler and typedefs ?
> > For
> > > > > compiler on the server we have:
> > > > >
> > > > > -U clean install
> > > > > -P -main,utils
> > > > >
> > > > > It looks like that those profiles also deprecated - can you
> confirm ?
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > śr., 22 sty 2020 o 18:37 Carlos Rovira 
> > > > > napisał(a):
> > > > >
> > > > > > Hi Piotr,
> > > > > >
> > > > > > it surprise me that due all the changes done in maven builds.a.o
> > was
> > > > not
> > > > > > failing. I've even didn't repare that will need to be updated.
> > > > > >
> > > > > > These profiles does not exist anymore:
> > > > > >
> > > >
> > generate-swf,generate-swcs-for-swf,main,build-distribution,build-examples
> > > > > >
> > > > > > Here's the updated doc for maven simplified [1]
> > > > > >
> > > > > > In sort:
> > > > > >
> > > > > > 1.- Only env var needed in Maven now is FLASHPLAYER_DEBUGGER
> > > > > > 2.- Build from an empty repo is now more reliable (something that
> > > was a
> > > > > > real headache)
> > > > > > 3.- Profiles are reduced to:
> > > > > >
> > > > > >
> > > > > >- with-ui-testsuite
> > > > > >- option-with-swf
> > > > > >- with-examples
> > > > > >- with-distribution
> > > > > >
> > > > > > Can you upgrade builds.a.o to use this profiles?
> > > > > >
> > > > > > [1]
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > El mié., 22 ene. 2020 a las 17:40, Piotr Zarzycki (<
> > > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > > >
> > > > > > > Carlos,
> > > > > > >
> > > > > > > What has change more in case of Maven build for framework? On
> > > > > builds.a.o
> > > > > > we
> > > > > > > have following command which running royale-asjs. It looks like
> > > > > something
> > > > > > > is missing, cause I have removed locally my org.apache.royale
> > > folder
> > > > > from
> > > > > > > .m2 and start building PureMVC to swc. [1] - It throws
> exception
> > > now.
> > > > > > >
> > > > > > > Could not resolve dependencies for project
> > > > > > >
> > > >
> org.puremvc:puremvc-royale-as3-multicore-framework:swc:0.1.0-SNAPSHOT:
> > > > > > > Failure to find
> > > > org.apache.royale.framework:Core:swc:swf:0.9.7-SNAPSHOT
> > > > > > in
> > > > > > > https://repository.apache.org/content/repositories/snapshots
> was
> > > > > cached
> > > > > > in
> > > > > > > the local repository, resolution will not be reattempted until
> > the
> > > > > update
> > > > > > > interval of apache-snapshots has elapsed or updates are forced
> > > > > > >
> > > > > > > Above means that it probably doesn't exists in Apache Maven
> > > > central...
> > > > > > >
> > > > > > > Command on builds.a.o:
> > > > > > >
> > > > > > > -U
> > 

Re: Maven Distribution SDK fixed and working for IDEs

[Josh Tynjala]

You can see from the output that Moonshine is calling the command line
scripts in js/bin.

--
Josh Tynjala
Bowler Hat LLC 


On Wed, Feb 5, 2020 at 7:45 AM Carlos Rovira 
wrote:

> Hi Piotr,
>
> That was a problem I had with VSCode when started to work on fix SDK for
> IDE.
> Josh told me that VSCode tries to find that class in /js/lib/mxmlc.jar
> it needs /js/lib/mxmlc.jar too
>
> Maybe Moonshine is looking in other path?
>
> Thanks
>
> El mar., 4 feb. 2020 a las 14:43, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Hi Carlos,
> >
> > I have build on my Mac SDK and tried in Nightly Build of Moonshine. I
> > cannot build Hello World. I'm getting following error:
> >
> >
> >
> /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution/js/bin/mxmlc
> > -load-config+=obj/NewJavaScriptBrowserProjectConfig.xml -debug=true
> > -source-map=true -compiler.targets=JSRoyale
> > -js-output="/Users/piotr/Downloads/Tests/NewJavaScriptBrowserProject"
> > : Using Royale Compiler codebase:
> > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > : Using Royale SDK:
> > /Users/piotr/Downloads/MoonshineSDKs/Royale_SDK/royale_distribution
> > : Error: Could not find or load main class
> > org.apache.royale.compiler.clients.MXMLJSC
> >
> >
> >
> > czw., 23 sty 2020 o 16:26 Carlos Rovira 
> > napisał(a):
> >
> > > Hi Piotr,
> > >
> > > right, are simplified too and does not have any profile or variable.
> > >
> > > "-U clean install" is standard maven commands, nothing to do with us in
> > > particular, so you can left that
> > > "-P main,utils" are not needed anymore, since now there's no
> > > differentiation between a "first build" against rest of builds.
> > >
> > >
> > > El jue., 23 ene. 2020 a las 15:32, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > Hi Carlos,
> > > >
> > > > Builds for framework is updated. What about compiler and typedefs ?
> For
> > > > compiler on the server we have:
> > > >
> > > > -U clean install
> > > > -P -main,utils
> > > >
> > > > It looks like that those profiles also deprecated - can you confirm ?
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > śr., 22 sty 2020 o 18:37 Carlos Rovira 
> > > > napisał(a):
> > > >
> > > > > Hi Piotr,
> > > > >
> > > > > it surprise me that due all the changes done in maven builds.a.o
> was
> > > not
> > > > > failing. I've even didn't repare that will need to be updated.
> > > > >
> > > > > These profiles does not exist anymore:
> > > > >
> > >
> generate-swf,generate-swcs-for-swf,main,build-distribution,build-examples
> > > > >
> > > > > Here's the updated doc for maven simplified [1]
> > > > >
> > > > > In sort:
> > > > >
> > > > > 1.- Only env var needed in Maven now is FLASHPLAYER_DEBUGGER
> > > > > 2.- Build from an empty repo is now more reliable (something that
> > was a
> > > > > real headache)
> > > > > 3.- Profiles are reduced to:
> > > > >
> > > > >
> > > > >- with-ui-testsuite
> > > > >- option-with-swf
> > > > >- with-examples
> > > > >- with-distribution
> > > > >
> > > > > Can you upgrade builds.a.o to use this profiles?
> > > > >
> > > > > [1]
> > > > >
> > > >
> > >
> >
> https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > El mié., 22 ene. 2020 a las 17:40, Piotr Zarzycki (<
> > > > > piotrzarzyck...@gmail.com>) escribió:
> > > > >
> > > > > > Carlos,
> > > > > >
> > > > > > What has change more in case of Maven build for framework? On
> > > > builds.a.o
> > > > > we
> > > > > > have following command which running royale-asjs. It looks like
> > > > something
> > > > > > is missing, cause I have removed locally my org.apache.royale
> > folder
> > > > from
> > > > > > .m2 and start building PureMVC to swc. [1] - It throws exception
> > now.
> > > > > >
> > > > > > Could not resolve dependencies for project
> > > > > >
> > > org.puremvc:puremvc-royale-as3-multicore-framework:swc:0.1.0-SNAPSHOT:
> > > > > > Failure to find
> > > org.apache.royale.framework:Core:swc:swf:0.9.7-SNAPSHOT
> > > > > in
> > > > > > https://repository.apache.org/content/repositories/snapshots was
> > > > cached
> > > > > in
> > > > > > the local repository, resolution will not be reattempted until
> the
> > > > update
> > > > > > interval of apache-snapshots has elapsed or updates are forced
> > > > > >
> > > > > > Above means that it probably doesn't exists in Apache Maven
> > > central...
> > > > > >
> > > > > > Command on builds.a.o:
> > > > > >
> > > > > > -U
> > > > > > clean
> > > > > > deploy
> > > > > > -P
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> generate-swf,generate-swcs-for-swf,main,build-distribution,build-examples,apache-snapshots-enabled
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> -Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=sometoken
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>