Build failed in Jenkins: royale-asjs_jsonly #3398

See -- [...truncated 1.72 MB...] [java] [java] public var scriptName:String; [java] ^ [java] [java]

Re: Discuss of release steps preparation

This console output is here [1], but it is version where script failing, cause there wasn't "../../". Let me know if it's enough actually. [1] https://paste.apache.org/zvxoi czw., 15 sie 2019 o 22:37 Alex Harui napisał(a): > That's a possibility. I only used absolute paths. > > Piotr, it would

Build failed in Jenkins: royale-asjs_jsonly #3397

See -- [...truncated 1.72 MB...] [java] [java] public var scriptName:String; [java] ^ [java] [java]

Build failed in Jenkins: royale-asjs_jsonly #3396

See -- [...truncated 1.72 MB...] [java] [java] public var scriptName:String; [java] ^ [java] [java]

File Handling (was Re: inject_html in the framework via rawgit)

Greg's email coincided with some other interesting file-handling issues that might be worth a discussion. The issue I ran into was that the old MX RichTextEditor has some icon buttons. In Flex, those buttons are embedded. We are not (yet) supporting embedding in Royale, so the question is how

Build failed in Jenkins: royale-asjs_jsonly #3395

See Changes: [aharui] well, if we're going to leverage explicitWidth/Height we also have to [aharui] try to get DG columns to behave better [aharui] need another pixel to keep labe

Re: Discuss of release steps preparation

Sorry, that should be plural -DskipTests=true -Alex On 8/15/19, 4:15 PM, "Alex Harui" wrote: Also, try adding -DskipTest=true to skip the mustella tests. On 8/15/19, 1:37 PM, "Alex Harui" wrote: That's a possibility. I only used absolute paths.

Re: Discuss of release steps preparation

Also, try adding -DskipTest=true to skip the mustella tests. On 8/15/19, 1:37 PM, "Alex Harui" wrote: That's a possibility. I only used absolute paths. Piotr, it would nice to see the Windows console output including the paths you gave to help make this process more robust.

Re: Discuss of release steps preparation

That's a possibility. I only used absolute paths. Piotr, it would nice to see the Windows console output including the paths you gave to help make this process more robust. -Alex On 8/15/19, 1:21 PM, "Josh Tynjala" wrote: If it started working correctly after changing the path to includ

Re: Discuss of release steps preparation

If it started working correctly after changing the path to include ../../, perhaps ${artifactfolder} is being set to a relative path, but the script expects the path to be absolute. I'm not familiar with the release steps yet, so I'm just guessing, but does that make sense? -- Josh Tynjala Bowler

Discuss of release steps preparation

Nope Maven didn't provide such feature or at least I didn't get any questions on console. I was today on a last step which takes lot's of time - build on machine whole framework by ant, but if failed on mustella tests. I will try tomorrow and see whether it happen again. If that very last step wil

Build failed in Jenkins: royale-asjs_jsonly #3394

See Changes: [yishayjobs] Fixes #445 [yishayjobs] bad comment [yishayjobs] Fixes #445 again -- [...truncated 1.72 MB...] [java]

Re: Discuss of release steps preparation

Good to know. When it failed on Windows, did Maven offer command-line options to continue from the point of failure? Unless all future RMs have Macs, we still need to find a way for Windows-only RMs to be successful. -Alex On 8/15/19, 5:12 AM, "Piotr Zarzycki" wrote: Good news. I tried

Build failed in Jenkins: royale-asjs_MXTests #1061

See -- [...truncated 897.25 KB...] [mxmlc] -compiler.library-path+=

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="08/15/19 01:53 -0800" -Dplayerglobal.version=11.7 -Dflat.donot.ask=true -Drc=1 This will download the artifacts then unzip and compile the source artifact. 2. Validate that the co

Re: Discuss of release steps preparation

If we would use for release process develop it would impossible for me finish that process. I'm volunteer - even if current tasks is being paid job. - It means that I could do first 5 steps first day and in couple of days another 2 steps. If there would be some commit between those days - I will ha

Re: Discuss of release steps preparation

Good news. I tried today again upload artifacts from my Windows machine - it failed again. I copied my signed artifacts to my Mac machine which is using different internet connection. I'm not sure how it influences all the process but I have uploaded artifacts without any problem. I'm moving forwar

Release Step 012 Succeeded

Folder 0.9.6 already exists. Continue to next step

Build failed in Jenkins: royale-asjs_MXTests #1060

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

Build failed in Jenkins: royale-asjs_MXTests #1059

See Changes: [aharui] handle left/right and top/bottom sizing -- [...truncated 984.24 KB...] [mxmlc] scanning for overrides: CustomEvent