RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Maria Jose Esteve]

I don't have mvn.exe in the /bin directory of Maven... but I tried it and it 
didn't work.
I have restored mvn.cmd (this file does exist) in ApproveRoyale.xml
I modified my build bat and manually set MAVEN_HOME, in case the system 
variable was getting lost, but the result was the same.
The last test was to put MAVEN_HOME in first position in the path, also, same 
error.

I have run out of ideas ☹

Hiedra

-Mensaje original-
De: Josh Tynjala  
Enviado el: lunes, 15 de mayo de 2023 23:20
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

It seems to be failing when running Maven, but it's not giving you an error 
message to explain what the issue is.

I see that you're on Windows. I wonder if you're having a similar issue that I 
had on a previous release of the Royale build tools (I was on Windows at the 
time, but I'm on macOS these days):

https://lists.apache.org/thread/4fw80rsr87h79tofzsfs908plvfghvd4

In this case, a similar workaround would be to change mvn.cmd to mvn.exe on 
line 72 of ApproveRoyale.xml





--
Josh Tynjala
Bowler Hat LLC 


On Mon, May 15, 2023 at 2:08 PM Maria Jose Esteve  wrote:

> It has no longer included it as unapproved, but I still can't finish 
> the Maven compilation, same problem but I don't know why, it's in the 
> path. (I can compile the SDK normally with ant and with mvn and it 
> hasn't given me any problems).
> any idea?
> ---
> main:
>
> build_maven:
> Path is C:\Program Files (x86)\Common
> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache
> \apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\b
> in;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\
> System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Progr
> am Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> Files\dotnet\;C:\Program
> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS 
> Code;C:\Program Files\Microsoft SQL Server\Client 
> SDK\ODBC\170\Tools\Binn\;C:\Program
> Files\PowerShell\7-preview\preview;C:\Program Files 
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;
> C:\Program Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) 
> Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) 
> Management Engine Components\DAL;C:\Program Files (x86)\Pulse 
> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse 
> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL 
> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL 
> Server\130\Tools\Binn\;C:\Program Files 
> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:
> \Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\
> tools;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> VS
> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppDat
> a\Roaming\npm;C:\Program
> Files\Microsoft Office\root\Client
>
> BUILD FAILED
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:798: 
> The following error occurred while executing this line:
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:811: 
> exec
> returned: 1
>
> Total time: 37 minutes 10 seconds
>
> --
> --
>
> Hiedra
>
> -Mensaje original-
> De: Josh Tynjala  Enviado el: lunes, 15 de 
> mayo de 2023 22:16
> Para: dev@royale.apache.org
> Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> Yes, as I said, "You should be able to use it with this existing RC, 
> if you'd like."
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Mon, May 15, 2023 at 1:15 PM Maria Jose Esteve 
> wrote:
>
> > can I test this "ApproveRoyale.xml" with RC4 Josh?
> > Hiedra
> >
> > -Mensaje original-
> > De: Josh Tynjala  Enviado el: lunes, 15 
> > de mayo de 2023 20:04
> > Para: dev@royale.apache.org
> > Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> >
> > That being said, I have updated the approval script in the 
> > royale-asjs Git repo. You should be able to use it with this 
> > existing RC, if you'd
> like.
> >
> > https://github.com/apache/royale-asjs/blob/develop/ApproveRoyale.xml
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Mon, May 15, 2023 at 9:35 AM Josh Tynjala 
> > 
> > wrote:
> >
> > > Now that I've had my morning tea, I remember now that I put 
> > > RoyaleUnit's dependencies into a separate directory so that they 
> > > don't conflict with anything else (and so that they aren't loaded 
> > > by the compiler when they aren't needed). I didn't know that I 
> > > needed to update ApproveRoyale.xml. I will get that fixed for 
> > > *future*
> releases.
> > >
> > > For now, this is just a minor issue, and it should not prevent you 
> > > from voting in favor of this RC. The license 

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

It seems to be failing when running Maven, but it's not giving you an error
message to explain what the issue is.

I see that you're on Windows. I wonder if you're having a similar issue
that I had on a previous release of the Royale build tools (I was on
Windows at the time, but I'm on macOS these days):

https://lists.apache.org/thread/4fw80rsr87h79tofzsfs908plvfghvd4

In this case, a similar workaround would be to change mvn.cmd to mvn.exe on
line 72 of ApproveRoyale.xml





--
Josh Tynjala
Bowler Hat LLC 


On Mon, May 15, 2023 at 2:08 PM Maria Jose Esteve  wrote:

> It has no longer included it as unapproved, but I still can't finish the
> Maven compilation, same problem but I don't know why, it's in the path. (I
> can compile the SDK normally with ant and with mvn and it hasn't given me
> any problems).
> any idea?
> ---
> main:
>
> build_maven:
> Path is C:\Program Files (x86)\Common
> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
> Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> Files\dotnet\;C:\Program
> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> Code;C:\Program Files\Microsoft SQL Server\Client
> SDK\ODBC\170\Tools\Binn\;C:\Program
> Files\PowerShell\7-preview\preview;C:\Program Files
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
> Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine
> Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine
> Components\DAL;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
> Server\130\Tools\Binn\;C:\Program Files
> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> VS
> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm;C:\Program
> Files\Microsoft Office\root\Client
>
> BUILD FAILED
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:798: The
> following error occurred while executing this line:
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:811: exec
> returned: 1
>
> Total time: 37 minutes 10 seconds
>
> 
>
> Hiedra
>
> -Mensaje original-
> De: Josh Tynjala 
> Enviado el: lunes, 15 de mayo de 2023 22:16
> Para: dev@royale.apache.org
> Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> Yes, as I said, "You should be able to use it with this existing RC, if
> you'd like."
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Mon, May 15, 2023 at 1:15 PM Maria Jose Esteve 
> wrote:
>
> > can I test this "ApproveRoyale.xml" with RC4 Josh?
> > Hiedra
> >
> > -Mensaje original-
> > De: Josh Tynjala  Enviado el: lunes, 15 de
> > mayo de 2023 20:04
> > Para: dev@royale.apache.org
> > Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
> >
> > That being said, I have updated the approval script in the royale-asjs
> > Git repo. You should be able to use it with this existing RC, if you'd
> like.
> >
> > https://github.com/apache/royale-asjs/blob/develop/ApproveRoyale.xml
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Mon, May 15, 2023 at 9:35 AM Josh Tynjala
> > 
> > wrote:
> >
> > > Now that I've had my morning tea, I remember now that I put
> > > RoyaleUnit's dependencies into a separate directory so that they
> > > don't conflict with anything else (and so that they aren't loaded by
> > > the compiler when they aren't needed). I didn't know that I needed
> > > to update ApproveRoyale.xml. I will get that fixed for *future*
> releases.
> > >
> > > For now, this is just a minor issue, and it should not prevent you
> > > from voting in favor of this RC. The license is actually allowed,
> > > but
> > "Rat"
> > > incorrectly flags it. The approval script will not fail when it
> > > mentions this license, so we don't need to do anything to fix it
> > > immediately.
> > >
> > > --
> > > Josh Tynjala
> > > Bowler Hat LLC 
> > >
> > >
> > > On Mon, May 15, 2023 at 8:55 AM Josh Tynjala
> > > 
> > > wrote:
> > >
> > >> The approval script excludes dom4j-LICENSE.txt at the following
> > location:
> > >>
> > >> 
> > >>
> > >> But your path is slightly different:
> > >>
> > >> royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
> > >>
> > >> I think we can just make a minor tweak to the 

RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Maria Jose Esteve]

