Build failed in Jenkins: TourDeFlexMigration #535

See Changes: -- [...truncated 123.83 KB...] [mxmlc] Loading configuration: C:\jenkins\workspace\royale-asjs\frameworks\flex-config.xml [mxmlc]

Build failed in Jenkins: Royale_ASDoc_Example #536

See Changes: -- [...truncated 41.15 KB...] [java] ^ [java] [java]

Re: Generating Royale API report failing on Mac

Hi Takeshita, Sure I know. What I refer I do not understand is the way how it's connected to the problem. Anyway LFCR - is something which is ok on Windows, but not ok on Mac? I will try to download tar.gz on Mac and see if it works. On Thu, Jan 23, 2020, 7:23 AM Takeshita Shoichiro wrote: >

Re: Generating Royale API report failing on Mac

Piotr, zip and tar.gz are file types. On Mac, it is better to download file with tar.gz file type. Zip is for Windows. 2020年1月23日(木) 15:11 Piotr Zarzycki : > Hi Alex, > > Unfortunately I completely don't understand what do you mean. What zip or > tar.gz? Scenario is simple: > > 1) I'm

Re: Generating Royale API report failing on Mac

Hi Alex, Unfortunately I completely don't understand what do you mean. What zip or tar.gz? Scenario is simple: 1) I'm downloading Nightly build 2) Setup it in Moonshine 3) Trying to generate API report using Moonshine Files in SDK are broken. Screenshot which I have shown in previous email was

Build failed in Jenkins: TourDeFlexMigration #534

See Changes: [aharui] a few tweaks to allow LineNumberTextDisplay in #598 -- [...truncated 125.17 KB...] [mxmlc] Loading

Build failed in Jenkins: Royale_ASDoc_Example #535

See Changes: [aharui] a few tweaks to allow LineNumberTextDisplay in #598 -- [...truncated 42.49 KB...] [java]

Build failed in Jenkins: TourDeFlexMigration #533

See Changes: [aharui] emulate skinClass [carlosrovira] html-a: default anchor tag should not define href, sometimes we need [carlosrovira] jewel-renderers: remove href from

Build failed in Jenkins: Royale_ASDoc_Example #534

See Changes: [aharui] emulate skinClass [carlosrovira] html-a: default anchor tag should not define href, sometimes we need [carlosrovira] jewel-renderers: remove href from

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

See

Re: Generating Royale API report failing on Mac

IIRC, there is a step in the build process that is supposed to remove CRLF from certain files. Did you use the zip or tar.gz for Mac? It might be that if you use the zip on a Mac that the files may still have CRLF. You can check the build log and see if the CRLF removal tasks ran or not. I

Build failed in Jenkins: royale-asjs #610

See Changes: -- Started by upstream project "royale-asjs_jsonly" build number 670 originally caused by: Started by an SCM change Started by upstream project

Jenkins build is back to normal : royale-compiler-integration-tests #457

See

Build failed in Jenkins: TourDeFlexMigration #532

See Changes: [carlosrovira] maven-distribution: remove closure library jars from js/lib since we [carlosrovira] jewel-navigation: remove href since is not used anymore and

Re: Generating Royale API report failing on Mac

Alex, Carlos, I have checked mxmlc file in repository and it has LF lines only which is ok. However when I have downloaded build version of SDK [1] - that file and others has CR LF [2] - which causes all problems on Mac. Maybe this is problem with our build machine where after checkout something

Build failed in Jenkins: Royale_ASDoc_Example #533

See Changes: [carlosrovira] maven-distribution: remove closure library jars from js/lib since we [carlosrovira] jewel-navigation: remove href since is not used anymore and

Re: InvalidPathException: Illegal char (was: Building Royale project with Maven throws NPE)

Is the URL for Notifier.as valid? Do you have an older project around that you can compare the source mapping URLs? Looks like Google is complaining about the source map URL. -Alex On 1/22/20, 9:01 AM, "Piotr Zarzycki" wrote: It looks like I have two separate issues - apart of behavior

Re: Apache PMCs: your chance to support your projects with Outreachy internships

I personally don’t have the bandwidth (although I can answer questions here and there). > On Jan 22, 2020, at 5:34 PM, Andrew Wetmore wrote: > > Hi: > > Are we organized enough, and do we have enough bandwidth, do get some > documentation help through this program? Mentoring can take an

