issues with Sourcetree in Mac

Hi Carlos, It means that you cannot update links on the website? I'm using GitHub Desktop and yesterday everything was working fine. Thanks, Piotr On Mon, Oct 7, 2019, 11:34 PM Carlos Rovira wrote: > Hi, > > I'm having issues with source tree on Mac > this Saturday I tried to commit some

Release 0.9.6 Announce for web post?

Hey Andrew, Thank you! On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore wrote: > I looked over the draft announcement, Piotr, and it seems fine as to the > English. I cannot speak to the technical details as well as other > committers can. > > Andrew > > On Mon, Oct 7, 2019 at 5:01 PM Piotr

Build failed in Jenkins: royale-asjs_MXTests #1222

See -- [...truncated 1.01 MB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning

Build failed in Jenkins: royale-asjs_MXTests #1221

See Changes: [piotrzarzycki21] [maven-release-plugin] prepare branch release/0.9.6 [piotrzarzycki21] update royale.compiler.version and royale.typedefs.version in pom

Jenkins build is back to normal : royale-asjs #2780

See

Build failed in Jenkins: royale-asjs #2779

See Changes: [noreply] Update GIT-TEST.txt [carlosrovira] Changes in main menu links for ASDocs -- [...truncated 1.61 MB...] [java] Picked up

issues with Sourcetree in Mac

Hi, I'm having issues with source tree on Mac this Saturday I tried to commit some changes and I was not able to do it. I can commit to local but not push to remote I thought that was some punctual problem, and since I had not much time, I decided to wait to next day. I'm trying today and still

Re: Release 0.9.6 Announce for web post?

I looked over the draft announcement, Piotr, and it seems fine as to the English. I cannot speak to the technical details as well as other committers can. Andrew On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki wrote: > Currently I'm waiting for review of Draft of announcement. Till maximum >

Release 0.9.6 Announce for web post?

Currently I'm waiting for review of Draft of announcement. Till maximum Wednesday. Than I will send announce to dev, users and announce mailing list. I think you should create draft and post it once announce will be sent. Apart of that I should add our release somewhere in the whimsy but I don't

Re: Release 0.9.6 Announce for web post?

That would be good On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, wrote: > Hi, > I'll be updating website in next few hours, but I was thinking we don't > have the habitual blog post for 0.9.6 release. > Should I create one from scratch based on 0.9.4? > > thanks > > -- > Carlos Rovira >

Release 0.9.6 Announce for web post?

Hi, I'll be updating website in next few hours, but I was thinking we don't have the habitual blog post for 0.9.6 release. Should I create one from scratch based on 0.9.4? thanks -- Carlos Rovira http://about.me/carlosrovira

Build failed in Jenkins: royale-asjs #2778

See Changes: [aharui] typedefs also has a build.properties now [aharui] need to update this in pom [aharui] fix a few version numbers that don't get updated because commented out

New apache-royale questions for Oct 7 - Stack Exchange

***1 new question in [ApacheRoyale Tag Notifications filter]() on stackexchange.com*** [How to use js:DataGrid on Apache Royale ? Issue with

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

See

Build failed in Jenkins: royale-asjs_jsonly #3655

re.com:8080/job/royale-asjs_jsonly/ws/> [echo] royalelib = <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks> [echo] doc_output = <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/asdoc-output> [echo

Re: ROYALE_REFLECTION_INFO.compileFlags

I’m using an older compiler. I’ll check when I update my compiler. Thanks. Harbs > On Oct 7, 2019, at 8:42 PM, Greg Dove wrote: > > Hi Harbs I actually noticed that recently prompted by something Alex had > mentioned in a thread somewhere. It should be fixed in a recent commit > during the

Re: ROYALE_REFLECTION_INFO.compileFlags

Hi Harbs I actually noticed that recently prompted by something Alex had mentioned in a thread somewhere. It should be fixed in a recent commit during the past week sometime, unless I missed something (it was working for Hello World). What build are you using? And are you using any features that

Build failed in Jenkins: royale-asjs_jsonly #3654

e.com:8080/job/royale-asjs_jsonly/ws/frameworks> [echo] doc_output = <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/asdoc-output> [echo] compiler.source-path = <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

Hi Piotr, yes, I'll do in next few hours. thanks. El lun., 7 oct. 2019 a las 9:54, Piotr Zarzycki () escribió: > Hi Carlos, > > Will you be able update website with links for 0.9.6 release ? > > Thanks, > Piotr > > niedz., 6 paź 2019 o 10:52 Piotr Zarzycki > napisał(a): > > > Hi Alex, > > > >

Re: Build failed in Jenkins: royale-asjs #2777

I'll check it today Piotr. On Tue, 8 Oct 2019, 01:50 Piotr Zarzycki, wrote: > RoyaleUnit tests are failing on XML module, can someone with some free > cycle look into this ? > > pon., 7 paź 2019 o 14:47 Apache Royale CI Server > > napisał(a): > > > See < > > >

Re: Nightly Build Server going offline

I think the merge happened, so I am going to try to do the rebuild this week, probably on my Tuesday if I can finish up some fixes to releasecandidate.xml needed for Windows today. -Alex On 10/7/19, 12:39 AM, "Carlos Rovira" wrote: Hi, don't think a day be a problem. When can

Re: Build failed in Jenkins: royale-asjs #2777

RoyaleUnit tests are failing on XML module, can someone with some free cycle look into this ? pon., 7 paź 2019 o 14:47 Apache Royale CI Server napisał(a): > See < > http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/2777/display/redirect > > > >

Build failed in Jenkins: royale-asjs #2777

See -- [...truncated 1.61 MB...] [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g compile-js: [echo] swc-date is 10/07/19

Build failed in Jenkins: royale-asjs_jsonly #3653

re.com:8080/job/royale-asjs_jsonly/ws/> [echo] royalelib = <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks> [echo] doc_output = <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/asdoc-output> [echo

Build failed in Jenkins: royale-asjs #2776

See Changes: [piotrzarzycki21] [maven-release-plugin] prepare branch release/0.9.6 [piotrzarzycki21] update royale.compiler.version and royale.typedefs.version in pom [piotrzarzycki21]

Build failed in Jenkins: royale-asjs_jsonly #3652

re.com:8080/job/royale-asjs_jsonly/ws/> [echo] royalelib = <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks> [echo] doc_output = <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/asdoc-output> [echo

ROYALE_REFLECTION_INFO.compileFlags

It seems to me like the size of my app has recently increased and I’m trying to understand why. I noticed that I have 1270 instances of ROYALE_REFLECTION_INFO.compileFlags in my app (and 1421 instances of ROYALE_REFLECTION_INFO) in my minified app. I don’t know what this does. Is this always

Build failed in Jenkins: royale-asjs_jsonly #3651

re.com:8080/job/royale-asjs_jsonly/ws/> [echo] royalelib = <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks> [echo] doc_output = <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/asdoc-output> [echo

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

Hi Carlos, Will you be able update website with links for 0.9.6 release ? Thanks, Piotr niedz., 6 paź 2019 o 10:52 Piotr Zarzycki napisał(a): > Hi Alex, > > Thank you for the fix. Everything worked fine this time. > > Piotr > > sob., 5 paź 2019 o 01:51 Alex Harui napisał(a): > >> I found

Re: Nightly Build Server going offline

Hi, don't think a day be a problem. When can better warn in social networks about that 24h unavailability. Other option is to store in pre web server (Royale.codeoscopic.com). You have credentials and can upload to Wordpress and then we can share that link. Whatever option could be fine, but for

Re: Branches and Commits and Cherry-Picking

HI Alex, right, I'm only saying that as part as the natural process, people should not need to ask for agreement, since what is in develop should not go to release. And if something need to be fixed in release it will happen there (of course promoted by some discussion about something is not