It has no longer included it as unapproved, but I still can't finish the Maven 
compilation, same problem but I don't know why, it's in the path. (I can 
compile the SDK normally with ant and with mvn and it hasn't given me any 
problems).
any idea?
---
main:

build_maven:
Path is C:\Program Files (x86)\Common 
Files\Oracle\Java\javapath;D:\Apache;C:\Program 
Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
 Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program 
Files\dotnet\;C:\Program 
Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS 
Code;C:\Program Files\Microsoft SQL Server\Client 
SDK\ODBC\170\Tools\Binn\;C:\Program 
Files\PowerShell\7-preview\preview;C:\Program Files 
(x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
 Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine 
Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine 
Components\DAL;C:\Program Files (x86)\Pulse Secure\VC142.CRT\X64\;C:\Program 
Files (x86)\Pulse Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL 
Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL 
Server\130\Tools\Binn\;C:\Program Files 
(x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Programs\Microsoft
 VS 
Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm;C:\Program
 Files\Microsoft Office\root\Client

BUILD FAILED
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:798: The 
following error occurred while executing this line:
D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:811: exec 
returned: 1

Total time: 37 minutes 10 seconds


Hiedra

-Mensaje original-
De: Josh Tynjala  
Enviado el: lunes, 15 de mayo de 2023 22:16
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

Yes, as I said, "You should be able to use it with this existing RC, if you'd 
like."

--
Josh Tynjala
Bowler Hat LLC 


On Mon, May 15, 2023 at 1:15 PM Maria Jose Esteve  wrote:

> can I test this "ApproveRoyale.xml" with RC4 Josh?
> Hiedra
>
> -Mensaje original-
> De: Josh Tynjala  Enviado el: lunes, 15 de 
> mayo de 2023 20:04
> Para: dev@royale.apache.org
> Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> That being said, I have updated the approval script in the royale-asjs 
> Git repo. You should be able to use it with this existing RC, if you'd like.
>
> https://github.com/apache/royale-asjs/blob/develop/ApproveRoyale.xml
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Mon, May 15, 2023 at 9:35 AM Josh Tynjala 
> 
> wrote:
>
> > Now that I've had my morning tea, I remember now that I put 
> > RoyaleUnit's dependencies into a separate directory so that they 
> > don't conflict with anything else (and so that they aren't loaded by 
> > the compiler when they aren't needed). I didn't know that I needed 
> > to update ApproveRoyale.xml. I will get that fixed for *future* releases.
> >
> > For now, this is just a minor issue, and it should not prevent you 
> > from voting in favor of this RC. The license is actually allowed, 
> > but
> "Rat"
> > incorrectly flags it. The approval script will not fail when it 
> > mentions this license, so we don't need to do anything to fix it 
> > immediately.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Mon, May 15, 2023 at 8:55 AM Josh Tynjala 
> > 
> > wrote:
> >
> >> The approval script excludes dom4j-LICENSE.txt at the following
> location:
> >>
> >> 
> >>
> >> But your path is slightly different:
> >>
> >> royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
> >>
> >> I think we can just make a minor tweak to the approval script to 
> >> add this path too:
> >>
> >> 
> >>
> >> --
> >> Josh Tynjala
> >> Bowler Hat LLC 
> >>
> >>
> >> On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve 
> >> 
> >> wrote:
> >>
> >>> Hi,
> >>> I keep testing the automated compilation option [1] the 
> >>> compilation gave me error ☹.
> >>> I have left the log of the compilation here [2] but I attach the error:
> >>>
> >>> <<<
> >>> ...
> >>> main:
> >>> Copying 1 file to
> >>>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\
> royale-asjs\examples\native\USStatesMap\bin\js-debug
> >>> Copying 1 file to
> >>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-
> >>> sr c\royale-asjs\examples\native\USStatesMap\bin\js-release
> >>>
> 

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

Based on some further investigation, it looks like the Royale compiler
knows how to implement the JS IEventDispatcher API in generated .js files
only. When those .js files are included in a SWC file, the binary part of
the SWC file that is used for type checking and IDE support will always be
generated with the SWF IEventDispatcher API. That's where the conflict
comes from.

This does not appear to me to be a regression, but how it has always
worked. We may want to provide a way to generate both APIs in SWC binary
code, but I would say that's for a future release.

In Royale framework code, it looks like there are two ways to manually
handle bindable beads.

1) Extend DispatcherBead. It looks like a lot of bead classes do this.

2) Manually implement IEventDispatcher, with the different signatures
conditionally compiled with COMPILE::SWF and COMPILE::JS. This is much less
common, but it is used in a couple of places.

In both cases, the compiler won't generate any IEventDispatcher code for
bindable properties because the beads will already be event dispatchers.

The first option is most common, but not always possible when another is
superclass already being used. The second option where the interface is
manually implemented happens in these two bead:

a) In Jewel, a manual IEventDispatcher implementation is used in
ArrayListSelectionModel.
b) In Spark, a manual implementation is used in LayoutBase.

In the case of Jewel's TileHorizontalLayout, if you wanted to avoid
manually implementing IEventDispatcher, the Core version of LayoutBase
would need to extend DispatcherBead. However, I don't think this would be
considered PAYG, which Core is expected to follow more strictly than Jewel,
so there's no way to use DispatcherBead with Jewel's TileHorizontalLayout.
TileHorizontalLayout probably needs a manual implementation of
IEventDispatcher. Or possibly SimpleHorizontalLayout or StyledLayoutBase
instead, depending on how strict you want to be with PAYG in Jewel. For the
least impact and most PAYG, you should manually implement IEventDispatcher
directly on TileHorizontalLayout.

(In my opinion, this is not a release blocker. I'm just letting you know
what I found in my investigation, and my advice for fixing it.)

--
Josh Tynjala
Bowler Hat LLC 


On Mon, May 15, 2023 at 1:13 PM Josh Tynjala 
wrote:

> > Does anyone have any idea what has happened here ? Why
> TileHorizontalLayout
> > after compilation to TileHorizontalLayout.js have all of these methods ?
>
> TileHorizontallayout has [Bindable] metadata on some properties. If
> anything in a class is marked as [Bindable], and that class (or a
> superclass) does not already extend EventDispatcher (or implement
> IEventDispatcher), the compiler will automatically generate an
> implementation of IEventDispatcher. This is true in Royale, and it was also
> true in Flex.
>
> Here are the classes that TileHorizontalLayout is a subclass of:
> TileHorizontalLayout extends SimpleHorizontalLayout extends
> StyledLayoutBase extends LayoutBase extends Bead
>
> There are also the following interfaces in the type hierarchy:
> ILayoutStyleProperties, IBeadLayout, IBead
>
> Nowhere in this chain of classes is there an EventDispatcher or
> IEventDispatcher. So the compiler is generating its own implementation of
> IEventDispatcher.
>
> Unfortunately, it seems to be generating an implementation of the methods
> from the SWF version of IEventDispatcher instead of the methods from the JS
> version of IEventDispatcher. I don't believe that I have worked with the
> part of the Royale compiler that generates code for bindable
> classes/properties before, so I don't know why it would be doing that.
> However, that seems like a bug. Maybe not necessarily in the compiler. It
> could be that the compiler options used by the JewelJS build are wrong.
>
> Note: I don't think that the compiler is incorrectly using the Spark
> version of LayoutBase instead of the Core version of LayoutBase. This can
> be explained without the Spark version of LayoutBase being involved in any
> way.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Mon, May 15, 2023 at 5:14 AM Piotr Zarzycki 
> wrote:
>
>> Hi Guys,
>>
>> I have voted +1, but I have found one issue which concerns me a little
>> bit.
>> I have need of usage in my application
>> -> org.apache.royale.jewel.beads.layouts.TileHorizontalLayout. I have made
>> my own custom class which extends that one. To my big surprise I got
>> following compilation error:
>>
>>  Error: interface method addEventListener in interface IEventDispatcher is
>> implemented with an incompatible signature in class
>> ExtendedTileHorizontalLayout
>> : Error: interface method removeEventListener in interface
>> IEventDispatcher
>> is implemented with an incompatible signature in class
>> ExtendedTileHorizontalLayout
>> : Error: interface method dispatchEvent in interface IEventDispatcher is
>> implemented with an incompatible 

