Re: Building Maven Distribution

2021-04-16 Thread Yishay Weiss 
This is probably due to the fact I was doing some manual editing and git pushes 
which messed up the release. I'm going to start another RC next week.

From: Yishay Weiss 
Sent: Friday, April 16, 2021 7:02 AM
To: dev@royale.apache.org 
Subject: RE: Building Maven Distribution

C:\jenkins\workspace\Royale_Release_Step_010\distribution\jars\compiler-mxmljsc\target\compiler-mxmljsc-0.9.8.jar

Cannot be archived because it does not exist. What does exist is


C:\jenkins\workspace\Royale_Release_Step_010\distribution\jars\compiler-mxmljsc\target\compiler-mxmljsc-0.9.9.jar

Not sure where the version got bumped.

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Friday, April 16, 2021 9:58 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: Building Maven Distribution

I’m getting the same error on the CI server [1], when running from the project 
root.


C:\jenkins\workspace\Royale_Release_Step_010>exit 0

[Royale_Release_Step_010] $ cmd.exe /C "mvn --batch-mode 
"-Proyale-release,apache-release,with-distribution,with-examples,with-manualtests,option-with-swf"
 release:prepare -Dtag=org.apache.royale.framework-0.9.8-rc2 
-DpushChanges=false -Dusername=yishayw -DautoVersionSubmodules=true 
-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=35b7e7b4
 -Dwebdriver.gecko.driver=C:\geckodriver\geckodriver.exe 
-Dgenerate.swf.swcs=true -Dgenerate.swf && exit %%ERRORLEVEL%%"



[1] Royale_Release_Step_010 #21 Console [Jenkins] 
(azure.com)<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/view/Royale_Release_Steps/job/Royale_Release_Step_010/21/console>

From: Josh Tynjala<mailto:joshtynj...@bowlerhat.dev>
Sent: Thursday, April 15, 2021 7:32 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: Building Maven Distribution

Good to know. However, assuming that Yishay is building the distribution as
part of his efforts to do a release, it's probably best for him to run the
longer clean build from the root so that he can be sure that his
distribution doesn't unexpectedly include older build output.

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


On Thu, Apr 15, 2021 at 9:24 AM Piotr Zarzycki 
wrote:

> Josh,
>
> It is possible to generate distribution by running following command from
> distribution folder;
>
> mvn clean install DdistributionTargetFolder=path_to_empty_folder
>
> Maybe it is neccassery build sdk upfront in first attempt, but later
> creating distribution is a matter of 5 minutes max.
>
> Thanks,
> Piotr
>
> czw., 15 kwi 2021 o 18:20 Josh Tynjala 
> napisał(a):
>
> > You need to run Maven in the root of the repo rather than the
> distribution
> > folder:
> >
> > C:\dev\full_royale_sdk\royale-asjs
> >
> > To build a distribution you need to enable the with-distribution profile.
> >
> > To include SWF support you need to enable the option-with-swf profile
> too.
> >
> > So something like this should give you a distribution:
> >
> > C:\dev\full_royale_sdk\royale-asjs>mvn clean install -P
> > with-distribution,option-with-swf
> >
> > More details (and some additional profiles) here:
> >
> >
> https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Thu, Apr 15, 2021 at 7:05 AM Yishay Weiss 
> > wrote:
> >
> > >
> > > Sorry if this has come up already but can anyone point me in the right
> > > direction?
> > >
> > > I ran
> > >
> > > C:\dev\full_royale_sdk\royale-asjs\distribution>mvn clean install
> > >
> > > And got
> > >
> > > [ERROR] Failed to execute goal
> > > org.apache.maven.plugins:maven-assembly-plugin:3.2.0:single
> > > (create-distro-packages) on project distribution: Failed to create as
> > > sembly: Error adding file to archive:
> > >
> >
> C:\dev\full_royale_sdk\royale-asjs\distribution\jars\compiler-mxmljsc\target\compiler-mxmljsc-0.9.8-SNAPSHOT.jar
> > > -> [Help
> > > 1]
> > >
> >
>
>
> --
>
> Piotr Zarzycki
>

RE: Building Maven Distribution

2021-04-16 Thread Yishay Weiss 
C:\jenkins\workspace\Royale_Release_Step_010\distribution\jars\compiler-mxmljsc\target\compiler-mxmljsc-0.9.8.jar

Cannot be archived because it does not exist. What does exist is


C:\jenkins\workspace\Royale_Release_Step_010\distribution\jars\compiler-mxmljsc\target\compiler-mxmljsc-0.9.9.jar

Not sure where the version got bumped.

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Friday, April 16, 2021 9:58 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: RE: Building Maven Distribution

I’m getting the same error on the CI server [1], when running from the project 
root.


