Build failed in Jenkins: royale-asjs_MXTests #1058

See -- [...truncated 983.60 KB...] [mxmlc] scanning for overrides: CustomEvent [mxmlc] scanning for overrides: ItemAddedEvent [mxmlc] scanning

Build failed in Jenkins: royale-asjs_MXTests #1057

See -- [...truncated 982.97 KB...] [mxmlc] scanning for overrides: CustomEvent [mxmlc] scanning for overrides: ItemAddedEvent [mxmlc] scanning

inject_html in the framework via rawgit

"RawGit is now in a sunset phase and will soon shut down" [1] It just came to my attention today that some of the framework code uses script tag injections for rawgit urls, and I checked that service... it could be shut down as early as October 2019. This looks to only be used in MXRoyale and AceE

Build failed in Jenkins: royale-asjs_MXTests #1056

See Changes: [aharui] ensure end values if the update happens well after the duration expires [aharui] set the return type to Number because JS returns a number --

Re: Compiler Performance (was Re: Problem with Vectors)

Hi Greg, Well I definitely in the very last steps, but if I won't be able to figure out how to upload artifacts I'm not sure whether we will not stuck for the next couple of weeks. :( Thanks, Piotr On Wed, Aug 14, 2019, 9:50 PM Greg Dove wrote: > I should have drawn attention to this again bef

Re: Compiler Performance (was Re: Problem with Vectors)

I should have drawn attention to this again before release work started... I guess it is too late to get rid of that diagnostic output (described below) from the compiler in the release? It might be confusing output for some people, or create the wrong impression, but perhaps it is too late in the

Re: Discuss of release steps preparation

Carlos, In [1] that you referenced it says about release branches: "During that time, bug fixes may be applied in this branch (rather than on the develop branch)." To me, that means that new unstable changes should go into develop, but changes to make the release better should be discussed wit

Re: Discuss of release steps preparation

On 8/14/19, 1:14 AM, "Piotr Zarzycki" wrote: If your folder with artifacts is in ~/temp/releasesteps - What do you type when script asking you about ? I would type (on a Mac): /Users/aharui/temp/releasesteps There are 3 different Ant targets for Step 003: - Release_Step_003

Build failed in Jenkins: royale-asjs_MXTests #1055

See -- [...truncated 984.27 KB...] [mxmlc] scanning for overrides: CustomEvent [mxmlc] scanning for overrides: ItemAddedEvent [mxmlc] scanning

Re: Discuss of release steps preparation

Can you explain why that would be the right change? Doesn't make sense to me. On 8/14/19, 3:36 AM, "Piotr Zarzycki" wrote: So far so good. I did tweak the script and was able to upload artifacts. I have changed in each script: Line from: To The very last

Re: Discuss of release steps preparation

I think this may be something on the Nexus sight. When I had opened page [1] and at the same time I was trying to upload artifacts. It failed and on the webpage I got [2] [1] https://repository.apache.org/#stagingRepositories [2] https://pasteboard.co/IsFDChX.png śr., 14 sie 2019 o 15:33 Piotr

Build failed in Jenkins: royale-asjs_MXTests #1054

See Changes: [yishayjobs] Make sure controller has state selected state ready before any external -- [...truncated 984.27 KB...] [mxmlc

Re: Discuss of release steps preparation

I completely cannot right now upload artifacts to nexus. It's failing due to inability to upload artifacts always in different places. I can't believe that this is because of my internet connection. Actually I have two sources of my internet and on both it's failing. I will probably try repeat pro

Re: Discuss of release steps preparation

It looks like those items wasn't added to sign script. I will add them and fix script. śr., 14 sie 2019 o 12:35 Piotr Zarzycki napisał(a): > So far so good. I did tweak the script and was able to upload artifacts. I > have changed in each script: > Line from: > > > To > > > The very last thing

Re: Discuss of release steps preparation

So far so good. I did tweak the script and was able to upload artifacts. I have changed in each script: Line from: To The very last thing was close repository, so I got some errors you can check here by logging your Apache handle [1] related to RoyaleUnit [2]. Missing Signature: '/org/apache/r

Re: Discuss of release steps preparation

Hi Alex, El lun., 12 ago. 2019 a las 19:30, Alex Harui () escribió: > Also, the other committers should be aware that an RC is being created > because they see the emails being sent by the CI server and ask the RM to > agree to accept a commit to the release branch instead of the develop > branch

Build failed in Jenkins: royale-asjs_MXTests #1053

See Changes: [aharui] try using visibility instead of display=none so that offsetParent and [aharui] propagate systemManager property [aharui] handle measuredWidth without measuri

Re: Discuss of release steps preparation

I'm trying to understand part of the script which is responsible for upload it is for example in compiler: Release_Step_003_Upload My folder contains: - artifacts folder - sources folder Now you are launching command: "> po

Re: Discuss of release steps preparation

If your folder with artifacts is in ~/temp/releasesteps - What do you type when script asking you about ? get-artifact-folder: [input] Enter the temporary folder to store the downloaded artifacts: wt., 13 sie 2019 o 22:20 Alex Harui napisał(a): > I'm not sure you should skip the uploading.