Re: [VOTE] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

+1
Package
https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/apache-royale-0.9.10-src.tar.gz
Java 17
OS: Mac OS X aarch64 13.3.1
Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives: y
No unapproved binaries: y

Package
https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/binaries/apache-royale-0.9.10-bin-js-swf.tar.gz
Binary kit signatures match: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives in binary package: y
No unapproved binaries in binary package: y

Additional notes:
1) ApproveRoyale.xml works with both JS/SWF and JS-only packages on my
machine.
2) I confirmed that both of the binary packages may be installed
successfully with npm.
3) I can successfully build the asconfigc tool with all RoyaleUnit tests
passing, and I can use it to build projects that have asconfig.json files.
4) SWF tests were run with Flash Player 32 and AIR 32.

--
Josh Tynjala
Bowler Hat LLC 


On Sat, May 13, 2023 at 10:35 AM Yishay Weiss 
wrote:

> Hi,
> This is the vote for the 0.9.10 release of Apache Royale.  The release
> candidate can be found here;
> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/
>
> Before voting please review the section,'What are the ASF requirements on
> approving a release?', at:
> http://www.apache.org/dev/release.html#approving-a-release
>
> At a minimum you would be expected to check that:
> - SHA and signed packages are correct
> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
> - That the build script completes successfully
> - That you can compile and crosscompile a simple example using the SDK.
>
> The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS
>
> The source package is a combination of the 3 main Royale repos.
>
> To use the binary package, unzip it into a folder. The -js package is
> ready-to-use in an IDE or command-line. If you need SWF output, use the
> -js-swf package and use Apache Ant to run the InstallAdobeSDKs script via:
> ant -f InstallAdobeSDKs.xml
>
> You may also get the binarypackages via NPM. The -js package can be
> installed via:
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/binaries/apache-royale-0.9.10-bin-js.tar.gz
>
> The full package with SWF support can be installed via:
>
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/binaries/apache-royale-0.9.10-bin-js-swf.tar.gz
>
> Maven artifacts are staged here:
> https://repository.apache.org/content/repositories/orgapacheroyale-1096
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Disapprove the release (please provide specific comments to why)
>
> This vote will be open for 72 hours or until a result can be called.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> Remember that this is a 'beta-quality' release so expect there will be
> many bugs found. IMO the goal is not to try to find and fix bugs in the RC,
> but to make sure we have the packaging right, and enough functionality that
> folks will have some success trying to use it.  People who are not in PMC
> are also encouraged to test out the release and vote, although their votes
> will not be binding, they can influence how the PMC votes.
>
> When voting please indicate what OS, IDE, Flash Player version and AIR
> version you tested with.
>
> For your convenience, there is an ant script that automates the common
> steps to validate a release.  Instead of individually downloading the
> package and signature files, unzipping, etc, you can instead:
> 1) create an empty folder,
> 2) download into that folder this file:
> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/ApproveRoyale.xml
> 3) run the script:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.10 -Drc=4
>If you want to test SWF support during the approval, use:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.10 -Drc=4
> -Duse-flash=true
>
> You are not required to use this script, and more testing of the packages
> and build results are always encouraged.
>
> Please put all discussion about this release in the DISCUSSION thread not
> this VOTE thread.
>
> Thanks,
> Yishay Weiss
>
>

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

Yes, as I said, "You should be able to use it with this existing RC, if
you'd like."

--
Josh Tynjala
Bowler Hat LLC 


On Mon, May 15, 2023 at 1:15 PM Maria Jose Esteve  wrote:

> can I test this "ApproveRoyale.xml" with RC4 Josh?
> Hiedra
>
> -Mensaje original-
> De: Josh Tynjala 
> Enviado el: lunes, 15 de mayo de 2023 20:04
> Para: dev@royale.apache.org
> Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> That being said, I have updated the approval script in the royale-asjs Git
> repo. You should be able to use it with this existing RC, if you'd like.
>
> https://github.com/apache/royale-asjs/blob/develop/ApproveRoyale.xml
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Mon, May 15, 2023 at 9:35 AM Josh Tynjala 
> wrote:
>
> > Now that I've had my morning tea, I remember now that I put
> > RoyaleUnit's dependencies into a separate directory so that they don't
> > conflict with anything else (and so that they aren't loaded by the
> > compiler when they aren't needed). I didn't know that I needed to
> > update ApproveRoyale.xml. I will get that fixed for *future* releases.
> >
> > For now, this is just a minor issue, and it should not prevent you
> > from voting in favor of this RC. The license is actually allowed, but
> "Rat"
> > incorrectly flags it. The approval script will not fail when it
> > mentions this license, so we don't need to do anything to fix it
> > immediately.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Mon, May 15, 2023 at 8:55 AM Josh Tynjala
> > 
> > wrote:
> >
> >> The approval script excludes dom4j-LICENSE.txt at the following
> location:
> >>
> >> 
> >>
> >> But your path is slightly different:
> >>
> >> royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
> >>
> >> I think we can just make a minor tweak to the approval script to add
> >> this path too:
> >>
> >> 
> >>
> >> --
> >> Josh Tynjala
> >> Bowler Hat LLC 
> >>
> >>
> >> On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve 
> >> wrote:
> >>
> >>> Hi,
> >>> I keep testing the automated compilation option [1] the compilation
> >>> gave me error ☹.
> >>> I have left the log of the compilation here [2] but I attach the error:
> >>>
> >>> <<<
> >>> ...
> >>> main:
> >>> Copying 1 file to
> >>>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
> >>> Copying 1 file to
> >>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-sr
> >>> c\royale-asjs\examples\native\USStatesMap\bin\js-release
> >>>
> >>> main:
> >>>
> >>> build_maven:
> >>> Path is C:\Program Files (x86)\Common
> >>> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> >>> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apac
> >>> he\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client
> >>> _1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Wi
> >>> ndows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;
> >>> C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> >>> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbe
> >>> m;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\Op
> >>> enSSH\;C:\Program
> >>> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> >>> Code;C:\Program Files\Microsoft SQL Server\Client
> >>> SDK\ODBC\170\Tools\Binn\;C:\Program
> >>> Files\PowerShell\7-preview\preview;C:\Program Files
> >>> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\nek
> >>> o;C:\Program Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R)
> >>> Management Engine Components\DAL;C:\Program Files\Intel\Intel(R)
> >>> Management Engine Components\DAL;C:\Program Files (x86)\Pulse
> >>> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
> >>> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
> >>> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
> >>> Server\130\Tools\Binn\;C:\Program Files
> >>> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;
> >>> C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dot
> >>> net\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Use
> >>> rs\hiedra\AppData\Local\Programs\Microsoft
> >>> VS
> >>> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppD
> >>> ata\Roaming\npm
> >>>
> >>> BUILD FAILED
> >>>
> >>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796:
> >>> The following error occurred while executing this line:
> >>>
> >>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809:
> >>> exec
> >>> returned: 1
> >>>
> >>> Total time: 39 minutes 52 seconds
> >>> >>>
> >>>
> >>> The error occurs in the Maven compilation task (it's in the path,
> >>> could it be because of the maven version?):
> >>>
> >>> >>>
> >>> ...
> >>> 
> 

RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Maria Jose Esteve]

can I test this "ApproveRoyale.xml" with RC4 Josh?
Hiedra

-Mensaje original-
De: Josh Tynjala  
Enviado el: lunes, 15 de mayo de 2023 20:04
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

That being said, I have updated the approval script in the royale-asjs Git 
repo. You should be able to use it with this existing RC, if you'd like.

https://github.com/apache/royale-asjs/blob/develop/ApproveRoyale.xml

--
Josh Tynjala
Bowler Hat LLC 


On Mon, May 15, 2023 at 9:35 AM Josh Tynjala 
wrote:

> Now that I've had my morning tea, I remember now that I put 
> RoyaleUnit's dependencies into a separate directory so that they don't 
> conflict with anything else (and so that they aren't loaded by the 
> compiler when they aren't needed). I didn't know that I needed to 
> update ApproveRoyale.xml. I will get that fixed for *future* releases.
>
> For now, this is just a minor issue, and it should not prevent you 
> from voting in favor of this RC. The license is actually allowed, but "Rat"
> incorrectly flags it. The approval script will not fail when it 
> mentions this license, so we don't need to do anything to fix it 
> immediately.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Mon, May 15, 2023 at 8:55 AM Josh Tynjala 
> 
> wrote:
>
>> The approval script excludes dom4j-LICENSE.txt at the following location:
>>
>> 
>>
>> But your path is slightly different:
>>
>> royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
>>
>> I think we can just make a minor tweak to the approval script to add 
>> this path too:
>>
>> 
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC 
>>
>>
>> On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve 
>> wrote:
>>
>>> Hi,
>>> I keep testing the automated compilation option [1] the compilation 
>>> gave me error ☹.
>>> I have left the log of the compilation here [2] but I attach the error:
>>>
>>> <<<
>>> ...
>>> main:
>>> Copying 1 file to
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
>>> Copying 1 file to
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-sr
>>> c\royale-asjs\examples\native\USStatesMap\bin\js-release
>>>
>>> main:
>>>
>>> build_maven:
>>> Path is C:\Program Files (x86)\Common 
>>> Files\Oracle\Java\javapath;D:\Apache;C:\Program
>>> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apac
>>> he\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client
>>> _1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Wi
>>> ndows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;
>>> C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
>>> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbe
>>> m;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\Op
>>> enSSH\;C:\Program 
>>> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS 
>>> Code;C:\Program Files\Microsoft SQL Server\Client 
>>> SDK\ODBC\170\Tools\Binn\;C:\Program
>>> Files\PowerShell\7-preview\preview;C:\Program Files 
>>> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\nek
>>> o;C:\Program Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) 
>>> Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) 
>>> Management Engine Components\DAL;C:\Program Files (x86)\Pulse 
>>> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse 
>>> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL 
>>> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL 
>>> Server\130\Tools\Binn\;C:\Program Files 
>>> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;
>>> C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dot
>>> net\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Use
>>> rs\hiedra\AppData\Local\Programs\Microsoft
>>> VS
>>> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppD
>>> ata\Roaming\npm
>>>
>>> BUILD FAILED
>>>
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: 
>>> The following error occurred while executing this line:
>>>
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809: 
>>> exec
>>> returned: 1
>>>
>>> Total time: 39 minutes 52 seconds
>>> >>>
>>>
>>> The error occurs in the Maven compilation task (it's in the path, 
>>> could it be because of the maven version?):
>>>
>>> >>>
>>> ...
>>> 
>>> >> value="-Poption-with-swf"
>>> else="-Ddummy=true">
>>> 
>>> 
>>> >> value="-Pwith-examples,with-distribution,option-with-swf"
>>> else="-Pwith-examples,with-distribution">
>>> 
>>> 
>>> Path is ${env.Path}
>>>
>>> -- >>>>> inputstring="Yes">
>>> 
>>> 
>>> 
>>> 
>>> 
>>>   

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

> Does anyone have any idea what has happened here ? Why
TileHorizontalLayout
> after compilation to TileHorizontalLayout.js have all of these methods ?

TileHorizontallayout has [Bindable] metadata on some properties. If
anything in a class is marked as [Bindable], and that class (or a
superclass) does not already extend EventDispatcher (or implement
IEventDispatcher), the compiler will automatically generate an
implementation of IEventDispatcher. This is true in Royale, and it was also
true in Flex.

Here are the classes that TileHorizontalLayout is a subclass of:
TileHorizontalLayout extends SimpleHorizontalLayout extends
StyledLayoutBase extends LayoutBase extends Bead

There are also the following interfaces in the type hierarchy:
ILayoutStyleProperties, IBeadLayout, IBead

Nowhere in this chain of classes is there an EventDispatcher or
IEventDispatcher. So the compiler is generating its own implementation of
IEventDispatcher.

Unfortunately, it seems to be generating an implementation of the methods
from the SWF version of IEventDispatcher instead of the methods from the JS
version of IEventDispatcher. I don't believe that I have worked with the
part of the Royale compiler that generates code for bindable
classes/properties before, so I don't know why it would be doing that.
However, that seems like a bug. Maybe not necessarily in the compiler. It
could be that the compiler options used by the JewelJS build are wrong.

Note: I don't think that the compiler is incorrectly using the Spark
version of LayoutBase instead of the Core version of LayoutBase. This can
be explained without the Spark version of LayoutBase being involved in any
way.

--
Josh Tynjala
Bowler Hat LLC 


On Mon, May 15, 2023 at 5:14 AM Piotr Zarzycki 
wrote:

> Hi Guys,
>
> I have voted +1, but I have found one issue which concerns me a little bit.
> I have need of usage in my application
> -> org.apache.royale.jewel.beads.layouts.TileHorizontalLayout. I have made
> my own custom class which extends that one. To my big surprise I got
> following compilation error:
>
>  Error: interface method addEventListener in interface IEventDispatcher is
> implemented with an incompatible signature in class
> ExtendedTileHorizontalLayout
> : Error: interface method removeEventListener in interface IEventDispatcher
> is implemented with an incompatible signature in class
> ExtendedTileHorizontalLayout
> : Error: interface method dispatchEvent in interface IEventDispatcher is
> implemented with an incompatible signature in class
> ExtendedTileHorizontalLayout
>
> I have looked into TileHorizontalLayout in Moonshine and I see there
> signature methods -> https://prnt.sc/crcNcuFHgu-8
>
> Look int signatures dispatchEvent, hasEventListener, removeEventListener
> and addEventListener - they are all missing fields name. This is definitely
> wrong, but I think all of these methods shouldn't even exists in
> frameworks/js/libs/JewelJS.swc -> TileHorizontalLayout.
>
> TileHorizontalLayout extends several classes, one of them
> is org.apache.royale.core.LayoutBase - non of these classes have anywhere
> inside methods dispatchEvent, hasEventListener etc. However there is
> another class in completely different
> package spark.layouts.supportClasses.LayoutBase - that one have these
> methods implemented exactly in the same way as my TileHorizontalLayout.js
> have.
>
> Does anyone have any idea what has happened here ? Why TileHorizontalLayout
> after compilation to TileHorizontalLayout.js have all of these methods ?
>
> Thanks,
> Piotr
>
>
> niedz., 14 maj 2023 o 03:29 Maria Jose Esteve 
> napisał(a):
>
> > Hi,
> > I keep testing the automated compilation option [1] the compilation gave
> > me error ☹.
> > I have left the log of the compilation here [2] but I attach the error:
> >
> > <<<
> > ...
> > main:
> > Copying 1 file to
> >
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
> > Copying 1 file to
> >
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release
> >
> > main:
> >
> > build_maven:
> > Path is C:\Program Files (x86)\Common
> > Files\Oracle\Java\javapath;D:\Apache;C:\Program
> >
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
> > Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> >
> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
> > Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> > Code;C:\Program Files\Microsoft SQL Server\Client
> > 

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Piotr Zarzycki]