C:\jenkins\workspace\Royale_Release_Step_010>exit 0

[Royale_Release_Step_010] $ cmd.exe /C "mvn --batch-mode 
"-Proyale-release,apache-release,with-distribution,with-examples,with-manualtests,option-with-swf"
 release:prepare -Dtag=org.apache.royale.framework-0.9.8-rc2 
-DpushChanges=false -Dusername=yishayw -DautoVersionSubmodules=true 
-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=35b7e7b4
 -Dwebdriver.gecko.driver=C:\geckodriver\geckodriver.exe 
-Dgenerate.swf.swcs=true -Dgenerate.swf && exit %%ERRORLEVEL%%"



[1] Royale_Release_Step_010 #21 Console [Jenkins] 
(azure.com)<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/view/Royale_Release_Steps/job/Royale_Release_Step_010/21/console>

From: Josh Tynjala<mailto:joshtynj...@bowlerhat.dev>
Sent: Thursday, April 15, 2021 7:32 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: Building Maven Distribution

Good to know. However, assuming that Yishay is building the distribution as
part of his efforts to do a release, it's probably best for him to run the
longer clean build from the root so that he can be sure that his
distribution doesn't unexpectedly include older build output.

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


On Thu, Apr 15, 2021 at 9:24 AM Piotr Zarzycki 
wrote:

> Josh,
>
> It is possible to generate distribution by running following command from
> distribution folder;
>
> mvn clean install DdistributionTargetFolder=path_to_empty_folder
>
> Maybe it is neccassery build sdk upfront in first attempt, but later
> creating distribution is a matter of 5 minutes max.
>
> Thanks,
> Piotr
>
> czw., 15 kwi 2021 o 18:20 Josh Tynjala 
> napisał(a):
>
> > You need to run Maven in the root of the repo rather than the
> distribution
> > folder:
> >
> > C:\dev\full_royale_sdk\royale-asjs
> >
> > To build a distribution you need to enable the with-distribution profile.
> >
> > To include SWF support you need to enable the option-with-swf profile
> too.
> >
> > So something like this should give you a distribution:
> >
> > C:\dev\full_royale_sdk\royale-asjs>mvn clean install -P
> > with-distribution,option-with-swf
> >
> > More details (and some additional profiles) here:
> >
> >
> https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Thu, Apr 15, 2021 at 7:05 AM Yishay Weiss 
> > wrote:
> >
> > >
> > > Sorry if this has come up already but can anyone point me in the right
> > > direction?
> > >
> > > I ran
> > >
> > > C:\dev\full_royale_sdk\royale-asjs\distribution>mvn clean install
> > >
> > > And got
> > >
> > > [ERROR] Failed to execute goal
> > > org.apache.maven.plugins:maven-assembly-plugin:3.2.0:single
> > > (create-distro-packages) on project distribution: Failed to create as
> > > sembly: Error adding file to archive:
> > >
> >
> C:\dev\full_royale_sdk\royale-asjs\distribution\jars\compiler-mxmljsc\target\compiler-mxmljsc-0.9.8-SNAPSHOT.jar
> > > -> [Help
> > > 1]
> > >
> >
>
>
> --
>
> Piotr Zarzycki
>

RE: Building Maven Distribution

2021-04-16 Thread Yishay Weiss 
I’m getting the same error on the CI server [1], when running from the project 
root.


C:\jenkins\workspace\Royale_Release_Step_010>exit 0

[Royale_Release_Step_010] $ cmd.exe /C "mvn --batch-mode 
"-Proyale-release,apache-release,with-distribution,with-examples,with-manualtests,option-with-swf"
 release:prepare -Dtag=org.apache.royale.framework-0.9.8-rc2 
-DpushChanges=false -Dusername=yishayw -DautoVersionSubmodules=true 
-Dcom.adobe.systemIdsForWhichTheTermsOfTheAdobeLicenseAgreementAreAccepted=35b7e7b4
 -Dwebdriver.gecko.driver=C:\geckodriver\geckodriver.exe 
-Dgenerate.swf.swcs=true -Dgenerate.swf && exit %%ERRORLEVEL%%"



[1] Royale_Release_Step_010 #21 Console [Jenkins] 
(azure.com)<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/view/Royale_Release_Steps/job/Royale_Release_Step_010/21/console>

From: Josh Tynjala<mailto:joshtynj...@bowlerhat.dev>
Sent: Thursday, April 15, 2021 7:32 PM
To: Apache Royale Development<mailto:dev@royale.apache.org>
Subject: Re: Building Maven Distribution

Good to know. However, assuming that Yishay is building the distribution as
part of his efforts to do a release, it's probably best for him to run the
longer clean build from the root so that he can be sure that his
distribution doesn't unexpectedly include older build output.

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


