Build failed in Jenkins: royale-asjs #1430

See -- [...truncated 2.33 MB...] [mxmlc] org.apache.royale.states.AddItems depends on org.apache.royale.core.IDocument [mxmlc] Dependencies calculated

Build failed in Jenkins: royale-asjs_MXTests #19

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

Build failed in Jenkins: royale-asjs_MXTests #18

ale-asjs_MXTests/ws/js/lib/google/closure-library> subset-goog: [echo] Subsetting <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/js/lib/google/closure-library> main: [echo] Use thirdparty-clean or super-clean to remove these. crea

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

On Wed, Oct 3, 2018 at 2:02 PM Alex Harui wrote: > Hi Om, > > Does anything deploy, or is that the first thing that is attempted to > deploy? I found this article that might help: > > https://community.apigee.com/questions/50756/unable-to-deploy-using-maven-script-due-to-error-r.html It

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

Hi Om, Does anything deploy, or is that the first thing that is attempted to deploy? I found this article that might help: https://community.apigee.com/questions/50756/unable-to-deploy-using-maven-script-due-to-error-r.html I would be concerned about restarting from the middle of a Maven call.

Build failed in Jenkins: royale-asjs_MXTests #17

> subset-goog: [echo] Subsetting <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/js/lib/google/closure-library> main: [echo] Use thirdparty-clean or super-clean to remove these. create-description: [echo] build.number is 20181003 js-output-ro

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

It would be hard to make this happen. I think all artefacts are spread across target folders and local caches. When artefacts is build I'm not sure from where Maven is taking it - Cache or Targets folder. You are almost done with that. If you won't succeed till Monday maybe I will try to find

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

Another suggestion I have is - can we do all the pushes to remote after everything is done locally? That way, if something goes wrong halfway, we can just delete the royale-* dirs locally and rerun the releasecandiate ant script? Not sure if this is an easy change? Thanks, Om On Wed, Oct 3,

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

Okay, I tried a couple of times and I have started getting `SSL peer shut down incorrectly errors` [exec] [INFO] [INFO] [exec] [INFO] [INFO] BUILD FAILURE [exec] [INFO] [INFO]

Re: [royale-asjs] annotated tag org.apache.royale.framework-0.9.4-rc1 updated (29713a0 -> 25c496e)

I'll do it's clear source tree is doing something under the hood and it's clearly a bug thanks El mié., 3 oct. 2018 a las 17:37, Alex Harui () escribió: > Carlos, > > I would recommend that you contact SourceTree and find out what you can do > to prevent this. > > -Alex > > On 10/3/18, 3:47 AM,

Build failed in Jenkins: royale-asjs_MXTests #16

nto <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/js/lib/google/closure-library> subset-goog: [echo] Subsetting <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/js/lib/google/closure-library> main: [echo] Use

Re: [royale-asjs] annotated tag org.apache.royale.framework-0.9.4-rc1 updated (29713a0 -> 25c496e)

Carlos, I would recommend that you contact SourceTree and find out what you can do to prevent this. -Alex On 10/3/18, 3:47 AM, "carlosrov...@apache.org" wrote: This is an automated email from the ASF dual-hosted git repository. carlosrovira pushed a change to annotated tag

Re: Migrating Enterprise Flex Application

Hi, Royale doesn't currently support resource bundles. It is on my list of things to investigate to see how hard it will be to support it. The main challenge is that resource bundles are pre-compiled ABC code and we really want the raw strings. Royale does have a different, lightweight

Build failed in Jenkins: royale-asjs_MXTests #15

ale-asjs_MXTests/ws/in/google-closure-library-master.zip> into <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/js/lib/google/closure-library> subset-goog: [echo] Subsetting <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/js/lib/g

Build failed in Jenkins: royale-asjs_MXTests #14

echo] Subsetting <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/js/lib/google/closure-library> main: [echo] Use thirdparty-clean or super-clean to remove these. create-description: [echo] build.number is 20181003 js-output-royale-description: sw

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

See

Re: NextGenAS tutorials on Royale website

I agree that it would be great to make it easier to use Node. There are some sticking points currently. To answer your points: 1. Yes. It’s kind of similar in that it declares dependencies and optionally build tasks. Although there’s not necessarily a build step at all in Node.js. It’s worth

RE: [royale-asjs] 01/01: Merge pull request #309 from pashminakazi/branch21

Sorry I will be more careful while merging a Pull Request. -Alina -Original Message- From: Alex Harui [mailto:aha...@adobe.com.INVALID] Sent: Wednesday, October 03, 2018 12:49 PM To: dev@royale.apache.org; comm...@royale.apache.org Subject: Re: [royale-asjs] 01/01: Merge pull request

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

See

Re: NextGenAS tutorials on Royale website

