Build failed in Jenkins: royale-asjs #33

See Changes: -- [...truncated 2.04 MB...] [java] ^ [java] [java]

Build failed in Jenkins: royale-asjs #32

See Changes: -- [...truncated 2.04 MB...] [java] public var lastEvent:Event; [java] ^ [java] [java]

Build failed in Jenkins: royale-asjs #31

See Changes: -- [...truncated 2.05 MB...] [java] ^ [java] [java]

Re: [royale-asjs] 01/06: RoyaleArrayLike support (IArrayList and BinaryData)

Thanks for bringing that to my attention, Josh. it should be fixed now (I tested with your example, thanks for that). On Tue, Oct 15, 2019 at 10:31 AM Greg Dove wrote: > > Hi Josh, thanks, I will look into that today. > > > On Tue, Oct 15, 2019 at 10:30 AM Josh Tynjala > wrote: > >> Hey Greg,

Re: [royale-asjs] 01/06: RoyaleArrayLike support (IArrayList and BinaryData)

Hi Josh, thanks, I will look into that today. On Tue, Oct 15, 2019 at 10:30 AM Josh Tynjala wrote: > Hey Greg, > > Starting with the commit, there are times when compilation gets stuck in > an infinite loop. It should be possible to reproduce using the following > code: > > for each(var

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

We've never tried a hotfix release version. Could be a lot of work to get it to work. Might be easier to just roll forward to 0.9.7. Volunteers are welcome to try. I won't be spending time on it. Regarding a "modified SDK", the issue is not a licensing issue, but a branding issue. We

Build failed in Jenkins: royale-asjs #30

See Changes: [piotrzarzycki21] Fix MX NumberFormatter to be usable in MX components -- [...truncated 2.04 MB...] [java] public var

Build failed in Jenkins: royale-asjs #29

See Changes: -- [...truncated 2.05 MB...] [java] public var lastEvent:Event; [java] ^ [java] [java]

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hi Piotr, about license: My common sense says that you can provide a modified SDK (since is an Open Source project) but you should state that *it is not* the official 0.9.6 SDK release, but a modified one provided by Moonshine to fix an issue. Maybe others could know and say more about this.

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Ok that's can be an idea - It may happen or not - We will see. Currently I'm interested really in an answer for the license question. pon., 14 paź 2019 o 12:34 Carlos Rovira napisał(a): > Hi Piotr, > > I think since is a hot fix it starts from 0.9.6 release branch and there > you apply the fix

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hi Piotr, I think since is a hot fix it starts from 0.9.6 release branch and there you apply the fix to generate a 0.9.6.1. Then when released the hot fix is merged in current develop branch with 0.9.7 Or at least is what I suppose it should be El lun., 14 oct. 2019 a las 12:15, Piotr

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hi Carlos, I was talking exactly about hot fix. However it seems to me a bit difficult, cause we have now in develop version 0.9.7 - I'm not really sure how maven react if I change it to 0.6.1 ;) Thanks, Piotr pon., 14 paź 2019 o 11:13 Carlos Rovira napisał(a): > Hi Piotr, > > other option is

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hi Piotr, other option is to release a hot fix version like 0.9.6.1 if you want to release in few days what do you think? El lun., 14 oct. 2019 a las 9:58, Piotr Zarzycki () escribió: > Hey Guys, > > I'm willing to try release very soon another version of Royale just with > fix for our issue

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hey Guys, I'm willing to try release very soon another version of Royale just with fix for our issue with broken royale config. If it won't happen next week I will probably do that next month which will be I think enough to have proper release not only with that fix. Anyway my question is a bit

Feedback after sending release annonce to announce mailing list

Hi Guys, I won't push this time that to announce, but when I send it there our announce I got below feedback. In the next release I will remove those links. Thanks, Piotr śr., 9 paź 2019 o 21:12 napisał(a): > > Hi! This is the ezmlm program. I'm managing the > annou...@apache.org mailing