Hi Harbs,

I did my first attempt of implementation in a simple Hello World, so the
answer is no I don't use Spark in my app. This code come to me with
framework. If you download official build 0.9.10 [1] and unpack
frameworks/js/libs/JewelJS.swc you will find in TileHorizontalLayout
unnecessary code.

Why compiler "confuses" all of that.

[1] https://nightlies.apache.org/Royale/Royale-asjs/

pon., 15 maj 2023 o 18:39 Harbs  napisał(a):

> Yes. That is somewhat concerning.
>
> Are you using Spark anywhere in your application?
>
> > On May 15, 2023, at 3:13 PM, Piotr Zarzycki 
> wrote:
> >
> > Hi Guys,
> >
> > I have voted +1, but I have found one issue which concerns me a little
> bit.
> > I have need of usage in my application
> > -> org.apache.royale.jewel.beads.layouts.TileHorizontalLayout. I have
> made
> > my own custom class which extends that one. To my big surprise I got
> > following compilation error:
> >
> > Error: interface method addEventListener in interface IEventDispatcher is
> > implemented with an incompatible signature in class
> > ExtendedTileHorizontalLayout
> > : Error: interface method removeEventListener in interface
> IEventDispatcher
> > is implemented with an incompatible signature in class
> > ExtendedTileHorizontalLayout
> > : Error: interface method dispatchEvent in interface IEventDispatcher is
> > implemented with an incompatible signature in class
> > ExtendedTileHorizontalLayout
> >
> > I have looked into TileHorizontalLayout in Moonshine and I see there
> > signature methods -> https://prnt.sc/crcNcuFHgu-8
> >
> > Look int signatures dispatchEvent, hasEventListener, removeEventListener
> > and addEventListener - they are all missing fields name. This is
> definitely
> > wrong, but I think all of these methods shouldn't even exists in
> > frameworks/js/libs/JewelJS.swc -> TileHorizontalLayout.
> >
> > TileHorizontalLayout extends several classes, one of them
> > is org.apache.royale.core.LayoutBase - non of these classes have anywhere
> > inside methods dispatchEvent, hasEventListener etc. However there is
> > another class in completely different
> > package spark.layouts.supportClasses.LayoutBase - that one have these
> > methods implemented exactly in the same way as my TileHorizontalLayout.js
> > have.
> >
> > Does anyone have any idea what has happened here ? Why
> TileHorizontalLayout
> > after compilation to TileHorizontalLayout.js have all of these methods ?
> >
> > Thanks,
> > Piotr
> >
> >
> > niedz., 14 maj 2023 o 03:29 Maria Jose Esteve 
> > napisał(a):
> >
> >> Hi,
> >> I keep testing the automated compilation option [1] the compilation gave
> >> me error ☹.
> >> I have left the log of the compilation here [2] but I attach the error:
> >>
> >> <<<
> >> ...
> >>main:
> >>Copying 1 file to
> >>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
> >>Copying 1 file to
> >>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release
> >>
> >>main:
> >>
> >>build_maven:
> >>Path is C:\Program Files (x86)\Common
> >> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> >>
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
> >> Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> >>
> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
> >> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> >> Code;C:\Program Files\Microsoft SQL Server\Client
> >> SDK\ODBC\170\Tools\Binn\;C:\Program
> >> Files\PowerShell\7-preview\preview;C:\Program Files
> >>
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
> >> Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine
> >> Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine
> >> Components\DAL;C:\Program Files (x86)\Pulse
> >> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
> >> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
> >> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
> >> Server\130\Tools\Binn\;C:\Program Files
> >>
> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> >> VS
> >>
> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm
> >>
> >>BUILD FAILED
> >>
> >> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: The
> >> following error occurred while executing 

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

That being said, I have updated the approval script in the royale-asjs Git
repo. You should be able to use it with this existing RC, if you'd like.

https://github.com/apache/royale-asjs/blob/develop/ApproveRoyale.xml

--
Josh Tynjala
Bowler Hat LLC 


On Mon, May 15, 2023 at 9:35 AM Josh Tynjala 
wrote:

> Now that I've had my morning tea, I remember now that I put
> RoyaleUnit's dependencies into a separate directory so that they don't
> conflict with anything else (and so that they aren't loaded by the compiler
> when they aren't needed). I didn't know that I needed to update
> ApproveRoyale.xml. I will get that fixed for *future* releases.
>
> For now, this is just a minor issue, and it should not prevent you from
> voting in favor of this RC. The license is actually allowed, but "Rat"
> incorrectly flags it. The approval script will not fail when it
> mentions this license, so we don't need to do anything to fix it
> immediately.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Mon, May 15, 2023 at 8:55 AM Josh Tynjala 
> wrote:
>
>> The approval script excludes dom4j-LICENSE.txt at the following location:
>>
>> 
>>
>> But your path is slightly different:
>>
>> royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
>>
>> I think we can just make a minor tweak to the approval script to add this
>> path too:
>>
>> 
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC 
>>
>>
>> On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve 
>> wrote:
>>
>>> Hi,
>>> I keep testing the automated compilation option [1] the compilation gave
>>> me error ☹.
>>> I have left the log of the compilation here [2] but I attach the error:
>>>
>>> <<<
>>> ...
>>> main:
>>> Copying 1 file to
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
>>> Copying 1 file to
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release
>>>
>>> main:
>>>
>>> build_maven:
>>> Path is C:\Program Files (x86)\Common
>>> Files\Oracle\Java\javapath;D:\Apache;C:\Program
>>> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
>>> Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
>>> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
>>> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
>>> Code;C:\Program Files\Microsoft SQL Server\Client
>>> SDK\ODBC\170\Tools\Binn\;C:\Program
>>> Files\PowerShell\7-preview\preview;C:\Program Files
>>> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
>>> Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine
>>> Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine
>>> Components\DAL;C:\Program Files (x86)\Pulse
>>> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
>>> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
>>> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
>>> Server\130\Tools\Binn\;C:\Program Files
>>> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\Programs\Microsoft
>>> VS
>>> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm
>>>
>>> BUILD FAILED
>>>
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: The
>>> following error occurred while executing this line:
>>>
>>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809: exec
>>> returned: 1
>>>
>>> Total time: 39 minutes 52 seconds
>>> >>>
>>>
>>> The error occurs in the Maven compilation task (it's in the path, could
>>> it be because of the maven version?):
>>>
>>> >>>
>>> ...
>>> 
>>> >> value="-Poption-with-swf"
>>> else="-Ddummy=true">
>>> 
>>> 
>>> >> value="-Pwith-examples,with-distribution,option-with-swf"
>>> else="-Pwith-examples,with-distribution">
>>> 
>>> 
>>> Path is ${env.Path}
>>>
>>> -- >>>>> inputstring="Yes">
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> >> inputstring="Yes">
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ...
>>> <<<
>>>
>>> I have a question about licenses... Yishay has no anomalies in this
>>> regard but I have an unapproved license:
>>> Unapproved licenses:

RE: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Maria Jose Esteve]

