Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 13 - Failure!

Yes, just read it, thanks :) El lun., 13 jul. 2020 a las 9:34, Harbs () escribió: > Alex just said we do. Apparently there were changes after the last release > related to reproducible builds. > > > On Jul 13, 2020, at 10:32 AM, Carlos Rovira > wrote: > > > > Hi Harbs, > > also I don't think we

Re: Trying to do daily build fail

I tried to build from the previous commit that started your try yesterday but I get the same error. Could be something external? There was some change in Royale-extras? El lun., 13 jul. 2020 a las 9:42, Harbs () escribió: > I just reverted the changes to versions from starting the release >

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

Not sure. It worked for Yishay when he did it, and I don’t think he put his credentials on the CI server. There are manual steps for pushing the git. I did that. Did something change in the compiler-build-tools between when Yishay did the release and now that might effect this? > On Jul 13,

Re: Apache Royale track at ApacheCon 2020

By the way, I am not even sure the track requires a fuller name than "Royale". I will look into it. a On Mon, Jul 13, 2020 at 7:27 AM Andrew Wetmore wrote: > Front-end-technology is fine, I guess. However, I can build a full app > with Royale if I am using just local storage or JSON files for

Re: Apache Royale track at ApacheCon 2020

Front-end-technology is fine, I guess. However, I can build a full app with Royale if I am using just local storage or JSON files for data and not relying on a back end structure in a language like mySQL. So it seems to me far stronger than a tool to design the front end of an app or service. a

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 14 - Still Failing!

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 14 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/14/ to view the results.

Re: Royale_Release_Step_002 - Build # 50 - Still Failing!

Hi, ok, now I understand why tools is going to be release, so forgot my previous email. as others says maven is responsible itself of updating "SNAPSHOTS", you don't need to do it manually El lun., 13 jul. 2020 a las 8:08, Piotr Zarzycki () escribió: > It is also not recommended to do that

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 13 - Failure!

Alex just said we do. Apparently there were changes after the last release related to reproducible builds. > On Jul 13, 2020, at 10:32 AM, Carlos Rovira wrote: > > Hi Harbs, > also I don't think we require a Tools release this time. There's no change > in that part this time, so Tools can be

Re: Trying to do daily build fail

Hi, seems build is now working now, thanks to Github god! :D El lun., 13 jul. 2020 a las 10:07, Carlos Rovira () escribió: > I was checking with Chris, and seems the problem is Royale-extras access > via github webui. > That's blocking all the build. > I think we should try to think a way to

Re: Royale_Release_Step_002 - Build # 50 - Still Failing!

Hi all, well I agree that it might be good to release the build tools first, but it seems that the builds were reproducible even without these changes. So theoretically it should be possible to do the release without releasing the build tools first. Chris Am 13.07.20, 09:35 schrieb "Carlos

Re: Royale_Release_Step_002 - Build # 50 - Still Failing!

Yeah ... we should, however it's not really an issue ... It's just something maven would like us to do and shouldn't cause any harm in the release. And regarding the upstream changes ... I know what the changes were as I implemented them. And therefore I would say: If the last release was

Re: Trying to do daily build fail

I haven’t changed royale-extras recently. > On Jul 13, 2020, at 10:45 AM, Carlos Rovira wrote: > > I tried to build from the previous commit that started your try yesterday > but I get the same error. > Could be something external? There was some change in Royale-extras? > > > El lun., 13

Re: Apache Royale track at ApacheCon 2020

Hi, "Apache Royale - The reincarnation of the greatest RIA" At least I wouldn't just call it "Application" ... I would make the name imply it being a Web-Frontend technology. Chris Am 13.07.20, 10:39 schrieb "Carlos Rovira" : Hi Andrew, some proposals: - We could go with

Re: Royale_Release_Step_002 - Build # 50 - Still Failing!

I’m going to try and go with 1. I’ll spend some more time trying to figure out the rm credentials thing. If I can’t figure it out, I’m going to have to wait for Alex. > On Jul 13, 2020, at 12:34 PM, Christofer Dutz > wrote: > > Ah ok, > > so the build-tools property was updated to the