Ok! publishing! :) While I publish I want to do share some thoughts I had today with friends that use Node. They say that we need to make it as easy as possible to work with Node since today is what front end devs use. So it's a must for us to succeed in the current JS world. So tow things: 1.-

Re: Migrating Enterprise Flex Application

Without seeing your source, I’d guess the problem is related to the locale you are feeding into the compiler. > On Oct 3, 2018, at 11:47 AM, chembali wrote: > > I am trying to compile a simple mxml file to js using mxmlc. Here is the mxml > fie. > > >

Re: Migrating Enterprise Flex Application

I am trying to compile a simple mxml file to js using mxmlc. Here is the mxml fie. http://ns.adobe.com/mxml/2009; xmlns:ss="com.infogix.iitap.component.scheduler.view.*"

Re: NextGenAS tutorials on Royale website

I’m done. I think it’s good to go. Harbs > On Oct 3, 2018, at 11:37 AM, Harbs wrote: > > I’m making a few small changes/corrections. I’ll be done in a few minutes. > >> On Oct 3, 2018, at 11:24 AM, Carlos Rovira wrote: >> >> Hi, I think a catch with all revisions. Please let me know if it's

Re: NextGenAS tutorials on Royale website

I’m making a few small changes/corrections. I’ll be done in a few minutes. > On Oct 3, 2018, at 11:24 AM, Carlos Rovira wrote: > > Hi, I think a catch with all revisions. Please let me know if it's ok to go: > >

Re: NextGenAS tutorials on Royale website

Hi Andrew, you're right, but since we are republishing Josh content, I think it should not be good to add content from other people (maybe you or I) that he originally didn't write. Maybe is not clear, but we should left as Josh did. In the other hand, Node is nowadays a standard in the industry

Re: NextGenAS tutorials on Royale website

Hi, I think a catch with all revisions. Please let me know if it's ok to go: https://royale.codeoscopic.com/hello-node-how-to-transpile-actionscript-for-node-js/ about Royale 0.8 to 0.9.4 change, I 'm not sure is what we want, since the node support was from 0.8 and we still didn't release

Build failed in Jenkins: royale-asjs_jsonly #1671

See Changes: [noreply] Update ButtonBase.as [om] [maven-release-plugin] prepare branch release/0.9.4 [om] [maven-release-plugin] prepare for next development iteration [om]

Re: [royale-compiler] 01/03: fix bracket access of XML/XMLList

OK. I added some test cases for XMLList indexed access and assignment. One of those tests passed before your change and is now failing. I think this is a summary of the cases we need to deal with (and we probably need more test cases…) Given: var xml:XML = var baz:XMLList = foo.baz; baz =

Re: [royale-asjs] 01/01: Merge pull request #309 from pashminakazi/branch21

Alina and Pashmina, Please make sure your code compiles before committing. -Alex On 10/2/18, 10:28 PM, "alinak...@apache.org" wrote: This is an automated email from the ASF dual-hosted git repository. alinakazi pushed a commit to branch develop in repository

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

Looks like it was a missing [ MXRoyale and SparkRoyale built for me. HTH, -Alex On 10/3/18, 12:43 AM, "OmPrakash Muppirala" wrote: Thanks! I reverted everything back to previous state. I can give it a shot tomorrow evening. Regards, Om On Wed, Oct 3,

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

Thanks! I reverted everything back to previous state. I can give it a shot tomorrow evening. Regards, Om On Wed, Oct 3, 2018 at 12:41 AM Alex Harui wrote: > It was in a releasable state. TourDeFlex was running on it. > > I'm trying to track down the change that broke it. > > -Alex > > On

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

It was in a releasable state. TourDeFlex was running on it. I'm trying to track down the change that broke it. -Alex On 10/3/18, 12:32 AM, "OmPrakash Muppirala" wrote: A bit more progress. Now we are failing on the MXRoyale project: [exec] [INFO] [INFO]

Build failed in Jenkins: royale-asjs #1423

See Changes: [noreply] Update SkinnableContainer.as [noreply] Update SkinnableTextBase.as [noreply] Update DividedBox.as [noreply] Update ButtonBase.as [om] [maven-release-plugin]

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

A bit more progress. Now we are failing on the MXRoyale project: [exec] [INFO] [INFO] [exec] [INFO] [INFO] BUILD FAILURE [exec] [INFO] [INFO]

Re: NextGenAS tutorials on Royale website

Agree. Remove the section about “This tutorial was made possible”, and link to Josh’s site in the top box. > On Oct 3, 2018, at 2:24 AM, Alex Harui wrote: > > Personally, I don't have a problem, but I think Apache doesn't like anything > that implies that Apache pays for code. > IMO, the

Build failed in Jenkins: royale-asjs_jsonly #1670

See Changes: [noreply] Update SkinnableContainer.as [noreply] Update SkinnableTextBase.as [noreply] Update DividedBox.as -- [...truncated