Build failed in Jenkins: royale-asjs_jsonly #3404

See -- [...truncated 1.72 MB...] [java] public static var noScriptComplete:Boolean = false; [java] ^ [java] [java]

Build failed in Jenkins: royale-asjs_jsonly #3403

See -- [...truncated 1.71 MB...] [java] public static var noScriptComplete:Boolean = false; [java] ^ [java] [java]

Build failed in Jenkins: royale-asjs_jsonly #3402

See Changes: [aharui] horizontalAlign in MX Container/Panel -- [...truncated 1.71 MB...] [java] public static var noScriptComplete:B

Re: Build failed in Jenkins: royale-asjs_jsonly #3398

In my experience locally that can break the build for some tests. I have had to uninstall firefox and reinstall version 47 many times on my own machine. There is a compatibility with (iirc) mustella testing that requires the older firefox version. So I would guess that is what is happening on the s

Build failed in Jenkins: royale-asjs_jsonly #3401

See Changes: [aharui] handle background with only a color specified. Fixes #449 -- [...truncated 1.71 MB...] [java] public static v

Re: Discuss of release steps preparation

Piotr, At this point, I would definitely recommend trying the three steps without any changes to the release_steps.xml file and use an ABSOLUTE path. That's the only way I tested the scripts. I did not try a relative path, and I highly recommend not putting all of these files in a working cop

Build failed in Jenkins: royale-asjs_jsonly #3399

See Changes: [carlosrovira] temporal fix for inject_html in @extern classes -- [...truncated 1.71 MB...] [java] public static var no

Re: Build failed in Jenkins: royale-asjs_jsonly #3398

I've seen on the server that Firefox was updated for some reason. Could it influence the build ? pt., 16 sie 2019 o 08:39 Apache Royale CI Server napisał(a): > See < > http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/3398/display/redirect > > > > -

Re: Discuss of release steps preparation

It looks like this is again problem with RoyaleUnit[1]. Here is the results of comparison. I'm not sure why left folder doesn't contains files. [1] https://pasteboard.co/IsWnHGq.png Thanks, Piotr pt., 16 sie 2019 o 11:08 Piotr Zarzycki napisał(a): > Ok I was mistake. Both zips exists, but they

Re: Discuss of release steps preparation

Ok I was mistake. Both zips exists, but they have different sizes! So comparison went fine and I need to understand one sources are different... pt., 16 sie 2019 o 10:59 Piotr Zarzycki napisał(a): > I have analyzed that target (compare-src-zips) and it compares zip file in > following locations:

Re: Discuss of release steps preparation

I have analyzed that target (compare-src-zips) and it compares zip file in following locations: 1) artifacts\apache-royale-0.9.6-src.zip 2) /sources/srczip/apache-royale-0.9.6-src.zip I have changed in that target all places where ${artifactfolder} to ../../${artifactfolder} and launch that targe

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

Hi Alex, I had to fight with assets for Jewel. I ended solving it in Maven. This approach could appear a bit cumbersome for our users since they need to think how to deal with it, and they could say us: "hey! I'm using a SDK...I should not need to spend time solving that, SDK should do it for me",

Re: Discuss of release steps preparation

Unfortunately I don't know what is happening but signing trough script hang for me. Stopped working. :( ant -f releasesteps.xml Release_Step_003_Sign -Drelease.version=0.9.6 Buildfile: d:\Work\royale-sources\royale-compiler\releasesteps.xml get-artifact-folder: [input] Enter the temporary fo

Build failed in Jenkins: royale-asjs #2601

See Changes: [yishayjobs] Fixes #445 [yishayjobs] bad comment [yishayjobs] Fixes #445 again [aharui] well, if we're going to leverage explicitWidth/Height we also have to [aharui] try t

Re: Discuss of release steps preparation

With "../../" or without ? I just run script with -DskiptTests="true" and it passes, but failed on "compare-src-zips" - It looks like it is also problem with paths. :( pt., 16 sie 2019 o 09:15 Alex Harui napisał(a): > I would also need to see the output of the other two steps > (Release_Step_003

Re: Discuss of release steps preparation

I would also need to see the output of the other two steps (Release_Step_003 and Release_Step_003_Sign) Thanks, -Alex On 8/15/19, 11:14 PM, "Piotr Zarzycki" wrote: This console output is here [1], but it is version where script failing, cause there wasn't "../../". Let me know if it's