On Thu, Apr 15, 2021 at 9:24 AM Piotr Zarzycki 
wrote:

> Josh,
>
> It is possible to generate distribution by running following command from
> distribution folder;
>
> mvn clean install DdistributionTargetFolder=path_to_empty_folder
>
> Maybe it is neccassery build sdk upfront in first attempt, but later
> creating distribution is a matter of 5 minutes max.
>
> Thanks,
> Piotr
>
> czw., 15 kwi 2021 o 18:20 Josh Tynjala 
> napisał(a):
>
> > You need to run Maven in the root of the repo rather than the
> distribution
> > folder:
> >
> > C:\dev\full_royale_sdk\royale-asjs
> >
> > To build a distribution you need to enable the with-distribution profile.
> >
> > To include SWF support you need to enable the option-with-swf profile
> too.
> >
> > So something like this should give you a distribution:
> >
> > C:\dev\full_royale_sdk\royale-asjs>mvn clean install -P
> > with-distribution,option-with-swf
> >
> > More details (and some additional profiles) here:
> >
> >
> https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Thu, Apr 15, 2021 at 7:05 AM Yishay Weiss 
> > wrote:
> >
> > >
> > > Sorry if this has come up already but can anyone point me in the right
> > > direction?
> > >
> > > I ran
> > >
> > > C:\dev\full_royale_sdk\royale-asjs\distribution>mvn clean install
> > >
> > > And got
> > >
> > > [ERROR] Failed to execute goal
> > > org.apache.maven.plugins:maven-assembly-plugin:3.2.0:single
> > > (create-distro-packages) on project distribution: Failed to create as
> > > sembly: Error adding file to archive:
> > >
> >
> C:\dev\full_royale_sdk\royale-asjs\distribution\jars\compiler-mxmljsc\target\compiler-mxmljsc-0.9.8-SNAPSHOT.jar
> > > -> [Help
> > > 1]
> > >
> >
>
>
> --
>
> Piotr Zarzycki
>

Re: Building Maven Distribution

2021-04-15 Thread Josh Tynjala 
Good to know. However, assuming that Yishay is building the distribution as
part of his efforts to do a release, it's probably best for him to run the
longer clean build from the root so that he can be sure that his
distribution doesn't unexpectedly include older build output.

--
Josh Tynjala
Bowler Hat LLC 


On Thu, Apr 15, 2021 at 9:24 AM Piotr Zarzycki 
wrote:

> Josh,
>
> It is possible to generate distribution by running following command from
> distribution folder;
>
> mvn clean install DdistributionTargetFolder=path_to_empty_folder
>
> Maybe it is neccassery build sdk upfront in first attempt, but later
> creating distribution is a matter of 5 minutes max.
>
> Thanks,
> Piotr
>
> czw., 15 kwi 2021 o 18:20 Josh Tynjala 
> napisał(a):
>
> > You need to run Maven in the root of the repo rather than the
> distribution
> > folder:
> >
> > C:\dev\full_royale_sdk\royale-asjs
> >
> > To build a distribution you need to enable the with-distribution profile.
> >
> > To include SWF support you need to enable the option-with-swf profile
> too.
> >
> > So something like this should give you a distribution:
> >
> > C:\dev\full_royale_sdk\royale-asjs>mvn clean install -P
> > with-distribution,option-with-swf
> >
> > More details (and some additional profiles) here:
> >
> >
> https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Thu, Apr 15, 2021 at 7:05 AM Yishay Weiss 
> > wrote:
> >
> > >
> > > Sorry if this has come up already but can anyone point me in the right
> > > direction?
> > >
> > > I ran
> > >
> > > C:\dev\full_royale_sdk\royale-asjs\distribution>mvn clean install
> > >
> > > And got
> > >
> > > [ERROR] Failed to execute goal
> > > org.apache.maven.plugins:maven-assembly-plugin:3.2.0:single
> > > (create-distro-packages) on project distribution: Failed to create as
> > > sembly: Error adding file to archive:
> > >
> >
> C:\dev\full_royale_sdk\royale-asjs\distribution\jars\compiler-mxmljsc\target\compiler-mxmljsc-0.9.8-SNAPSHOT.jar
> > > -> [Help
> > > 1]
> > >
> >
>
>
> --
>
> Piotr Zarzycki
>

Re: Building Maven Distribution

2021-04-15 Thread Piotr Zarzycki 
Josh,

It is possible to generate distribution by running following command from
distribution folder;

mvn clean install DdistributionTargetFolder=path_to_empty_folder

Maybe it is neccassery build sdk upfront in first attempt, but later
creating distribution is a matter of 5 minutes max.

