The issues were with that ant build. I think I've fixed that. ________________________________ From: cont...@cristallium.com <cont...@cristallium.com> Sent: Sunday, May 7, 2023 11:24 AM To: dev@royale.apache.org <dev@royale.apache.org> Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC2
Hi, I didn't see any issues with tour de jewel. Here is what I did this morning : - Downloading 0.9.10-rc2 - Downloading java sdk 20 and ant-1.10.13 and setup env vars - Goes to royale-asjs folder and make an 'ant all' - When finish, open royale-asjs\examples\jewel\TourDeJewel with Visual Studio Code. - Add SDK 0.9.10-rc2 - Add settings.json, launch.json and tasks.json in TourDeJewel\.vscode then it run fine Could you tell me what issue do you have with TDJ ? Le 2023-05-07 08:24, Yishay Weiss a écrit : > Thanks Josh. Sounds like another RC is in order for that fix and for > updating the README. Can someone confirm tour-de-jewel example is not > working and possibly offer a fix? > ________________________________ > From: Josh Tynjala <joshtynj...@bowlerhat.dev> > Sent: Friday, May 5, 2023 7:42 PM > To: dev@royale.apache.org <dev@royale.apache.org> > Subject: Re: [DISCUSS] Release Apache Royale 0.9.10 RC2 > > This RC has a couple of issues when installing the js-swf version with > npm. > > npm install -g apache-royale-0.9.10-bin-js-swf.tar.gz > > 1) The download URLs are no longer valid for playerglobal.swc and the > Adobe > AIR SDK. At some point, Adobe stopped providing anything before version > 32.0, and we were trying to download 25.0. I fixed this issue today, in > this commit: > https://github.com/apache/royale-asjs/commit/36adf988efddbb0ad508798b0ec371e87eb7b8e9 > > 2) Newer versions of npm (since v7, I think) no longer display any > prompts > to the user when a package has a "postinstall" script. We have a > "postinstall" script that asks the user to accept Adobe's licenses and > download the binaries. By default, npm now just skips this dependency > installation entirely because it aborts the "postinstall" script when > it > tries to prompt. > > One available workaround is to tell users to add --foreground-scripts > to > the npm install command. This will show the prompts, though they are > kind > of mixed together with npm's progress bar, which isn't ideal. The user > can > optionally add --no-progress to hide the progress bar. > > Another workaround is to set the environment > variable ACCEPT_ALL_ROYALE_LICENSES to true before installing. No > prompts > required, and the "postinstall" script completes successfully. > > The first issue is the bigger one, since it prevents the SWF/JS > distribution from installing its dependencies under any circumstances. > As I > said, it's now fixed on royale-asjs develop. > > For the second issue, we can update our npm install instructions on the > website to include --foreground-scripts. It's not ideal, but we can > come up > with a better solution later. > > -- > Josh Tynjala > Bowler Hat LLC <https://bowlerhat.dev> > > On Fri, May 5, 2023 at 1:58 AM Yishay Weiss <yishayj...@hotmail.com> > wrote: > >> This is the discuss thread. --
