Re: About Releasing 0.9.7

The original problem went away in 1.12.1, but running a release from a pom in a subfolder like compiler-build-tools exposed a different bug. It is being tracked as https://issues.apache.org/jira/browse/SCM-932 I even supplied a test case this time. I am hopeful they will accept it. I underst

Re: Ask for help for flex migration, question

Hi Eduardo, Sounds like you are migrating some really old Flex code. Every place where there is mx:Script will have to be changed to be fx:Script. HTH, -Alex On 4/8/20, 9:36 AM, "Eduardo Oficialdegui" wrote: Hi, Im trying to use mxmlcnpm compiler to convert an .mxlm template to

Re: Royale Releases

Hi Carlos, I'm still back on getting compiler-build-tools 1.2.0 released. What was posted on dist for compiler-build-tools was not complete, and I am trying to get the CI server to do it using JGit because that is more secure, but had to fix a JGit bug first. I hope the first 7 steps of the a

Re: Using SNAPSHOTS and self patched code (was Re: [royale-asjs.wiki] branch master updated: Updated CI Server Setup (markdown))

In accordance with Maven's release philosophy, Royale code will not have any snapshot versions on the staging or release repos nor will the jars and swcs depend on snapshot versions. The CI profile will use a snapshot version of JGit unless Maven decides to release it before we get our release

Build failed in Jenkins: royale-typedefs #512

See Changes: -- Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on agent1 in workspace

Build failed in Jenkins: royale-asjs_jsonly #1235

See Changes: -- [...truncated 120.32 KB...] clean-tests: [echo] swc-date is 04/10/20 02:40 + [delete] Deleting:

Build failed in Jenkins: royale-asjs_jsonly #1234

output> [echo] compiler.source-path = <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/projects/*/src/main/royale> clean: super-clean: [delete] Deleting directory <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/roy

Re: Royale compiler remove labels and/or icons randomly

Many thanks Brian I think that information is very helpful. Maybe Greg or Josh could take a look since they now bindings and compiler much better and can have a clue that what could be happening. Thanks! :) El jue., 9 abr. 2020 a las 22:33, Brian Raymes () escribió: > Hi Carlos, > > I've notic

RE: Royale compiler remove labels and/or icons randomly

Hi Carlos, I've noticed this as well from time to time. This last time, I made a copy of the target build folder to compare with a subsequent build (using Beyond Compare). It appears that some bindings are missing in a "bad" build. Here is example related to TourDeJewel: In NavigationGroupExam

Build failed in Jenkins: royale-asjs_jsonly #1233

ure.com:8080/job/royale-asjs_jsonly/ws/frameworks/spark-manifest.xml> [delete] Deleting: <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/ide/flashbuilder/flashbuilder-config.xml> create-description: [echo] build.number is 20200409 js-output-royale-de

Re: [royale-asjs] branch develop updated: Add conditonalBind.

Without digging deeper, my first impression is that this isn't complete. Doesn't Language.closure() add a third param so two calls return the same binding? I think that should happen here too. -Alex On 4/9/20, 2:37 AM, "yish...@apache.org" wrote: This is an automated email from the ASF

Build failed in Jenkins: royale-compiler #329

See Changes: -- Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on agent1 in workspace

Using SNAPSHOTS and self patched code (was Re: [royale-asjs.wiki] branch master updated: Updated CI Server Setup (markdown))

Hi Alex, using SNAPSHOTS of external software with self-patched code is something that is not the right way to go for any project and we shouldn't allow in Apache Royale too. Not releasing with snapshot dependencies is something that's in Maven official documentation [1] as something we must hono

Re: Royale Releases

Hi Alex, don't understand the problem. Chris and I was able to reach step 7. The big problem is there with compiler generating classes with lines in different orders depending on OS (and probably JDK vendor). I think solving that will make you move from the problematic point. But don't understand

Re: Royale Releases

Hi Yishay, if you both think that can be done, it's ok for me. I was proposing changing order since I know I can have a release in few time and what delays me more is the voting waiting times, so it make sense to do something we already have and in parallel work in something that still requires w

Re: Royale Releases

FWIW, I saw Royale_Compiler_Build_Tools_Release_Step_002 work. I'm done for tonight. If anyone is bored, they can try to get the Royale_Compiler_Build_Tools_Release_Step_002_Sign target to work in compiler-build-tools/releasesteps.xml by renaming Royale_Compiler_Build_Tools_Release_Step_003_S