Thanks,
Piotr

czw., 15 kwi 2021 o 18:20 Josh Tynjala 
napisał(a):

> You need to run Maven in the root of the repo rather than the distribution
> folder:
>
> C:\dev\full_royale_sdk\royale-asjs
>
> To build a distribution you need to enable the with-distribution profile.
>
> To include SWF support you need to enable the option-with-swf profile too.
>
> So something like this should give you a distribution:
>
> C:\dev\full_royale_sdk\royale-asjs>mvn clean install -P
> with-distribution,option-with-swf
>
> More details (and some additional profiles) here:
>
> https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Thu, Apr 15, 2021 at 7:05 AM Yishay Weiss 
> wrote:
>
> >
> > Sorry if this has come up already but can anyone point me in the right
> > direction?
> >
> > I ran
> >
> > C:\dev\full_royale_sdk\royale-asjs\distribution>mvn clean install
> >
> > And got
> >
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-assembly-plugin:3.2.0:single
> > (create-distro-packages) on project distribution: Failed to create as
> > sembly: Error adding file to archive:
> >
> C:\dev\full_royale_sdk\royale-asjs\distribution\jars\compiler-mxmljsc\target\compiler-mxmljsc-0.9.8-SNAPSHOT.jar
> > -> [Help
> > 1]
> >
>


-- 

Piotr Zarzycki

Re: Building Maven Distribution

2021-04-15 Thread Josh Tynjala 
You need to run Maven in the root of the repo rather than the distribution
folder:

C:\dev\full_royale_sdk\royale-asjs

To build a distribution you need to enable the with-distribution profile.

To include SWF support you need to enable the option-with-swf profile too.

So something like this should give you a distribution:

C:\dev\full_royale_sdk\royale-asjs>mvn clean install -P
with-distribution,option-with-swf

More details (and some additional profiles) here:

https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven

--
Josh Tynjala
Bowler Hat LLC 


On Thu, Apr 15, 2021 at 7:05 AM Yishay Weiss  wrote:

>
> Sorry if this has come up already but can anyone point me in the right
> direction?
>
> I ran
>
> C:\dev\full_royale_sdk\royale-asjs\distribution>mvn clean install
>
> And got
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:3.2.0:single
> (create-distro-packages) on project distribution: Failed to create as
> sembly: Error adding file to archive:
> C:\dev\full_royale_sdk\royale-asjs\distribution\jars\compiler-mxmljsc\target\compiler-mxmljsc-0.9.8-SNAPSHOT.jar
> -> [Help
> 1]
>

Building Maven Distribution

2021-04-15 Thread Yishay Weiss 

Sorry if this has come up already but can anyone point me in the right 
direction?

I ran

C:\dev\full_royale_sdk\royale-asjs\distribution>mvn clean install

And got

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-assembly-plugin:3.2.0:single 
(create-distro-packages) on project distribution: Failed to create as
sembly: Error adding file to archive: 
C:\dev\full_royale_sdk\royale-asjs\distribution\jars\compiler-mxmljsc\target\compiler-mxmljsc-0.9.8-SNAPSHOT.jar
 -> [Help
1]

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

2021-03-21 Thread Christofer Dutz 
Hi all,

So, in cases like this, I usually pull all latest changes from develop into the 
feature-branch. Run a full build there, push my changes. 
Then I switch back to develop and pull my changes of the feature-branch back 
into develop. This time I had to merge instead of my usual rebase as the Apache 
repo wasn't accepting it otherwise.

But ... now all changes should be back in develop and now the Maven 
distribution should be a lot better than before.

Hope all went well. I'm going to have an eye on the Apache CI.

Have a great Sunday,
  Chris


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

Hi Piotr,

So, I just updated all of my branches with the latest changes from develop ... 
currently running a full build. 
As soon as that's successful, I'll merge the changes back to develop.

I do agree that the changes should be merged before a RC is cut.

Chris


-Ursprüngliche Nachricht-
Von: Piotr Zarzycki 
Gesendet: Sonntag, 21. März 2021 10:06
An: dev@royale.apache.org
Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

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  Array> 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

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

2021-03-21 Thread Christofer Dutz 
Hi Piotr,

So, I just updated all of my branches with the latest changes from develop ... 
currently running a full build. 
As soon as that's successful, I'll merge the changes back to develop.

I do agree that the changes should be merged before a RC is cut.

Chris


-Ursprüngliche Nachricht-
Von: Piotr Zarzycki  
Gesendet: Sonntag, 21. März 2021 10:06
An: dev@royale.apache.org
Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

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  Array> 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 giv

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

2021-03-21 Thread 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

2021-03-17 Thread 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

2021-03-16 Thread 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

2021-03-16 Thread 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?

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