Build failed in Jenkins: royale-compiler-integration-tests #456

See Changes: [carlosrovira] maven: fix compilation from maven since latest changes break it [carlosrovira] maven: more closure library places were left in the latest

Re: Generating Royale API report failing on Mac

Hi, this could be something to do with changes done by me? if so I'm on Mac not Windows El mié., 22 ene. 2020 a las 17:11, Alex Harui () escribió: > > > On 1/22/20, 4:57 AM, "Piotr Zarzycki" wrote: > > Hi, > > This is the day of failing. > > I've definitely had days like this... > >

Re: Maven Distribution SDK fixed and working for IDEs

Hi Piotr, it surprise me that due all the changes done in maven builds.a.o was not failing. I've even didn't repare that will need to be updated. These profiles does not exist anymore: generate-swf,generate-swcs-for-swf,main,build-distribution,build-examples Here's the updated doc for maven

Build failed in Jenkins: TourDeFlexMigration #531

See Changes: [carlosrovira] maven: replace closure library in the rest of places -- [...truncated 125.16 KB...] [mxmlc] Loading

InvalidPathException: Illegal char (was: Building Royale project with Maven throws NPE)

It looks like I have two separate issues - apart of behavior when I'm building application by Maven - I'm getting this using Moonshine. In the morning this error points to different class. Now when I downloaded newest Nightly build - it points to some PureMVC class. : Internal error:

Build failed in Jenkins: Royale_ASDoc_Example #532

See Changes: [carlosrovira] maven: replace closure library in the rest of places -- [...truncated 42.48 KB...] [java]

Re: Maven Distribution SDK fixed and working for IDEs

Carlos, What has change more in case of Maven build for framework? On builds.a.o we have following command which running royale-asjs. It looks like something is missing, cause I have removed locally my org.apache.royale folder from .m2 and start building PureMVC to swc. [1] - It throws exception

Re: [Discuss] google closure library version for ANT/MAVEN (Re: Maven Distribution SDK fixed and working for IDEs)

And, IMO, we don't want to be bound to ClojureScript's release dates if we can help it. Perhaps those who want to see Maven releases from Google will have to contribute to Google a patch that builds a Maven artifact or publishes one based on a particular release artifact. It might be worth

Re: Generating Royale API report failing on Mac

On 1/22/20, 4:57 AM, "Piotr Zarzycki" wrote: Hi, This is the day of failing. I've definitely had days like this... Another issue which I'm struggling with is failing API report generation with SDK Nightly build [1] for a simple Hello World Flex app.

Re: [Discuss] google closure library version for ANT/MAVEN (Re: Maven Distribution SDK fixed and working for IDEs)

It's unfortunate that there isn't an official Maven release of Closure library that's managed by Google, like there is for Closure compiler. For context, we are currently using an "non-official" Maven release by the ClojureScript team. (Despite the similar name, ClojureScript has no relation to

Fwd: Apache PMCs: your chance to support your projects with Outreachy internships

Hi: Are we organized enough, and do we have enough bandwidth, do get some documentation help through this program? Mentoring can take an average of five hours a week, although that probably does not all have to be by one person. It may be, though, that a person with no AS3/MXML history would have

Re: Building Royale project with Maven throws NPE

Build is in progress. Once it's finish I will check -> https://builds.apache.org/job/Royale-compiler/1257/ śr., 22 sty 2020 o 15:54 Carlos Rovira napisał(a): > Hi Piotr, > latest commit seems to fix the problem. Let me know if all is now ok > sorry for the inconvenience > Carlos > > El mié., 22

Re: Building Royale project with Maven throws NPE

Hi Piotr, latest commit seems to fix the problem. Let me know if all is now ok sorry for the inconvenience Carlos El mié., 22 ene. 2020 a las 13:51, Carlos Rovira () escribió: > Hi Piotr, > > I can see the problem is related to my latest commit in compiler to solve > the GOOG_HOME problem. >

Build failed in Jenkins: royale-compiler-integration-tests #455