Re: Royale_Release_Step_002 - Build # 50 - Still Failing!

Ah ok, so the build-tools property was updated to the SNAPSHOT version. In my memory the property stayed on the last released version, but seems that was updated a few weeks ago. Well in this case you have two options: 1) You release the build tools and then update that property to the release

RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

I don’t remember. Can you link the discussion from the archives? From: Harbs Sent: Monday, July 13, 2020 12:47 PM To: Apache Royale Development Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

https://lists.apache.org/thread.html/rf263801c4e33cc08f473bd6dd0f6c3f28b131c0a48612d70c7b36bc7%40%3Cdev.royale.apache.org%3E > On Jul 13, 2020, at 1:13 PM, Yishay Weiss wrote: > > I don’t remember. Can you link the discussion from the archives? > > From: Harbs >

RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

This relates to issues I had with uploading to the Nexus server which only happens at a later stage. It ended up being a non-issue for me after we resolved some unnecessary loop in the upload process. From: Harbs Sent: Monday, July 13, 2020 1:23 PM To:

Trying to do daily build fail

Hi, trying to do my daily build but something is failing. Not sure what it's. This the last part of the log: [*ERROR*] Command execution failed. *org.apache.commons.exec.ExecuteException*: *Process exited with an error: 5 (Exit value: 5)* *at*

Re: Trying to do daily build fail

I just reverted the changes to versions from starting the release yesterday. That might have effected your build. > On Jul 13, 2020, at 10:29 AM, Carlos Rovira wrote: > > Hi, > > trying to do my daily build but something is failing. Not sure what it's. > This the last part of the log: > >

Re: Apache Royale track at ApacheCon 2020

Hi, yeah, I don't think we should limit ourselves to "Apps" too. El lun., 13 jul. 2020 a las 10:47, Christofer Dutz (< christofer.d...@c-ware.de>) escribió: > Hi, > > "Apache Royale - The reincarnation of the greatest RIA" > > At least I wouldn't just call it "Application" ... I would make the

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