2021-03-16 Thread Christofer Dutz 
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?







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>&

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

2021-03-16 Thread 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

2021-03-16 Thread 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

>…

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

2021-03-16 Thread Christofer Dutz 
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  
Gesendet: Dienstag, 16. März 2021 16:08
An: 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  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

2021-03-16 Thread 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

2021-03-15 Thread 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

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

2021-03-13 Thread Christofer Dutz 
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)
: at
org.apache.royale.compiler.internal.units.CompilationUnitBase$2$1.call(CompilationUnitBase.java:259)
: ... 6 more
: Caused by: java.lang.ClassNotFoundException: org.antlr.runtime.CharStream
: 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)
: ... 19 more
: 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(RequestMak

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

2021-03-12 Thread 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

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

2021-03-12 Thread Christofer Dutz 
So:

The Ant version:

Doesn't seem to be having the following libs in the "libs" directory:
- compiler-compjsc.jar
- compiler-externc.jar
- compiler-jburg-types.jar
- compiler-mxmljsc.jar
- compiler-playerglobal.jar
- royale-ant-tasks

In compiler-swfdump the MANIFEST refers to commons-io.jar which however should 
be external/commons-io.jar ... so effectively it's a useless addition.

In the Maven versions:

- I changed all compiler artifacts to no longer 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(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
> .ASBlockWalk

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

2021-03-12 Thread Christofer Dutz 
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(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(ASBloc

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

2021-03-11 Thread 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

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

2021-03-11 Thread Christofer Dutz 
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.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.jx.StatementEmitter.emit(StatementEmitter.java:40)
: at
org.apache.royale.compiler.internal.codegen.js.jx.StatementEmitter.emit(StatementEmitter.java:29)
: at
org.apache.royale.compiler.internal.codegen.js.JSEmitter.emitStatement(JSEmitter.java:349)
: at
org.apache.royale.compiler.internal.codegen.js.royale.JSRoyaleEmitter.emitStatement(JSRoyaleEmitter.java:1204)
: at
org.apache.royale.compiler.internal.codegen.as.ASBlockWalker.visitBlock(ASBlockWalker.java:349)
: at
org.apache.royale.compiler.internal.visitor.as.ASNodeSwitch.handle(ASNodeSwitch.java:278)
: at
org.apache.royale.compiler.internal.visitor.as.ASNodeHandler.handle(ASNodeHandler.java:85)
: at
org.apache.royale.compiler.internal.visitor.as.BeforeAfterStrategy.handle(BeforeAfterStrateg

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

2021-03-11 Thread 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

2021-03-09 Thread 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

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

2021-03-09 Thread Christofer Dutz 
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.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.BeforeAfterStrategy.handle(BeforeAfterStrategy.java:110)
: at
org.apache.royale.compiler.internal.codegen.as.ASBlockWalker.walk(ASBlockWalke

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

2021-03-09 Thread 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

2021-03-04 Thread 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

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

2021-03-04 Thread Christofer Dutz 
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 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.
>>> >>
>>>

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

2021-03-04 Thread Christofer Dutz 
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 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 
>>> >> devel

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

2021-03-04 Thread 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

2021-03-03 Thread 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

2021-03-03 Thread 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

2021-03-03 Thread 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

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

2021-03-03 Thread Christofer Dutz 
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 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 t

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

2021-03-03 Thread Christofer Dutz 
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 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
>> >
>> >
>>

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

2021-03-03 Thread 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

2021-03-03 Thread 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 
&

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

2021-03-03 Thread Christofer Dutz 
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 
> >> 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 .

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

2021-03-03 Thread 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]
> >>

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

2021-03-03 Thread Christofer Dutz 
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]
>> -
>> ---
>> [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
>

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

2021-03-03 Thread Christofer Dutz 
In the distribution directory, but it should work the same way in the root.

Chris

-Ursprüngliche Nachricht-
Von: Piotr Zarzycki  
Gesendet: Mittwoch, 3. März 2021 14:31
An: Apache Royale Development 
Betreff: Re: [MAVEN DISTRIBUTION] getting the Ant and Maven aligned

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
> > >

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

2021-03-03 Thread 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

2021-03-03 Thread 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
&

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

2021-03-03 Thread Christofer Dutz 
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 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 <htt

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

2021-03-03 Thread 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:
> > >
> > > 
> > >
&

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

2021-03-03 Thread Christofer Dutz 
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:
> >
> > 
> >
> > 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 
> >

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

2021-03-03 Thread 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

2021-03-03 Thread 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

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

2021-03-03 Thread Christofer Dutz 
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 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>
> >
> >
&g

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

2021-03-02 Thread 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

2021-03-02 Thread 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

2021-03-02 Thread 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

2021-03-02 Thread 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

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

2021-03-02 Thread Christofer Dutz 
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?



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 ... 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 
> > spe

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

2021-03-02 Thread 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

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

2021-03-02 Thread Christofer Dutz 
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 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 usin

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

2021-03-02 Thread 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

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

2021-03-02 Thread Christofer Dutz 
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 (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
> >

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

2021-03-01 Thread Christofer Dutz 
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 (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
>

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

2021-03-01 Thread 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

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

2021-03-01 Thread Christofer Dutz 
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.
>
> 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-c

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

2021-03-01 Thread 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

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

2021-03-01 Thread Christofer Dutz 
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 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 
&g

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

2021-03-01 Thread 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

2021-03-01 Thread 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

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

2021-03-01 Thread Christofer Dutz 
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 ()
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

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

2021-03-01 Thread 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

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

2021-02-28 Thread Christofer Dutz 
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

2021-02-28 Thread 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

2021-02-28 Thread 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

2021-02-28 Thread 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

2021-02-28 Thread 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

2021-02-28 Thread 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

2021-02-28 Thread 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)<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

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

2021-02-28 Thread Christofer Dutz 
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

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

2021-02-28 Thread Christofer Dutz 
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

[MAVEN DISTRIBUTION] getting the Ant and Maven aligned

2021-02-28 Thread Christofer Dutz 
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

2020-05-06 Thread 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

2020-05-06 Thread 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

2020-05-06 Thread 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

2020-05-06 Thread 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

2020-05-06 Thread 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

2020-05-05 Thread 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

2020-05-05 Thread 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

2020-05-05 Thread 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

2020-05-05 Thread 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
>
>

Maven DIstribution

2020-05-05 Thread Alex Harui 
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: Some of the Clipboard class method is not visible in Maven distribution build

2020-04-21 Thread Carlos Rovira 
Hi Piotr,

develop is actually in good state from saturday. I updated poms and could
remove my local .m2 royale folder and build a full maven 0.9.8-SNAPSHOT, so
you can do your changes without problem I think.

I think what you find is similar than the problem I fixed recently with
SVGImage where pom was not correctly set. We need to continue covering that
all things in Maven is working properly, but that just happen as someone
using maven tries to use it and finds the issue.

Thanks



El mar., 21 abr. 2020 a las 8:38, Piotr Zarzycki ()
escribió:

> Thanks Josh for help. I just checked distribution pom.xml and it doesn't
> contains module with Clipboard. I will add it once develop will be in good
> state.
>
> wt., 21 kwi 2020 o 00:21 Josh Tynjala 
> napisał(a):
>
> > I'm guessing that org.apache.royale.textLayout.edit.Clipboard is missing,
> > for some reason. In that case, it would fall back to the global
> Clipboard,
> > since that class doesn't need to be imported.
> >
> > As for why it is missing, I would guess that it's one of these two
> possible
> > reasons...
> >
> > 1) You forgot to add the SWC that contains
> > org.apache.royale.textLayout.edit.Clipboard to your pom.xml
> > 2) You have the correct SWC, but for some reason, it compiled without
> > including org.apache.royale.textLayout.edit.Clipboard.
> >
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Mon, Apr 20, 2020 at 3:13 PM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > wrote:
> >
> > > Ok but why it has happened? I will check tomorrow if I have correct
> > import,
> > > but I think I have.
> > > Why it is working with SDK from Jenkins, but doesn't with Maven
> > > distribution
> > >
> > > On Mon, Apr 20, 2020, 6:07 PM Josh Tynjala 
> > > wrote:
> > >
> > > > I think that you are trying to use the wrong Clipboard class. It
> looks
> > > like
> > > > you're using the JS global Clipboard, rather than
> > > > org.apache.royale.textLayout.edit.Clipboard.
> > > >
> > > > org.apache.royale.textLayout.edit.Clipboard doesn't have writeText()
> > and
> > > > readText() methods.
> > > >
> > > > https://developer.mozilla.org/en-US/docs/Web/API/Clipboard
> > > >
> > > > --
> > > > Josh Tynjala
> > > > Bowler Hat LLC <https://bowlerhat.dev>
> > > >
> > > >
> > > > On Mon, Apr 20, 2020 at 8:13 AM Piotr Zarzycki <
> > > piotrzarzyck...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I build SDK using distribution option by Maven. When I have tried
> > build
> > > > > application using distribution I'm getting following error:
> > > > >
> > > > > Error: Access of possibly undefined property generalClipboard
> > through a
> > > > > reference with static type Clipboard.
> > > > >
> > > > > It looks like this method [1] wasn't generated in distribution
> > output.
> > > > When
> > > > > I look into class signature in SWC I see following only [2]
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/royale-asjs/blob/bdaa1b0bc5f54423aac7bafda363f512236977a1/frameworks/projects/TLF/src/main/royale/org/apache/royale/textLayout/edit/Clipboard.as#L156
> > > > > [2] https://ibb.co/GWdj86b
> > > > >
> > > > > Thanks,
> > > > > --
> > > > >
> > > > > Piotr Zarzycki
> > > > >
> > > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > > <https://www.patreon.com/piotrzarzycki>*
> > > > >
> > > >
> > >
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

Re: Some of the Clipboard class method is not visible in Maven distribution build

2020-04-21 Thread Piotr Zarzycki 
Thanks Josh for help. I just checked distribution pom.xml and it doesn't
contains module with Clipboard. I will add it once develop will be in good
state.

wt., 21 kwi 2020 o 00:21 Josh Tynjala 
napisał(a):

> I'm guessing that org.apache.royale.textLayout.edit.Clipboard is missing,
> for some reason. In that case, it would fall back to the global Clipboard,
> since that class doesn't need to be imported.
>
> As for why it is missing, I would guess that it's one of these two possible
> reasons...
>
> 1) You forgot to add the SWC that contains
> org.apache.royale.textLayout.edit.Clipboard to your pom.xml
> 2) You have the correct SWC, but for some reason, it compiled without
> including org.apache.royale.textLayout.edit.Clipboard.
>
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Mon, Apr 20, 2020 at 3:13 PM Piotr Zarzycki 
> wrote:
>
> > Ok but why it has happened? I will check tomorrow if I have correct
> import,
> > but I think I have.
> > Why it is working with SDK from Jenkins, but doesn't with Maven
> > distribution
> >
> > On Mon, Apr 20, 2020, 6:07 PM Josh Tynjala 
> > wrote:
> >
> > > I think that you are trying to use the wrong Clipboard class. It looks
> > like
> > > you're using the JS global Clipboard, rather than
> > > org.apache.royale.textLayout.edit.Clipboard.
> > >
> > > org.apache.royale.textLayout.edit.Clipboard doesn't have writeText()
> and
> > > readText() methods.
> > >
> > > https://developer.mozilla.org/en-US/docs/Web/API/Clipboard
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC <https://bowlerhat.dev>
> > >
> > >
> > > On Mon, Apr 20, 2020 at 8:13 AM Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I build SDK using distribution option by Maven. When I have tried
> build
> > > > application using distribution I'm getting following error:
> > > >
> > > > Error: Access of possibly undefined property generalClipboard
> through a
> > > > reference with static type Clipboard.
> > > >
> > > > It looks like this method [1] wasn't generated in distribution
> output.
> > > When
> > > > I look into class signature in SWC I see following only [2]
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://github.com/apache/royale-asjs/blob/bdaa1b0bc5f54423aac7bafda363f512236977a1/frameworks/projects/TLF/src/main/royale/org/apache/royale/textLayout/edit/Clipboard.as#L156
> > > > [2] https://ibb.co/GWdj86b
> > > >
> > > > Thanks,
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > > <https://www.patreon.com/piotrzarzycki>*
> > > >
> > >
> >
>


-- 

Piotr Zarzycki

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

Re: Some of the Clipboard class method is not visible in Maven distribution build

2020-04-20 Thread Josh Tynjala 
I'm guessing that org.apache.royale.textLayout.edit.Clipboard is missing,
for some reason. In that case, it would fall back to the global Clipboard,
since that class doesn't need to be imported.

As for why it is missing, I would guess that it's one of these two possible
reasons...

1) You forgot to add the SWC that contains
org.apache.royale.textLayout.edit.Clipboard to your pom.xml
2) You have the correct SWC, but for some reason, it compiled without
including org.apache.royale.textLayout.edit.Clipboard.


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


