Build failed in Jenkins: royale-asjs_MXTests #1167

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

Build failed in Jenkins: royale-asjs_MXTests #1166

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

Build failed in Jenkins: royale-asjs_MXTests #1165

See Changes: [joshtynjala] RoyaleUnit: RunNotifierTests [joshtynjala] RoyaleUnit: fix event listener removal on MetadataRunner timer [joshtynjala] RoyaleUnit: Started implementing

Jenkins build is back to normal : royale-asjs #2714

See

New RoyaleUnit commits on develop should not go into release/0.9.6

I'm starting to add support for asynchronous tests to RoyaleUnit in the develop branch. It's still a work in progress, and things may be unstable. Please do not cherry pick any of these RoyaleUnit commits into release/ 0.9.6. Thanks! -- Josh Tynjala Bowler Hat LLC

Build failed in Jenkins: royale-asjs #2713

See Changes: [joshtynjala] RoyaleUnit: RunNotifierTests [joshtynjala] RoyaleUnit: fix event listener removal on MetadataRunner timer -- [...truncat

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

Couple of responses inline. On 9/18/19, 12:50 PM, "Greg Dove" wrote: I can see people definitely wanting to exclude it if they never use it in their app, Originally, the REFLECTION_DATA was removed if you didn't use any Reflection classes in the app. I hope that's still true. Although

Build failed in Jenkins: royale-asjs #2712

See Changes: [joshtynjala] RoyaleUnit: tests for BeforeClass and AfterClass scope [joshtynjala] RoyaleUnit: started implementing MetadataRunner architecture change to ---

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

Responses also inline. Beyond this reply, I'm going to dip out and let others contribute their ideas for a bit... because I really need to focus on other things for now. If I go silent that is why. On Thu, Sep 19, 2019 at 7:14 AM Alex Harui wrote: > Responses inline. > > On 9/18/19, 11:53 AM, "

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

Responses inline. On 9/18/19, 11:53 AM, "Greg Dove" wrote: Alex, the idea was to make the js output itself support the options, without any need to manipulate any files at all. Why would you not want to use goog defines? https://nam04.safelinks.protection.outlook.com/?url=https

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

I think the issue is that ApproveRoyale.xml isn't set up to generate the swf swcs, but there must be some configuration that causes Binding to look for the swf swc. I want to finish up getting the js-only build to work. I'll get to this eventually, but other volunteers are welcome to beat me t

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

Alex, the idea was to make the js output itself support the options, without any need to manipulate any files at all. Why would you not want to use goog defines? https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler#define-type-description It seems like the

Build failed in Jenkins: royale-asjs_MXTests #1164

See Changes: [joshtynjala] RoyaleUnit: tests for BeforeClass and AfterClass scope [joshtynjala] RoyaleUnit: started implementing MetadataRunner architecture change to ---

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

See

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

I probably won't object to folks trying out different config options, but the 3 buckets Harbs proposed didn't make any sense to me. I would want to turn them all on, and not be sure what the trade-offs are. IMO, modifying the JS from SWCs after compilation is "easy" in the sense that it is all

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

I think it could be as simple as having something like a class (eg. JSBuild) with a bunch of static goog @defines. These could be used to delimit sections of output that provide things like reflection, default initialized, vector runtime checking etc. In a sense it is not much different to how you

Re: Release vote/discuss reply-to address

Hi Josh, yes, Piotr and I talk a bit about gmail doing strange things. I finally could send messages to DISCUSS and to VOTE thread. But maybe the problem is the configuration done in the process. Maybe is just a matter of make a send to dev list and separate the two sendings, and remove that " apa

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

Maven with -X: https://paste.apache.org/ffq08 -- Josh Tynjala Bowler Hat LLC On Wed, Sep 18, 2019 at 8:44 AM Piotr Zarzycki wrote: > Thanks Josh. In logs there isn't any url from which you are downloading > artifacts. It means probably you are using cached one. One opt

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

Thanks Josh. In logs there isn't any url from which you are downloading artifacts. It means probably you are using cached one. One option is to remove cached artifacts and run build, the second is run build with -X. It doesn't have to be full build - it's the matter of see what actually maven do.

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/18/19 9:06 -0800" -Dplayerglobal.version=11.7 -Dflat.donot.ask=true -Drc=2 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Valid

Release Step 012 Succeeded

Folder 0.9.6 already exists. Continue to next step

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

Here's the console output from the Maven section of the build: https://paste.apache.org/cczye -- Josh Tynjala Bowler Hat LLC On Tue, Sep 17, 2019 at 10:20 PM Alex Harui wrote: > I assume that wasn't the whole log. I think we want to see the part where > it builds Core

Re: Discuss of release steps preparation

Because it means it is possible that the wrong version got into build.properties. -Alex On 9/17/19, 11:20 AM, "Piotr Zarzycki" wrote: 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

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

Hi Josh, The question is how Maven know if won't setup in settings link to staging to use proper version of compiler and sdk. How Maven taking from staging artefacts if you won't tell to him? I have tried build sources using in settings [1] - I didn't try without it. [1] https://paste.apache.org

Re: [royale-asjs] branch release/0.9.6 updated: Fix releasessteps script

Changing releaseversion to release.version should not be necessary and might break something else. Can you reproduce the failure? What is the console log? How did it not pick up the releaseversion from build.properties? -Alex On 9/17/19, 10:53 PM, "pio...@apache.org" wrote: This is an

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

Absolutely. Now we just need to figure out how… ;-) > On Sep 18, 2019, at 5:10 PM, Josh Tynjala wrote: > >> I think the main thing we are missing (from my perspective) is to avoid > the need to recompile the swcs to swap things in and out. > > I think that being able to switch things off and on

