Does Oracle's new 2019 Java licensing affects Royale?

Hi, like many other companies, we have to deal here with Oracles new Java strategy [1]. I am not familiar with Java and it seems to me that there is a lot of confusion about the future of Java out there. (For those which are interesting in this topic, this is a good summary [2]) However, I wonder

Jenkins build is back to normal : TourDeFlexMigration #532

See

Build failed in Jenkins: royale-asjs_MXTests #514

See Changes: [carlosrovira] fix a regression in jewel item render that removes other content when -- [...truncated 2.02 MB...] [mxmlc] u

Jenkins build is back to normal : royale-asjs_MXTests #515

See

Re: Does Oracle's new 2019 Java licensing affects Royale?

Hi Olaf, before comment anything, I must say that I didn't read the new license, but IICRC the changes was for new Java 11 version Anyway, Royale is using Java 8, and our code can be compiled with either, Oracle Java, or OpenJDK. So, that means for me, that if Oracle could make some change in lic

Re: Problems dealing with bead substitution in Royale

Hi Harbs El mar., 19 feb. 2019 a las 18:30, Harbs () escribió: > > > Yes. Basically, you can ask any bead for a list of its interests, and that > list is used to both add and remove bead references in the strand. The bead > does not need to clean itself. A ututiliy method can completely strip a >

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

See

Migrating an app from Apache Flex to Apache Royale (tweet thread)

Hi, just want to share our recent experience migrating an Apache Flex application to Apache Royale. So I post a thread of 17 tweets here: https://twitter.com/carlosrovira/status/1098333642751950848 Hope the info will be useful :) Enjoy and don't forget to share if that was useful for you! :) -

Re: Breaking Compiler Change

It exists to make Flex uses compatible with Royale when the type could not be determined. It’s possible that the new coercions might make it no longer necessary, but this whole thread started because the XML split method was still being called, so I’m not sure that we’re there yet… > On Feb 20

Re: [royale-compiler] 05/05: ParametersEmitter: fixed automatic type coercion and added some tests (closes #74)

My latest improvements to the compiler should resolve these 5 issues with coercion. - Josh On 2019/02/19 16:03:05, Josh Tynjala wrote: > 1. b.moveTo(Number(path.pathPoints[0].anchor.x), > Number(path.pathPoints[0].anchor.y)); > > I have determined that the compiler is not correctly resolving

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

See

Build failed in Jenkins: royale-asjs_MXTests #519

See -- [...truncated 2.02 MB...] [mxmlc] using source file:

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

See

Heads-up on coming updates to reflection and AMF

Just a fyi about what I am working on I am currently working on AMFBinaryData updates to support: IExternalizable dynamic class instances I expect to also support IDynamicPropertyWriter And refactoring the AMFBinaryData class to be a subclass of BinaryData (this part is done) and have an api

Jenkins build is back to normal : royale-asjs_MXTests #520

See

Re: [royale-compiler] 05/05: ParametersEmitter: fixed automatic type coercion and added some tests (closes #74)

SWF output might do more error checking and coercion than JS output, so if you were having trouble figuring out what to change for Vector, I was suggesting that you look in some of that code. Sounds like you got it working? Then my email doesn’t matter. -Alex On 2/19/19, 8:53 AM, "Josh Tynj

Re: Problems dealing with bead substitution in Royale

It looks like a reasonable subsystem design, but given that we have a lot of code running just fine without this, and that bead substitution should be a very rare situation, I'm having trouble understanding why we would want to add an entire just-in-case subsystem. Asking beads for their intere

Royale_Release_Step_001 - Build # 49 - Failure!

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

Release Step 001 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 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 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 You will need your Apache/Github username and 2FA token.