On Mon, Apr 20, 2020 at 3:13 PM Piotr Zarzycki 
wrote:

> Ok but why it has happened? I will check tomorrow if I have correct import,
> but I think I have.
> Why it is working with SDK from Jenkins, but doesn't with Maven
> distribution
>
> On Mon, Apr 20, 2020, 6:07 PM Josh Tynjala 
> wrote:
>
> > I think that you are trying to use the wrong Clipboard class. It looks
> like
> > you're using the JS global Clipboard, rather than
> > org.apache.royale.textLayout.edit.Clipboard.
> >
> > org.apache.royale.textLayout.edit.Clipboard doesn't have writeText() and
> > readText() methods.
> >
> > https://developer.mozilla.org/en-US/docs/Web/API/Clipboard
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <https://bowlerhat.dev>
> >
> >
> > On Mon, Apr 20, 2020 at 8:13 AM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > I build SDK using distribution option by Maven. When I have tried build
> > > application using distribution I'm getting following error:
> > >
> > > Error: Access of possibly undefined property generalClipboard through a
> > > reference with static type Clipboard.
> > >
> > > It looks like this method [1] wasn't generated in distribution output.
> > When
> > > I look into class signature in SWC I see following only [2]
> > >
> > > [1]
> > >
> > >
> >
> https://github.com/apache/royale-asjs/blob/bdaa1b0bc5f54423aac7bafda363f512236977a1/frameworks/projects/TLF/src/main/royale/org/apache/royale/textLayout/edit/Clipboard.as#L156
> > > [2] https://ibb.co/GWdj86b
> > >
> > > Thanks,
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
>