Or maybe the issue is a few lines up? [INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ compiler-build-tools --- [INFO] [INFO] Downloading from apache.snapshots.https:

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

Where am I supposed to put credential into the jenkins server? > On Jul 13, 2020, at 12:02 PM, Yishay Weiss wrote: > > Are you sure it’s not an Apache credentials problem? Last time I looked it > looked like you were getting 401 from the server. > > From: Harbs >

Re: Royale_Release_Step_002 - Build # 50 - Still Failing!

So do you have an explanation why the royale-compiler release failed when I tried? > On Jul 13, 2020, at 12:19 PM, Christofer Dutz > wrote: > > Yeah ... we should, > > however it's not really an issue ... It's just something maven would like us > to do and shouldn't cause any harm in the

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

Yeah ... just wanted to say: If you want to deploy to the Apache Nexus, you need credentials. Usually I have them defined in my settings.xml but I wouldn't want that done on the CI server. Wasn't this what some of the steps were about? The RM downloads the bundle built on the CI server and then

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

There was a discussion on April 28, but I did not follow what you did. Did you release the compiler-build-tools from your local machine or from the CI server? > On Jul 13, 2020, at 12:26 PM, Yishay Weiss wrote: > > Based on > > cat C:\Users\ApacheRoyaleCI\.m2\settings.xml > > >

Re: Apache Royale track at ApacheCon 2020

Hi, about Crux, it's part of the todomvc track. In the case of migrating, I think folks doing it will focus on the main points of how to make MX/SPARK working on Royale. In the case of Crux, it really is Swiz Framework, so if you used it in Flex, the change is just about namespaces and prefixes

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 13 - Failure!

Maybe, but IIRC, it shouldn't be uploading to snapshots, it should be uploading to releases/staging. Look at the console output from the last known good build (#12). There may be something wrong with the tag. It may not have tagged the poms with the SNAPSHOT removed. HTH, -Alex On

Royale Compiler Build Tools Release Step 001 Succeeded

Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the following commands: git push --set-upstream origin develop git push origin org.apache.royale.compiler-build-tools-1.2.1-rc1 You will need your

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

Apparently the problem was not github being down: [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 13 - Failure!

Can any Maven experts explain why this is failing? http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/13/console FWIW, there’s this warning which should probably be fixed… [WARNING] Some problems were encountered while building the effective

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 13 - Failure!

I’m guessing it’s a permissions problem transferring to repository.a.o: [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 13 - Failure!

It’s probably that I didn’t roll back after trying to start the Royale release. I just reverted those changes and I’ll start this again... > On Jul 13, 2020, at 9:37 AM, Alex Harui wrote: > > Maybe, but IIRC, it shouldn't be uploading to snapshots, it should be > uploading to

Royale_Compiler_Build_Tools_Release_Step_001 - Build # 21 - Failure!

Royale_Compiler_Build_Tools_Release_Step_001 - Build # 21 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_001/21/ to view the results.

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 13 - Failure!

Hi Harbs, also I don't think we require a Tools release this time. There's no change in that part this time, so Tools can be skipped and just release compiler, typedefs and asjs. In latest release we did a Tools release since there was changes, and was good to test the process with that variant,

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/15/ to view the results.

Re: Trying to do daily build fail

Oh. Looks like Github is down. > On Jul 13, 2020, at 10:48 AM, Harbs wrote: > > I haven’t changed royale-extras recently. > >> On Jul 13, 2020, at 10:45 AM, Carlos Rovira wrote: >> >> I tried to build from the previous commit that started your try yesterday >> but I get the same error. >>

Re: Royale_Release_Step_002 - Build # 50 - Still Failing!

I don’t know, but there seems to be an upstream dependency which needs to be released. Presumably that’s the compiler-build-tools. > On Jul 13, 2020, at 11:44 AM, Christofer Dutz > wrote: > > Hi all, > > well I agree that it might be good to release the build tools first, but it > seems

RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

Good question. Let me see if I can figure this out. From: Harbs Sent: Monday, July 13, 2020 12:05 PM To: dev@royale.apache.org Subject: Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing! Where am I supposed

Re: Trying to do daily build fail

I was checking with Chris, and seems the problem is Royale-extras access via github webui. That's blocking all the build. I think we should try to think a way to avoid this problem since it blocks completely a build. This is a good moment to see it :) El lun., 13 jul. 2020 a las 9:49, Harbs ()

Re: Apache Royale track at ApacheCon 2020

Hi Andrew, some proposals: - We could go with something that shows projection like "Apache Royale, Next Gen Application Technology" - Or something more funny like "Apache Royale, Back to the Future" - Or maybe a combo of two like "Apache Royale, application front-ends for the

Re: Royale_Release_Step_002 - Build # 50 - Still Failing!

BTW, where should this be fixed? [WARNING] Some problems were encountered while building the effective model for org.apache.royale.compiler:compiler-build-tools:maven-plugin:1.2.1-SNAPSHOT [WARNING] 'build.pluginManagement.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/16/ to view the results.

RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

Are you sure it’s not an Apache credentials problem? Last time I looked it looked like you were getting 401 from the server. From: Harbs Sent: Monday, July 13, 2020 11:58 AM To: dev@royale.apache.org Subject: Re:

RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 16 - Still Failing!

Based on cat C:\Users\ApacheRoyaleCI\.m2\settings.xml http://maven.apache.org/SETTINGS/1.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd;>

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!

It’s still having issues: [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project compiler-build-tools: Failed to deploy artifacts: Could not transfer artifact

Re: Apache Royale track at ApacheCon 2020

Hi all, You mean: "We are Royale: All your frontends are belong to us"? __ Chris Am 13.07.20, 14:41 schrieb "Alina Kazi" : Apache Royale future to all Frontend Technologies and New life to Flex ;) Alina On Mon, 13 Jul 2020, 3:41 am Andrew Wetmore, wrote: > Any thoughts on

Re: Apache Royale track at ApacheCon 2020

Apache Royale future to all Frontend Technologies and New life to Flex ;) Alina On Mon, 13 Jul 2020, 3:41 am Andrew Wetmore, wrote: > Any thoughts on a short, evocative title for the track? How about "Apache > Royale: Application Builder"? > > On Sun, Jul 12, 2020 at 7:28 AM Carlos Rovira >

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!

I’m trying to wrap my head around all the pieces here. How does the uploading to the nexus server work? > On Jul 13, 2020, at 7:21 PM, Alex Harui wrote: > > IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM > version. Compare the tag from 1.2.0. > > Maven should

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!

On 7/13/20, 9:32 AM, "Harbs" wrote: I’m trying to wrap my head around all the pieces here. How does the uploading to the nexus server work? It doesn't. After some snooping through the archives, I think that some credentials were (unsafely) stored on the CI Server. The

VSCode debugger issues since 1.47

Hi, I'm not able to launch Royale apps from Visual Studio Code since the latest update (1.47). I opened an issue in AS3 extension [1] but Josh said extension doesn't do anything for debugging. I must read more about changes [2], but want to know if someone here knows what's happening. [1]

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!

Another option is to find a way for Jenkins to securely pass the credentials to maven without it showing up in the logs. Yishay I think found a way to do that with Ant, but not sure about Jenkins jobs. HTH, -Alex On 7/13/20, 10:25 AM, "Alex Harui" wrote: On 7/13/20, 9:32 AM, "Harbs"

Re: VSCode debugger issues since 1.47

Hi, finally Josh provide a way to make it work in the extension issue 491 [1] [1] https://github.com/BowlerHatLLC/vscode-as3mxml/issues/491 El lun., 13 jul. 2020 a las 18:36, Carlos Rovira () escribió: > Hi, > > I'm not able to launch Royale apps from Visual Studio Code since the > latest

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!

IMO, step 1 went sideways. The tag should not contain SNAPSHOT in the POM version. Compare the tag from 1.2.0. Maven should also not be adding a timestamp to the artifact name. I don't remember why it does that, but I think there are internet articles about it. Comparing output of

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!

The Date-Versions you are seeing is how a SNAPSHOT is usually stored on a remote repository. If you have a look at the content every new snapshot will be added to the remaining and each will have a different date and a counter at the end. Maven uses this to detect if there is a newer version

RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!

I don’t recall removing credentials the CI server. The last successful build [2] shows I was the one who performed that step. One thing I couldn’t understand was how come these lines have my name in them [1]. Where does yishayw get retrieved from? [INFO] fetch url:

RE: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!

I’m going to try to change the job on Jenkins so it accepts Apache credentials as params and propagates them to the mvn command. I don’t know if Jenkins forms have a password element that hides the password though. From: Alex Harui Sent: Monday, July 13, 2020

Re: Royale_Compiler_Build_Tools_Release_Step_002 - Build # 15 - Still Failing!

I have a vague recollection of removing credentials. But also, I think the Maven/Nexus credentials might have been stored in a password manager when we last release compiler-build-tools. You may have run Maven from the command line and typed in credentials and they got stored. Later, we

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 13 - Failure!

Royale_Compiler_Build_Tools_Release_Step_002 - Build # 13 - Failure: Check console output at http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Compiler_Build_Tools_Release_Step_002/13/ to view the results.

RE: Royale_Release_Step_002 - Build # 50 - Still Failing!

You shouldn’t need to remove -SNAPSHOT manually. That should happen as part of (Royale) release step 2, which run mvn release:prepare [1] [1] https://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html From: Harbs Sent: Sunday, July

Re: Royale_Release_Step_002 - Build # 50 - Still Failing!

It is also not recommended to do that manually. Maven has special commands for such things. On Mon, Jul 13, 2020, 8:06 AM Yishay Weiss wrote: > You shouldn’t need to remove -SNAPSHOT manually. That should happen as > part of (Royale) release step 2, which run mvn release:prepare [1] > > [1] >