Ok Josh, thx

Hiedra

-Mensaje original-
De: Josh Tynjala  
Enviado el: lunes, 15 de mayo de 2023 18:35
Para: dev@royale.apache.org
Asunto: Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

Now that I've had my morning tea, I remember now that I put RoyaleUnit's 
dependencies into a separate directory so that they don't conflict with 
anything else (and so that they aren't loaded by the compiler when they aren't 
needed). I didn't know that I needed to update ApproveRoyale.xml. I will get 
that fixed for *future* releases.

For now, this is just a minor issue, and it should not prevent you from voting 
in favor of this RC. The license is actually allowed, but "Rat"
incorrectly flags it. The approval script will not fail when it mentions this 
license, so we don't need to do anything to fix it immediately.

--
Josh Tynjala
Bowler Hat LLC 


On Mon, May 15, 2023 at 8:55 AM Josh Tynjala 
wrote:

> The approval script excludes dom4j-LICENSE.txt at the following location:
>
> 
>
> But your path is slightly different:
>
> royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
>
> I think we can just make a minor tweak to the approval script to add 
> this path too:
>
> 
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve 
> wrote:
>
>> Hi,
>> I keep testing the automated compilation option [1] the compilation 
>> gave me error ☹.
>> I have left the log of the compilation here [2] but I attach the error:
>>
>> <<<
>> ...
>> main:
>> Copying 1 file to
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
>> Copying 1 file to
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src
>> \royale-asjs\examples\native\USStatesMap\bin\js-release
>>
>> main:
>>
>> build_maven:
>> Path is C:\Program Files (x86)\Common 
>> Files\Oracle\Java\javapath;D:\Apache;C:\Program
>> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apach
>> e\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1
>> \bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windo
>> ws\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\P
>> rogram Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
>> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
>> ;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\Open
>> SSH\;C:\Program 
>> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS 
>> Code;C:\Program Files\Microsoft SQL Server\Client 
>> SDK\ODBC\170\Tools\Binn\;C:\Program
>> Files\PowerShell\7-preview\preview;C:\Program Files 
>> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko
>> ;C:\Program Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) 
>> Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) 
>> Management Engine Components\DAL;C:\Program Files (x86)\Pulse 
>> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse 
>> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL 
>> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL 
>> Server\130\Tools\Binn\;C:\Program Files 
>> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C
>> :\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotne
>> t\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\
>> hiedra\AppData\Local\Programs\Microsoft
>> VS
>> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppDa
>> ta\Roaming\npm
>>
>> BUILD FAILED
>>
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: 
>> The following error occurred while executing this line:
>>
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809: 
>> exec
>> returned: 1
>>
>> Total time: 39 minutes 52 seconds
>> >>>
>>
>> The error occurs in the Maven compilation task (it's in the path, 
>> could it be because of the maven version?):
>>
>> >>>
>> ...
>> 
>> > value="-Poption-with-swf"
>> else="-Ddummy=true">
>> 
>> 
>> > value="-Pwith-examples,with-distribution,option-with-swf"
>> else="-Pwith-examples,with-distribution">
>> 
>> 
>> Path is ${env.Path}
>>
>> -- >>>> inputstring="Yes">
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> > inputstring="Yes">
>> 
>> 
>> 
>> 
>> 
>> ...
>> <<<
>>
>> I have a question about licenses... Yishay has no anomalies in this 
>> regard but I have an unapproved license:
>> Unapproved licenses:
>>
>>  
>> D:/Develop_Royale/Projects/Royale-SDK/0.9.10/apache-royale-0.9.10-bin
>> -js-swf/royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
>> How can I fix it?
>>
>> [1]
>> 

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Harbs]

Yes. That is somewhat concerning.

Are you using Spark anywhere in your application?

> On May 15, 2023, at 3:13 PM, Piotr Zarzycki  wrote:
> 
> Hi Guys,
> 
> I have voted +1, but I have found one issue which concerns me a little bit.
> I have need of usage in my application
> -> org.apache.royale.jewel.beads.layouts.TileHorizontalLayout. I have made
> my own custom class which extends that one. To my big surprise I got
> following compilation error:
> 
> Error: interface method addEventListener in interface IEventDispatcher is
> implemented with an incompatible signature in class
> ExtendedTileHorizontalLayout
> : Error: interface method removeEventListener in interface IEventDispatcher
> is implemented with an incompatible signature in class
> ExtendedTileHorizontalLayout
> : Error: interface method dispatchEvent in interface IEventDispatcher is
> implemented with an incompatible signature in class
> ExtendedTileHorizontalLayout
> 
> I have looked into TileHorizontalLayout in Moonshine and I see there
> signature methods -> https://prnt.sc/crcNcuFHgu-8
> 
> Look int signatures dispatchEvent, hasEventListener, removeEventListener
> and addEventListener - they are all missing fields name. This is definitely
> wrong, but I think all of these methods shouldn't even exists in
> frameworks/js/libs/JewelJS.swc -> TileHorizontalLayout.
> 
> TileHorizontalLayout extends several classes, one of them
> is org.apache.royale.core.LayoutBase - non of these classes have anywhere
> inside methods dispatchEvent, hasEventListener etc. However there is
> another class in completely different
> package spark.layouts.supportClasses.LayoutBase - that one have these
> methods implemented exactly in the same way as my TileHorizontalLayout.js
> have.
> 
> Does anyone have any idea what has happened here ? Why TileHorizontalLayout
> after compilation to TileHorizontalLayout.js have all of these methods ?
> 
> Thanks,
> Piotr
> 
> 
> niedz., 14 maj 2023 o 03:29 Maria Jose Esteve 
> napisał(a):
> 
>> Hi,
>> I keep testing the automated compilation option [1] the compilation gave
>> me error ☹.
>> I have left the log of the compilation here [2] but I attach the error:
>> 
>> <<<
>> ...
>>main:
>>Copying 1 file to
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
>>Copying 1 file to
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release
>> 
>>main:
>> 
>>build_maven:
>>Path is C:\Program Files (x86)\Common
>> Files\Oracle\Java\javapath;D:\Apache;C:\Program
>> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
>> Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
>> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
>> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
>> Code;C:\Program Files\Microsoft SQL Server\Client
>> SDK\ODBC\170\Tools\Binn\;C:\Program
>> Files\PowerShell\7-preview\preview;C:\Program Files
>> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
>> Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine
>> Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine
>> Components\DAL;C:\Program Files (x86)\Pulse
>> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
>> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
>> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
>> Server\130\Tools\Binn\;C:\Program Files
>> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\Programs\Microsoft
>> VS
>> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm
>> 
>>BUILD FAILED
>> 
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: The
>> following error occurred while executing this line:
>> 
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809: exec
>> returned: 1
>> 
>>Total time: 39 minutes 52 seconds
> 
>> 
>> The error occurs in the Maven compilation task (it's in the path, could it
>> be because of the maven version?):
>> 
> 
>> ...
>>
>>> value="-Poption-with-swf"
>>else="-Ddummy=true">
>>
>>
>>> value="-Pwith-examples,with-distribution,option-with-swf"
>>else="-Pwith-examples,with-distribution">
>>
>>
>>Path is ${env.Path}
>> 
>> -- >>>> 

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