See Changes: -- [...truncated 127.53 KB...] [junit] for (const key in obj) { [junit]^ [junit] [junit] Jan 22,

Build failed in Jenkins: TourDeFlexMigration #530

See Changes: -- [...truncated 124.77 KB...] [mxmlc] Loading configuration: C:\jenkins\workspace\royale-asjs\frameworks\flex-config.xml [mxmlc]

Re: Flexlib Emulation

The video by the Flexlib author. http://tv.adobe.com/watch/360flex-conference/creating-reusable-components-by-ben-clinkinbeard/ On Wed, Jan 22, 2020 at 4:19 PM Takeshita Shoichiro wrote: > Greg, just for your reference. Flexlib provides MDI, multiple document > interface. This function

Build failed in Jenkins: Royale_ASDoc_Example #531

See Changes: -- [...truncated 42.06 KB...] [java] ^ [java] [java]

Generating Royale API report failing on Mac

Hi, This is the day of failing. Another issue which I'm struggling with is failing API report generation with SDK Nightly build [1] for a simple Hello World Flex app. Note that version 0.9.6 of Royale does work in that scenario. When I'm running following command in Terminal I get following

Re: Building Royale project with Maven throws NPE

Hi Piotr, I can see the problem is related to my latest commit in compiler to solve the GOOG_HOME problem. going to fix it El mié., 22 ene. 2020 a las 13:31, Carlos Rovira () escribió: > Hi Piotr, > > ok, now I understand... It's clear that I broke something since trying to > build now with

Re: Building Royale project with Maven throws NPE

Hi Piotr, ok, now I understand... It's clear that I broke something since trying to build now with Maven is generating the same issue ;) I was focused on making build works for IDEs, that didn't test normal maven path yesterday. I'll be looking over it to find where is the problem Sorry for the

Re: Building Royale project with Maven throws NPE

Hi Piotr, before understand the mistake, I downloaded and tested SDK from Jenkins (build #2552 that was the latest created) and build TDJ with VSCode and all worked ok (the same output as with Maven distribution created locally) Don't know if that report can be of help for you. El mié., 22

Re: Building Royale project with Maven throws NPE

Testing distribution is being handled in separate thread - you are mixing subjects :) śr., 22 sty 2020 o 13:22 Piotr Zarzycki napisał(a): > Exactly we are not discussion any stuff related to distribution :) We are > discussion at some point that maybe for some reason your changes influence >

Re: Building Royale project with Maven throws NPE

Exactly we are not discussion any stuff related to distribution :) We are discussion at some point that maybe for some reason your changes influence somehow compiler or anything else which end up with above error. Maybe that closure upgrade - I don't know. I look forward to hear more from someone

Re: Building Royale project with Maven throws NPE

Hi Piotr, El mié., 22 ene. 2020 a las 13:00, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > > > Nope. Let's pretend that you have clean PC. You have downloaded your Royale > application which contains pom.xml - You do "mvn clean install" - All the > dependencies will be downloaded

Re: Routing (was Re: Spectrum Components)

Hi Harbs, thanks for taking a look, I'll try to apply your suggestions and see if I can make it work. If you plan to work in that new Routing implementation, I'll wait for it to write about it in blog and social media, since better to point people to the more elaborated one. I as well recommend

Re: Building Royale project with Maven throws NPE

Comments inline: śr., 22 sty 2020 o 12:46 Carlos Rovira napisał(a): > Yes, I tried, and worked from js_only links, but as I did, I recall that > does not have any sense, since is the normal sdk Jenkins is building. > So reset...since I think we are not understanding to each one :) > > Your

Re: Building Royale project with Maven throws NPE

Yes, I tried, and worked from js_only links, but as I did, I recall that does not have any sense, since is the normal sdk Jenkins is building. So reset...since I think we are not understanding to each one :) Your first email talk about you building your project with maven. I suppose that you

Re: Building Royale project with Maven throws NPE

You will try to download from which Jenkins? - Do you refer to -> https://builds.apache.org/job/Royale-asjs/ or > http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ ? śr., 22 sty 2020 o 12:32 Carlos Rovira napisał(a): > Hi Piotr, > > one thing I already said is that

Re: Building Royale project with Maven throws NPE

My problem is completely unrelated to distribution - unless your changes influence other part. - I don't use Maven distribution to build anything. śr., 22 sty 2020 o 12:32 Carlos Rovira napisał(a): > Hi Piotr, > > one thing I already said is that currently Maven distribution is SWF and > JS,

Re: Building Royale project with Maven throws NPE