Re: Some of the Clipboard class method is not visible in Maven distribution build

2020-04-20 Thread Piotr Zarzycki 
Ok but why it has happened? I will check tomorrow if I have correct import,
but I think I have.
Why it is working with SDK from Jenkins, but doesn't with Maven
distribution

On Mon, Apr 20, 2020, 6:07 PM Josh Tynjala 
wrote:

> I think that you are trying to use the wrong Clipboard class. It looks like
> you're using the JS global Clipboard, rather than
> org.apache.royale.textLayout.edit.Clipboard.
>
> org.apache.royale.textLayout.edit.Clipboard doesn't have writeText() and
> readText() methods.
>
> https://developer.mozilla.org/en-US/docs/Web/API/Clipboard
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Mon, Apr 20, 2020 at 8:13 AM Piotr Zarzycki 
> wrote:
>
> > Hi,
> >
> > I build SDK using distribution option by Maven. When I have tried build
> > application using distribution I'm getting following error:
> >
> > Error: Access of possibly undefined property generalClipboard through a
> > reference with static type Clipboard.
> >
> > It looks like this method [1] wasn't generated in distribution output.
> When
> > I look into class signature in SWC I see following only [2]
> >
> > [1]
> >
> >
> https://github.com/apache/royale-asjs/blob/bdaa1b0bc5f54423aac7bafda363f512236977a1/frameworks/projects/TLF/src/main/royale/org/apache/royale/textLayout/edit/Clipboard.as#L156
> > [2] https://ibb.co/GWdj86b
> >
> > Thanks,
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>