Now that I've had my morning tea, I remember now that I put
RoyaleUnit's dependencies into a separate directory so that they don't
conflict with anything else (and so that they aren't loaded by the compiler
when they aren't needed). I didn't know that I needed to update
ApproveRoyale.xml. I will get that fixed for *future* releases.

For now, this is just a minor issue, and it should not prevent you from
voting in favor of this RC. The license is actually allowed, but "Rat"
incorrectly flags it. The approval script will not fail when it
mentions this license, so we don't need to do anything to fix it
immediately.

--
Josh Tynjala
Bowler Hat LLC 


On Mon, May 15, 2023 at 8:55 AM Josh Tynjala 
wrote:

> The approval script excludes dom4j-LICENSE.txt at the following location:
>
> 
>
> But your path is slightly different:
>
> royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
>
> I think we can just make a minor tweak to the approval script to add this
> path too:
>
> 
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve 
> wrote:
>
>> Hi,
>> I keep testing the automated compilation option [1] the compilation gave
>> me error ☹.
>> I have left the log of the compilation here [2] but I attach the error:
>>
>> <<<
>> ...
>> main:
>> Copying 1 file to
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
>> Copying 1 file to
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release
>>
>> main:
>>
>> build_maven:
>> Path is C:\Program Files (x86)\Common
>> Files\Oracle\Java\javapath;D:\Apache;C:\Program
>> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
>> Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
>> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
>> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
>> Code;C:\Program Files\Microsoft SQL Server\Client
>> SDK\ODBC\170\Tools\Binn\;C:\Program
>> Files\PowerShell\7-preview\preview;C:\Program Files
>> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
>> Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine
>> Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine
>> Components\DAL;C:\Program Files (x86)\Pulse
>> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
>> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
>> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
>> Server\130\Tools\Binn\;C:\Program Files
>> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\Programs\Microsoft
>> VS
>> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm
>>
>> BUILD FAILED
>>
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: The
>> following error occurred while executing this line:
>>
>> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809: exec
>> returned: 1
>>
>> Total time: 39 minutes 52 seconds
>> >>>
>>
>> The error occurs in the Maven compilation task (it's in the path, could
>> it be because of the maven version?):
>>
>> >>>
>> ...
>> 
>> > value="-Poption-with-swf"
>> else="-Ddummy=true">
>> 
>> 
>> > value="-Pwith-examples,with-distribution,option-with-swf"
>> else="-Pwith-examples,with-distribution">
>> 
>> 
>> Path is ${env.Path}
>>
>> -- >>>> inputstring="Yes">
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> > inputstring="Yes">
>> 
>> 
>> 
>> 
>> 
>> ...
>> <<<
>>
>> I have a question about licenses... Yishay has no anomalies in this
>> regard but I have an unapproved license:
>> Unapproved licenses:
>>
>>  
>> D:/Develop_Royale/Projects/Royale-SDK/0.9.10/apache-royale-0.9.10-bin-js-swf/royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
>> How can I fix it?
>>
>> [1]
>> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/ApproveRoyale.xml
>> y ejecutando el script:
>>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.10 -Drc=4
>> [2]
>> https://drive.google.com/file/d/1jCgS51cgtRSSuh11UJUxzdEaburpDdpF/view?usp=share_link
>>
>> Hiedra
>>
>> -Mensaje 

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Josh Tynjala]

The approval script excludes dom4j-LICENSE.txt at the following location:



But your path is slightly different:

royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt

I think we can just make a minor tweak to the approval script to add this
path too:



--
Josh Tynjala
Bowler Hat LLC 


On Sat, May 13, 2023 at 6:29 PM Maria Jose Esteve  wrote:

> Hi,
> I keep testing the automated compilation option [1] the compilation gave
> me error ☹.
> I have left the log of the compilation here [2] but I attach the error:
>
> <<<
> ...
> main:
> Copying 1 file to
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
> Copying 1 file to
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release
>
> main:
>
> build_maven:
> Path is C:\Program Files (x86)\Common
> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
> Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> Code;C:\Program Files\Microsoft SQL Server\Client
> SDK\ODBC\170\Tools\Binn\;C:\Program
> Files\PowerShell\7-preview\preview;C:\Program Files
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
> Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine
> Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine
> Components\DAL;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
> Server\130\Tools\Binn\;C:\Program Files
> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> VS
> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm
>
> BUILD FAILED
>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: The
> following error occurred while executing this line:
>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809: exec
> returned: 1
>
> Total time: 39 minutes 52 seconds
> >>>
>
> The error occurs in the Maven compilation task (it's in the path, could it
> be because of the maven version?):
>
> >>>
> ...
> 
>  value="-Poption-with-swf"
> else="-Ddummy=true">
> 
> 
>  value="-Pwith-examples,with-distribution,option-with-swf"
> else="-Pwith-examples,with-distribution">
> 
> 
> Path is ${env.Path}
>
> -- >>> inputstring="Yes">
> 
> 
> 
> 
>  dir="${basedir}/${maven.package.url.name}/royale-typedefs"
> failonerror="true" >
> 
> 
> 
>  dir="${basedir}/${maven.package.url.name}/royale-asjs"
> failonerror="true" inputstring="Yes">
> 
> 
> 
> 
> 
> ...
> <<<
>
> I have a question about licenses... Yishay has no anomalies in this regard
> but I have an unapproved license:
> Unapproved licenses:
>
>  
> D:/Develop_Royale/Projects/Royale-SDK/0.9.10/apache-royale-0.9.10-bin-js-swf/royale-asjs/js/lib/royaleunit/dom4j-LICENSE.txt
> How can I fix it?
>
> [1]
> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/ApproveRoyale.xml
> y ejecutando el script:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.10 -Drc=4
> [2]
> https://drive.google.com/file/d/1jCgS51cgtRSSuh11UJUxzdEaburpDdpF/view?usp=share_link
>
> Hiedra
>
> -Mensaje original-
> De: Yishay Weiss 
> Enviado el: sábado, 13 de mayo de 2023 19:36
> Para: dev@royale.apache.org
> Asunto: [DISCUSS] Release Apache Royale 0.9.10 RC4
>
> This is the discussion thread.
>

Re: [DISCUSS] Release Apache Royale 0.9.10 RC4

[Piotr Zarzycki]

Hi Guys,

I have voted +1, but I have found one issue which concerns me a little bit.
I have need of usage in my application
-> org.apache.royale.jewel.beads.layouts.TileHorizontalLayout. I have made
my own custom class which extends that one. To my big surprise I got
following compilation error:

 Error: interface method addEventListener in interface IEventDispatcher is
implemented with an incompatible signature in class
ExtendedTileHorizontalLayout
: Error: interface method removeEventListener in interface IEventDispatcher
is implemented with an incompatible signature in class
ExtendedTileHorizontalLayout
: Error: interface method dispatchEvent in interface IEventDispatcher is
implemented with an incompatible signature in class
ExtendedTileHorizontalLayout

I have looked into TileHorizontalLayout in Moonshine and I see there
signature methods -> https://prnt.sc/crcNcuFHgu-8

Look int signatures dispatchEvent, hasEventListener, removeEventListener
and addEventListener - they are all missing fields name. This is definitely
wrong, but I think all of these methods shouldn't even exists in
frameworks/js/libs/JewelJS.swc -> TileHorizontalLayout.

TileHorizontalLayout extends several classes, one of them
is org.apache.royale.core.LayoutBase - non of these classes have anywhere
inside methods dispatchEvent, hasEventListener etc. However there is
another class in completely different
package spark.layouts.supportClasses.LayoutBase - that one have these
methods implemented exactly in the same way as my TileHorizontalLayout.js
have.

Does anyone have any idea what has happened here ? Why TileHorizontalLayout
after compilation to TileHorizontalLayout.js have all of these methods ?

