Build failed in Jenkins: royale-asjs_MXTests #2

See Changes: [aharui] try to only fix up royale-config once. If more than once then it [aharui] another try to only fix up royale-config once. If more than once then [aharui]

Jenkins build is back to normal : Verify_Royale_Config #12

See

Build failed in Jenkins: Verify_Royale_Config #11

See Changes: -- Started by user Apache Royale Running as SYSTEM Building remotely on agent1 in workspace

Build failed in Jenkins: Verify_Royale_Config #10

See Changes: -- Started by user Apache Royale Running as SYSTEM Building remotely on agent1 in workspace

Build failed in Jenkins: Verify_Royale_Config #8

See Changes: -- Started by user Apache Royale Running as SYSTEM Building remotely on agent1 in workspace

Build failed in Jenkins: Royale_ASDoc_Example #2

See Changes: [aharui] try to only fix up royale-config once. If more than once then it [aharui] another try to only fix up royale-config once. If more than once then

Build failed in Jenkins: Verify_Royale_Config #7

See Changes: [aharui] another try to only fix up royale-config once. If more than once then -- Started by upstream project "royale-asjs"

Build failed in Jenkins: Verify_Royale_Config #6

See Changes: [aharui] try to only fix up royale-config once. If more than once then it -- Started by upstream project "royale-asjs" build

Build failed in Jenkins: royale-asjs_MXTests #1

See Changes: -- [...truncated 1.02 MB...] [mxmlc] scanning for overrides: SolidColor [mxmlc] scanning for overrides: IExternalizable [mxmlc]

Build failed in Jenkins: Royale_ASDoc_Example #1

See Changes: -- [...truncated 33.51 KB...] [mxmlc] scanning for overrides: IListPresentationModel [mxmlc] scanning for overrides: IState

Build failed in Jenkins: Verify_Royale_Config #5

See Changes: -- Started by upstream project "royale-asjs" build number 15 originally caused by: Started by upstream project "royale-asjs_jsonly" build

Build failed in Jenkins: Verify_Royale_Config #4

See Changes: [yishayjobs] ListItemRenderer needs to be a UIComponent. [yishayjobs] Use spark layout for UIComponents. [yishayjobs] Let SparkRoyale enjoy VSCode features too

Build failed in Jenkins: Verify_Royale_Config #3

See Changes: -- Started by user Apache Royale Running as SYSTEM Building remotely on agent1 in workspace

Build failed in Jenkins: Verify_Royale_Config #2

See Changes: -- Started by user Apache Royale Running as SYSTEM Building remotely on agent1 in workspace

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

Hi Guys, I would share my experience and feelings as a new and fresh user on Apache Royale, hope it will help... The background : I'm a Flex developper since about 10 years. I love it because for me it's (was...for flashplayer) the fastest way to do something that would have same render on

Build failed in Jenkins: Verify_Royale_Config #1

See Changes: -- Started by user Apache Royale Running as SYSTEM Building remotely on agent1 in workspace

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

See

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

See

Re: CI emails

The CI server cannot currently send to commits@. If you can figure out how to get it to work, then it would be an option. But also in the Flex project, several committers did not subscribe to commits@ because they were not interested in the email traffic there. Thanks, -Alex On 10/10/19,

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

I know this isn't the last post on the thread, and I echo the sentiment of others that we want to know what problems folks are running into getting started with Royale. Meanwhile, back to the technical issue. Josh is mostly right. I don't think folks test the nightly -js package from the

Nightly Build Server going offline

Ok I will, but first they need to be accessible outside ;) Not only for commiters. On Thu, Oct 10, 2019, 2:35 PM Carlos Rovira wrote: > Hi, > > I don't know if finally is better to change links on website. If so, > please, let me know what links I must substitute and the new links to avoid >

Re: Nightly Build Server going offline

Hi, I don't know if finally is better to change links on website. If so, please, let me know what links I must substitute and the new links to avoid confusion. Thanks El jue., 10 oct. 2019 a las 10:12, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > How can we expose Nightly build

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

Hi Richard (and others in the same wagon), I only can say one thing: If you're a former Flex user, I encourage you to not give up and try to get your path with Royale. I think it can be difficult to start, but at this point (6 months after your latest try). I think is worth it and we are in good

Build failed in Jenkins: royale-asjs_jsonly #10

See Changes: -- [...truncated 1.15 MB...] [java] Oct 10, 2019 12:21:57 PM com.google.javascript.jscomp.LoggerErrorManager println [java]

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

Hi, yes, I already did some days ago an uploaded to website If you search for some new class (like jewel SimpleButton) it appears now. El jue., 10 oct. 2019 a las 11:49, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Hi Carlos, > > Did you make an update API doc ? -> >

Re: CI emails

Hi Alex, if Commiters need are the target, maybe better to use the list for that comm...@royale.apache.org thoughts? El mié., 9 oct. 2019 a las 19:50, Alex Harui () escribió: > IOM, we need the committers to see these in order to fix broken builds. > You might be better off filtering out

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

Hi Carlos, Did you make an update API doc ? -> https://royale.apache.org/asdoc/index.html Thanks, Piotr pon., 7 paź 2019 o 19:38 Carlos Rovira napisał(a): > Hi Piotr, > yes, I'll do in next few hours. > thanks. > > El lun., 7 oct. 2019 a las 9:54, Piotr Zarzycki (< >

Re: Nightly Build Server going offline

How can we expose Nightly build from new server outside ? Now if I would like to send links it requires from me login. śr., 9 paź 2019 o 20:08 Alex Harui napisał(a): > OK, I will switch the service to use the ApacheRoyaleCI account and see > what happens. > > -ALex > > On 10/9/19, 9:12 AM,

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

Hearing from new users what the roadblocks are, is very useful. To me, Royale feels very plug and play, but I know it well. It’s hard to see the roadblocks to new users when you have been involved for a long time. Thinking back to the days I was learning Flex, I think it was easy to learn it

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

Hi Piotr Last time would be a good 6 months ago. I didn’t ask for help but I know you all would  have been very helpful if I had - I see you doing so week in week out. We are using Angular for new work but still have a number of existing apps we need to port over,  re - write or convert to air