Re: Some of the Clipboard class method is not visible in Maven distribution build

2020-04-20 Thread Josh Tynjala 
I think that you are trying to use the wrong Clipboard class. It looks like
you're using the JS global Clipboard, rather than
org.apache.royale.textLayout.edit.Clipboard.

org.apache.royale.textLayout.edit.Clipboard doesn't have writeText() and
readText() methods.

https://developer.mozilla.org/en-US/docs/Web/API/Clipboard

--
Josh Tynjala
Bowler Hat LLC 


On Mon, Apr 20, 2020 at 8:13 AM Piotr Zarzycki 
wrote:

> Hi,
>
> I build SDK using distribution option by Maven. When I have tried build
> application using distribution I'm getting following error:
>
> Error: Access of possibly undefined property generalClipboard through a
> reference with static type Clipboard.
>
> It looks like this method [1] wasn't generated in distribution output. When
> I look into class signature in SWC I see following only [2]
>
> [1]
>
> https://github.com/apache/royale-asjs/blob/bdaa1b0bc5f54423aac7bafda363f512236977a1/frameworks/projects/TLF/src/main/royale/org/apache/royale/textLayout/edit/Clipboard.as#L156
> [2] https://ibb.co/GWdj86b
>
> Thanks,
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>

Some of the Clipboard class method is not visible in Maven distribution build

2020-04-20 Thread Piotr Zarzycki 
Hi,

I build SDK using distribution option by Maven. When I have tried build
application using distribution I'm getting following error:

Error: Access of possibly undefined property generalClipboard through a
reference with static type Clipboard.

It looks like this method [1] wasn't generated in distribution output. When
I look into class signature in SWC I see following only [2]

[1]
https://github.com/apache/royale-asjs/blob/bdaa1b0bc5f54423aac7bafda363f512236977a1/frameworks/projects/TLF/src/main/royale/org/apache/royale/textLayout/edit/Clipboard.as#L156
[2] https://ibb.co/GWdj86b

Thanks,
-- 

Piotr Zarzycki

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

Re: Maven Distribution SDK fixed and working for IDEs

2020-03-26 Thread 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-mem

Re: Maven Distribution SDK fixed and working for IDEs

2020-03-26 Thread 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.
> >
> >
>

Re: Maven Distribution SDK fixed and working for IDEs

2020-03-26 Thread 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.

Re: Maven Distribution SDK fixed and working for IDEs

2020-03-26 Thread 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 tha

  1   2   >