Thanks,
Piotr


niedz., 14 maj 2023 o 03:29 Maria Jose Esteve 
napisał(a):

> Hi,
> I keep testing the automated compilation option [1] the compilation gave
> me error ☹.
> I have left the log of the compilation here [2] but I attach the error:
>
> <<<
> ...
> main:
> Copying 1 file to
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-debug
> Copying 1 file to
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\apache-royale-0.9.10-src\royale-asjs\examples\native\USStatesMap\bin\js-release
>
> main:
>
> build_maven:
> Path is C:\Program Files (x86)\Common
> Files\Oracle\Java\javapath;D:\Apache;C:\Program
> Files\Java\jdk1.8.0_281\bin;D:\Apache\apache-ant-1.10.13\bin;D:\Apache\apache-maven-3.9.1\bin;D:\app\client\hiedra\product\19.0.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program
> Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program
> Files\dotnet\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
> Files\Git\cmd;C:\Users\hiedra\AppData\Local\Programs\Microsoft VS
> Code;C:\Program Files\Microsoft SQL Server\Client
> SDK\ODBC\170\Tools\Binn\;C:\Program
> Files\PowerShell\7-preview\preview;C:\Program Files
> (x86)\Yarn\bin\;D:\Apache\HaxeToolkit\haxe;D:\Apache\HaxeToolkit\neko;C:\Program
> Files\nodejs\;C:\Program Files (x86)\Intel\Intel(R) Management Engine
> Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine
> Components\DAL;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X64\;C:\Program Files (x86)\Pulse
> Secure\VC142.CRT\X86\;C:\Program Files\Microsoft SQL
> Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL
> Server\130\Tools\Binn\;C:\Program Files
> (x86)\GnuPG\bin;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\GitHubDesktop\bin;C:\Users\hiedra\.dotnet\tools;C:\Users\hiedra\AppData\Local\Microsoft\WindowsApps;C:\Users\hiedra\AppData\Local\Programs\Microsoft
> VS
> Code\bin;C:\Users\hiedra\AppData\Local\Yarn\bin;C:\Users\hiedra\AppData\Roaming\npm
>
> BUILD FAILED
>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:796: The
> following error occurred while executing this line:
>
> D:\Develop_Royale\Projects\Royale-SDK\0.9.10\ApproveRoyale.xml:809: exec
> returned: 1
>
> Total time: 39 minutes 52 seconds
> >>>
>
> The error occurs in the Maven compilation task (it's in the path, could it
> be because of the maven version?):
>
> >>>
> ...
> 
>  value="-Poption-with-swf"
> else="-Ddummy=true">
> 
> 
>  value="-Pwith-examples,with-distribution,option-with-swf"
> else="-Pwith-examples,with-distribution">
> 
> 
> Path is ${env.Path}
>
> -- >>> inputstring="Yes">
> 
> 
> 
> 
>  dir="${basedir}/${maven.package.url.name}/royale-typedefs"
> failonerror="true" >
> 
> 
> 
>  dir="${basedir}/${maven.package.url.name}/royale-asjs"
> failonerror="true" 

Re: [VOTE] Release Apache Royale 0.9.10 RC4

[Piotr Zarzycki]

+1 (Binding)

Package
https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/apache-royale-0.9.10-src.tar.gz

Java 9

OS: Mac OS X x86_64 13.3.1

Source kit signatures match: y

Source kit builds: y

README is ok: y

RELEASE_NOTES is ok: y

NOTICE is ok: y

LICENSE is ok: y

No unapproved licenses or archives: y

No unapproved binaries: y


Package
https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/binaries/apache-royale-0.9.10-bin-js-swf.tar.gz

Binary kit signatures match: y

NOTICE is ok: y

LICENSE is ok: y

No unapproved licenses or archives in binary package: y

No unapproved binaries in binary package: y

I have made additional tests:

1) Binaries build by Ant were used to open, build and run in Moonshine two
large Royale applications

2) I have used Maven deployed artifacts to build and run two Royale
applications


Thanks,

Piotr

sob., 13 maj 2023 o 19:38 Yishay Weiss  napisał(a):

> +1
> Package
> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/apache-royale-0.9.10-src.zip
> Java 17
> OS: Windows 11 amd64 10.0
> Source kit signatures match: y
> Source kit builds: y
> README is ok: y
> RELEASE_NOTES is ok: y
> NOTICE is ok: y
> LICENSE is ok: y
> No unapproved licenses or archives: y
> No unapproved binaries: y
>
> Package
> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/binaries/apache-royale-0.9.10-bin-js-swf.zip
> Binary kit signatures match: y
> NOTICE is ok: y
> LICENSE is ok: y
> No unapproved licenses or archives in binary package: y
> No unapproved binaries in binary package: y
>
> 
> From: Yishay Weiss 
> Sent: Saturday, May 13, 2023 8:35 PM
> To: dev@royale.apache.org 
> Subject: [VOTE] Release Apache Royale 0.9.10 RC4
>
> Hi,
> This is the vote for the 0.9.10 release of Apache Royale.  The release
> candidate can be found here;
> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/
>
> Before voting please review the section,'What are the ASF requirements on
> approving a release?', at:
> http://www.apache.org/dev/release.html#approving-a-release
>
> At a minimum you would be expected to check that:
> - SHA and signed packages are correct
> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
> - That the build script completes successfully
> - That you can compile and crosscompile a simple example using the SDK.
>
> The KEYS file is at https://dist.apache.org/repos/dist/release/royale/KEYS
>
> The source package is a combination of the 3 main Royale repos.
>
> To use the binary package, unzip it into a folder. The -js package is
> ready-to-use in an IDE or command-line. If you need SWF output, use the
> -js-swf package and use Apache Ant to run the InstallAdobeSDKs script via:
> ant -f InstallAdobeSDKs.xml
>
> You may also get the binarypackages via NPM. The -js package can be
> installed via:
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/binaries/apache-royale-0.9.10-bin-js.tar.gz
>
> The full package with SWF support can be installed via:
>
> npm install
> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/binaries/apache-royale-0.9.10-bin-js-swf.tar.gz
>
> Maven artifacts are staged here:
> https://repository.apache.org/content/repositories/orgapacheroyale-1096
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Disapprove the release (please provide specific comments to why)
>
> This vote will be open for 72 hours or until a result can be called.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> Remember that this is a 'beta-quality' release so expect there will be
> many bugs found. IMO the goal is not to try to find and fix bugs in the RC,
> but to make sure we have the packaging right, and enough functionality that
> folks will have some success trying to use it.  People who are not in PMC
> are also encouraged to test out the release and vote, although their votes
> will not be binding, they can influence how the PMC votes.
>
> When voting please indicate what OS, IDE, Flash Player version and AIR
> version you tested with.
>
> For your convenience, there is an ant script that automates the common
> steps to validate a release.  Instead of individually downloading the
> package and signature files, unzipping, etc, you can instead:
> 1) create an empty folder,
> 2) download into that folder this file:
> https://dist.apache.org/repos/dist/dev/royale/0.9.10/rc4/ApproveRoyale.xml
> 3) run the script:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.10 -Drc=4
>If you want to test SWF support during the approval, use:
>ant -e -f ApproveRoyale.xml -Drelease.version=0.9.10 -Drc=4
> -Duse-flash=true
>
> You are not required to use this script, and more testing of the packages
> and build results are always encouraged.
>
> Please put all discussion about this release in the DISCUSSION thread not
> this VOTE thread.
>
> Thanks,
> Yishay Weiss
>
>

-- 

Piotr Zarzycki