Build failed in Jenkins: royale-asjs_MXTests #1163

See -- [...truncated 1000.72 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

I'm going to push fixes for release steps script today and make RC2. If I figure out how to export gpg KEY in a proper format as it is in KEYS file I will update them as well - if not people can use Josh's way of getting my key for now. śr., 18 wrz 2019 o 07:20 Alex Harui napisał(a): > I assume

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

I assume that wasn't the whole log. I think we want to see the part where it builds Core, we only see the last bit of Core. Core looks like it thought it was in js-only config and didn't build a swf swc and/or Binding thinks it is building swf swcs and is looking for Core's swf swc. FWIW, I a

Build failed in Jenkins: royale-asjs_MXTests #1162

See -- [...truncated 999.68 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning

[DISCUSS] Release Apache Royale 0.9.6 RC1

Hi Josh, Do you have in your Maven config setup link to Maven artifacts? Cause error is saying that it was attempt of downloading them from Snapshot. However Core build successfully, so I'm a bit confused. Thanks, Piotr On Tue, Sep 17, 2019, 11:47 PM Josh Tynjala wrote: > Unfortunately, I'm se

Build failed in Jenkins: royale-asjs_MXTests #1161

See Changes: [joshtynjala] CreditCardValidatorExample: fixed build script -- [...truncated 1000.13 KB...] [mxmlc] scanning for overrides

Jenkins build is back to normal : royale-asjs_jsonly #3556

See

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

Unfortunately, I'm seeing that the Maven part of ApproveRoyale is failing too. Here's the end of my console output: https://paste.apache.org/83miv -- Josh Tynjala Bowler Hat LLC On Tue, Sep 17, 2019 at 2:22 PM Josh Tynjala wrote: > Getting the following error when runn

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

I'd rather not accidentally commit something to a release branch that shouldn't go there, so to stay safe, I'll keep committing to develop first. We can always cherry pick if needed. -- Josh Tynjala Bowler Hat LLC On Tue, Sep 17, 2019 at 2:29 PM Alex Harui wrote: > Hmm.

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

Hmm. I thought I'd fixed that. I swear I had all examples building. Anyway, fixes like these should be going in the release branch, not develop, IMO. Thanks, -Alex On 9/17/19, 2:22 PM, "Josh Tynjala" wrote: Getting the following error when running the ApproveRoyale ant script...

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

Getting the following error when running the ApproveRoyale ant script... Error: unable to open '/Users/joshtynjala/Desktop/royale/apache-royale-0.9.6-src/royale-asjs/examples/royale/CreditCardValidatorExample/src/main/royale/App.mxml'. Seems to be caused by this line in build.xml from CreditCardV

Re: Release vote/discuss reply-to address

Hmm... looking at the headers in Gmail seems to indicate that reply-to is actually set to the dev list. I wonder why Gmail is ignoring it... One thing that I see is that reply-to is showing up in the UI like this: reply-to: dev@royale.apache.org, dev@royale.apache.org Maybe Gmail is getting conf

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

I downloaded the KEYS file and imported it. gpg --import KEYS However, when I ran the ApproveRoyale.xml script after that, I got this error: gpg: Signature made 09/17/19 05:01:35 Pacific Daylight Time gpg:using RSA key B0A9098B61A39B1E8D5B7C9976CF6A81D5C80F47 gpg: Can't check sig

Release vote/discuss reply-to address

I just realized that several replies that I sent to the 0.9.6 discuss thread were lost because I was unexpectedly replying to apacheroyal...@gmail.com. When the server sends out vote/discuss threads, is it possible to set the reply-to address to dev@royale.apache.org? -- Josh Tynjala Bowler Hat L

Discuss of release steps preparation

Alex, I will fix those issues once we make current release. Both of them are not a blockers in my opinion. How issue in release steps script can influence sources ? Thanks, Piotr On Tue, Sep 17, 2019, 7:29 PM Alex Harui wrote: > If you had to do that, how do you know the RC is still valid?

[DISCUSS] Release Apache Royale 0.9.6 RC1

Carlos, Could you also try to setup Maven artifacts and build your project - see if all is ok? It is the matter of setup links with artifacts in settings.xml. Set it as active profile and maybe switch in pom to 0.9.6 non Snapshot. If you will have time! Thanks, Piotr On Tue, Sep 17, 2019, 6:34

Re: Discuss of release steps preparation

If you had to do that, how do you know the RC is still valid? Sounds like there is a version number that isn't right in the source package. One reason to have scripts is to detect things that are not right. Yes there might be bugs in the scripts, but if you didn't have to do this before, it s

Re: [VOTE] Release Apache Royale 0.9.6 RC1

Hi, +1 Package https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/apache-royale-0.9.6-src.tar.gz Java 1.8.0_181 OS: Mac OS X x86_64 10.14.6 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 ar

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

Hi Piotr, is ok is in royale-asjs README repo. All ok (about gmail mixing topics, good catch...although that's very strange gmail behavior :-? ) El mar., 17 sept. 2019 a las 18:25, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Are you checking README in sources? I think those infor

[DISCUSS] Release Apache Royale 0.9.6 RC1

Are you checking README in sources? I think those information are in some release notes file not readme. On Tue, Sep 17, 2019, 6:17 PM Carlos Rovira wrote: > Hi Piotr, > > I notice this thread is VOTE and not DISCUSS. > > About celebration, I think it deserves admiration, although we know we > s

[DISCUSS] Release Apache Royale 0.9.6 RC1

Carlos, Gmail merge both topics, but if you hit Reply All and check Edit Title you can make sure that your replaying in a good subject. Check before reply. Thanks, Piotr On Tue, Sep 17, 2019, 6:17 PM Carlos Rovira wrote: > Hi Piotr, > > I notice this thread is VOTE and not DISCUSS. > > About c

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

Hi Piotr, I notice this thread is VOTE and not DISCUSS. About celebration, I think it deserves admiration, although we know we still could need a little final adjustment. But this process is about 99%, so is good to celebrate all the hard work here by Alex, Om, you and others involved :) Going t

[DISCUSS] Release Apache Royale 0.9.6 RC1

Hi Carlos, Thanks but I won't start celebrate till someone build stuff on his PC using approval script or whatever other method. I did try script. I reached the point where SDK need to be build - I left it for now to try tomorrow maybe. wt., 17 wrz 2019 o 17:02 Carlos Rovira napisał(a): > Hi,

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

Hi, congrats to reach this step! many work involved here so far! :) El mar., 17 sept. 2019 a las 15:45, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Hi Guys, > > I believe we can officially start testing, providing feedback and hopefully > voting. > > Thanks, > Piotr > > wt., 17 wrz

[DISCUSS] Release Apache Royale 0.9.6 RC1

This is the discussion thread. Thanks, Piotr

[VOTE] Release Apache Royale 0.9.6 RC1

Hi, This is the vote for the 0.9.6 release of Apache Royale. The release candidate can be found here; https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc1/ Before voting please review the section,'What are the ASF requirements on approving a release?', at: http://www.apache.org/dev/release.ht

[DISCUSS] Release Apache Royale 0.9.6 RC1

Hi Guys, I believe we can officially start testing, providing feedback and hopefully voting. Thanks, Piotr wt., 17 wrz 2019 o 15:43 Apache Royale CI Server napisał(a): > This is the discussion thread. > > Thanks, > Piotr -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki <

Build failed in Jenkins: royale-asjs_jsonly #3552

See -- [...truncated 159.64 KB...] [delete] Deleting directory C:\Program Files (x86)\Jenkins\workspace\royale-compiler\compiler-externc\target clean:

Re: Discuss of release steps preparation

Another small issue which I discovered is that I had to specify in Step 13 -Drelease.version=0.9.6 -Dreleaseversion=0.9.6 - With dot and without dot, cause script failed on compiler cloning. Thanks, Piotr wt., 17 wrz 2019 o 10:47 Piotr Zarzycki napisał(a): > Hi Guys, > > I'm in a process of upl

Release Step 013 Succeeded

>From the royale-asjs repo 1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.6 -Droyale.swc-date="9/17/19 9:06 -0800" -Dplayerglobal.version=11.7 -Dflat.donot.ask=true -Drc=1 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Valid

Re: Could @nocollapse be a solution to the -warn-public-vars issue?

Rather than having to specify a whole slew of compiler options, I’d like to see 2 or 3 compiler configurations that would set the defaults on a group of options to get the best default behavior for a use case. Maybe something like this: js-config=compatible (for maximum, compatibility with Flash

Release Step 012 Succeeded

Folder 0.9.6 already exists. Continue to next step

Re: Discuss of release steps preparation

Hi Guys, I'm in a process of uploading Maven artifacts and after upload I got following problem [1]. I will sign those artifacts manually, but this is something what should be fixed in the script for the next release. [1] https://ibb.co/zh0r5nn Thanks, Piotr niedz., 15 wrz 2019 o 08:18 Alex Har

Re: Could @nocollapse be a solution to the -warn-public-vars issue?

I personally would use a non-default setting to keep things as they are right now, but I agree with Josh in that as it is, I don't think it's a good hurdle to present to new users, or people in general that simply want things to 'work' out of the box, based on what they should reasonably expect to

RE: Async RoyaleUnit Tests

Ok, thanks for making it clear. We ended up implementing sync xhr requests. From: Josh Tynjala Sent: Monday, September 16, 2019 12:33:45 AM To: Apache Royale Development Subject: Re: Async RoyaleUnit Tests Async tests are not yet supported by RoyaleUnit. It's