Re: [DISCUSS] Release Apache Royale 0.9.6 RC1

I don't know enough about Maven to answer your question, Piotr. All I can say is that I have successfully run the ApproveRoyale script for previous releases, and I don't think that I have changed any kind of global Maven settings on this machine since then. I can run it again and share the entire

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

> I think the main thing we are missing (from my perspective) is to avoid the need to recompile the swcs to swap things in and out. I think that being able to switch things off and on without recompiling SWCs would be awesome. Without that control, we will continue to struggle with differing opini

Build failed in Jenkins: royale-asjs_jsonly #3559

See -- [...truncated 274.64 KB...] [echo] ROYALE_COMPILER_HOME is C:\Program Files (x86)\Jenkins\workspace\royale-compiler\compiler check-dependency:

Release Step 011 Succeeded

>From the royale-asjs repo: 1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.6 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant -f r

Release Step 010 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands: git push git push origin org.apache.royale.framework-0.9.6-rc2 You will need your Apache/Github username and 2FA token.

Release Step 009 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_009 and run the following commands: git push You will need your Apache/Github username and 2FA token.

Release Step 008 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands: git push git checkout release/0.9.6 git push -u origin release/0.9.6 You will need your Apache/Github username and 2FA token.

Release Step 007 Succeeded

>From the royale-typedefs repo: 1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.6 -DskipTests=true This will download the artifacts then unzip and compile the source artifact. 2. Validate that the compiled artifacts match the downloaded artifacts. 3. If they do, then run ant

Release Step 006 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands: git push git push origin org.apache.royale.typedefs-0.9.6-rc2 You will need your Apache/Github username and 2FA token.

Release Step 005 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_005 and run the following commands: git push You will need your Apache/Github username and 2FA token.

Release Step 004 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands: git push git checkout release/0.9.6 git push -u origin release/0.9.6 You will need your Apache/Github username and 2FA token.

Release Step 003 Succeeded

>From the royale-compiler repo: 1. If you are releasing the utils jars (compiler-jburg-types and compiler-build-tools) - you have set in previous step for mentioned projects version ex. 1.1.0 not snapshot, Run: ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6 -Dski

Release Step 002a Succeeded

Continue on to Release Step 003

Release Step 002 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.6-rc2 You will need your Apache/Github username and 2FA token.

Royale_Release_Step_002 - Build # 43 - Failure!

Royale_Release_Step_002 - Build # 43 - Failure: Check console output at http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/43/ to view the results.

Release Step 001a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001a_If_Utils and run the following commands: git push You will need your Apache/Github username and 2FA token.

Release Step 003 Succeeded

>From the royale-compiler repo: 1. If you are releasing the utils jars (compiler-jburg-types and compiler-build-tools) - you have set in previous step for mentioned projects version ex. 1.1.0 not snapshot, Run: ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6 -Dski

Release Step 002a Succeeded

Continue on to Release Step 003

Release Step 002 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands: git push git push origin org.apache.royale.compiler-0.9.6-rc2 You will need your Apache/Github username and 2FA token.

Release Step 001a Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001a_If_Utils and run the following commands: git push You will need your Apache/Github username and 2FA token.

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

I agree 100% Harbs. And I think that is not difficult to achieve. The decisions and collaborative effort need to take place in the planning side of things to figure out the reasonable set of granular things to support. Perhaps we can do that once the 'dust has settled' after 0.9.6 is out. Then you