Hi Piotr, one thing I already said is that currently Maven distribution is SWF and JS, (not JS only). I requested Chris that I want to get JS only as well, so I need him to guide me for this change. Anyway, distribution requires the profile "option-with-swf" to work (in other case it fails and

Re: Maven Distribution SDK fixed and working for IDEs

Ok let's wait to see whether someone actually know what is the version. śr., 22 sty 2020 o 12:27 Carlos Rovira napisał(a): > Hi Piotr, > > I explained in this thread that I couldn't find in maven the same exact > version that ANT one, I put the closest in date available from maven > I proposed

Re: Maven Distribution SDK fixed and working for IDEs

Hi Piotr, I explained in this thread that I couldn't find in maven the same exact version that ANT one, I put the closest in date available from maven I proposed as well if we can upgrade ANT/MAVEN to the same one that works. Other thing is that maybe I fail in the search and the version could

Re: Building Royale project with Maven throws NPE

It is possible that Moonshine issue build which is based on http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ - may be something different than I reported after build by Maven. śr., 22 sty 2020 o 12:03 Piotr Zarzycki napisał(a): > Carlos, > > Just to make sure that

Re: Maven Distribution SDK fixed and working for IDEs

Why you didn't use exactly the same version ? Maybe this is the reason why my application is failing. I see this in Maven: com.google.javascript closure-compiler v20181210 org.clojure google-closure-library 0.0-20190213-2033d5d9 śr., 22 sty 2020 o 10:52 Carlos Rovira napisał(a): > Hi Alex,

Re: Building Royale project with Maven throws NPE

Carlos, Just to make sure that you understand. When I'm building my application I don't relay on local build from sources - I only rely on what Jenkins is building. In case of Maven it would be https://builds.apache.org/job/Royale-asjs/ in case of Moonshine it would be

Re: Building Royale project with Maven throws NPE

In case of Maven I have used this -> https://builds.apache.org/job/Royale-asjs/2551/ and that https://builds.apache.org/job/Royale-compiler/1255/ - Those builds should contains your changes. śr., 22 sty 2020 o 11:58 Carlos Rovira napisał(a): > Hi Piotr, > > first I need to know about the other

Re: Building Royale project with Maven throws NPE

Hi Piotr, first I need to know about the other email I sent just now, if you're using latest sources, and depending on that will go over this El mié., 22 ene. 2020 a las 10:40, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Ok doing build trough Moonshine it's actually also failing.

Re: Building Royale project with Maven throws NPE

Hi Piotr, this error was the issue yesterday without the GOOG_HOME patch. did you rebuild today with latest fixes in compiler and framework? El mié., 22 ene. 2020 a las 10:19, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > Hi Guys, > > I have just tired build our project with Maven

Re: Building Royale project with Maven throws NPE

I have used the oldest available build [1] and it's still failing when I'm building trough Moonshine. [1] http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/656/ śr., 22 sty 2020 o 10:40 Piotr Zarzycki napisał(a): > Ok doing build trough Moonshine it's actually also

Build failed in Jenkins: royale-compiler-integration-tests #454

See Changes: -- [...truncated 130.46 KB...] [junit] [junit] Jan 22, 2020 10:03:59 AM

Re: Maven Distribution SDK fixed and working for IDEs

Hi Alex, I didn't put the latest one. Used the closest one in dates to the one in ANT. Should be that valid? And how can I ensure compatibility? Where to check that? But what I really want to do is update ANT/MAVEN to the same one that is ok for all of us. We need to ensure one that is available

Re: Building Royale project with Maven throws NPE

Ok doing build trough Moonshine it's actually also failing. I did build with -debug=false and got following exception: : Internal error: java.nio.file.InvalidPathException: Illegal char <:> at index 4:

Build failed in Jenkins: TourDeFlexMigration #529

See Changes: -- [...truncated 124.12 KB...] [mxmlc] Loading configuration: C:\jenkins\workspace\royale-asjs\frameworks\flex-config.xml [mxmlc]

Building Royale project with Maven throws NPE

Hi Guys, I have just tired build our project with Maven (we are using it when wanted to deploy version on the server) and I'm getting following compilation error: got null for string/internal.js > got null for debug/errorcontext.js > got null for debug/debug.js > Internal error:

Build failed in Jenkins: Royale_ASDoc_Example #530

See Changes: -- [...truncated 41.42 KB...] [java] ^ [java] [java]

Build failed in Jenkins: royale-compiler-integration-tests #453

See Changes: -- [...truncated 131.04 KB...] [junit] [junit] Jan 22, 2020 8:12:54 AM