RE: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

the > package and signature files, unzipping, etc, you can instead: > > 1) create an empty folder, > > 2) download into that folder this file: > > > https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/ApproveBuildTools.xml > > 3) run the script: > &

RE: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

Sunday, April 19, 2020 5:10 PM To: Apache Royale Development<mailto:dev@royale.apache.org> Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0 Ok Yishay, and is this version used in current 0.9.7 ongoing release process? thanks El dom., 19 abr. 2020 a las 15:37,

RE: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

() escribió: > Ok Yishay, > > and is this version used in current 0.9.7 ongoing release process? > > thanks > > > > El dom., 19 abr. 2020 a las 15:37, Yishay Weiss () > escribió: > >> Hi Carlos, >> >> It’s already been released, just haven

RE: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

Turns out my public key needed to be distributed to a keyserver. gpg --keyserver http://keyserver.ubuntu.com --send-keys did the trick. You should see it now. From: Yishay Weiss Sent: Sunday, April 19, 2020 5:22:56 PM To: dev@royale.apache.org Subject: RE: [VOTE] Release Apache Royale

RE: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

that is still to be checked if that works), along other fixes in compiler. Thanks El dom., 19 abr. 2020 a las 19:37, Yishay Weiss () escribió: > Turns out my public key needed to be distributed to a keyserver. > > > > gpg --keyserver http://keyserver.ubuntu.com --send-ke

RE: [royale-compiler] branch release/0.9.7 updated: Update compiler build tools version

Carlos, are you sure your commit belongs in dev at this stage? If we are going to merge release into dev anyway, maybe it’s best to wait until then to avoid this conflict. Also, I’m not a Git expert, but wouldn’t the merge algorithm detect the identity in content anyway and avoid conflict?

RE: Prioritize Release Jobs on CI

Can’t you do that with remote desktop? From: OmPrakash Muppirala Sent: Monday, April 13, 2020 9:51:25 AM To: Apache Royale Development Subject: Re: Prioritize Release Jobs on CI Alex, I believe this is your personal Azure subscription right? Any chance I can

RE: Prioritize Release Jobs on CI

: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Monday, April 13, 2020 9:55 AM To: dev@royale.apache.org<mailto:dev@royale.apache.org> Subject: RE: Prioritize Release Jobs on CI Can’t you do that with remote desktop? From: OmPrakash Muppirala Sent: Mond

RE: Royale Compiler Build Tools Release Step 002 Succeeded

>2. Validate that the compiled artifacts match the downloaded artifacts. What does this mean? Looks to me like the jars are different [1]. I’ll see if I understand why. [1] C:\temp1>git diff

RE: Prioritize Release Jobs on CI

I’d like to try and install an ssh server. Can anyone think of a reason not to do that? I’m asking in terms of security, and if there might be a problem because it’s a VM. Thanks. From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Monday, April 13, 2020 10:02 AM To: dev@royale.apac

RE: [DISCUSS] Discuss Release Apache Royale 1.2.0

> > > > > I think that most people will be fine, but I just wanted to mention it. > > > > > > -- > > > Josh Tynjala > > > Bowler Hat LLC <https://bowlerhat.dev> > > > > > > > > > On Mon, Apr 13, 2020 at 1:33 PM wrot

RE: [DISCUSS] Discuss Release Apache Royale 1.2.0

pache Royale 1.2.0 Hi Yishay, not sure but probably the empty file added will cause RAT problems with maven maybe you should see if that happens and at least add a license header About content, since is taken from the git history I think is ok thanks El vie., 17 abr. 2020 a las 10:14,

RE: [royale-asjs] branch develop updated: jewel-scrollToIndex: remove isolated function

Build is failing. Looks like you forgot to remove scrollToIndex from JewelClasses From: carlosrov...@apache.org Sent: Friday, April 17, 2020 3:56:44 AM To: comm...@royale.apache.org Subject: [royale-asjs] branch develop updated: jewel-scrollToIndex: remove

RE: [royale-asjs] branch develop updated: jewel-scrollToIndex: remove isolated function

: remove isolated function Thanks just commited :) El vie., 17 abr. 2020 a las 13:30, Yishay Weiss () escribió: > Build is failing. Looks like you forgot to remove scrollToIndex from > JewelClasses > > > From: carlosrov...@apache.org > Sent: Friday

RE: About Releasing 0.9.7

My impression was that Alex was working on integrating the latest Maven changes in the CI release steps. I’ll take over as soon as he’s got that polished. Alex, let me know if there’s anything I can do to speed things up. From: Carlos Rovira Sent: Wednesday,

RE: How to build users project using ANT to JS only

:49 Yishay Weiss napisał(a): > Bumping this. I’m wondering if Moonshine accidentally injects that file > which may cause these kinds of bugs. The script should verify your > ROYALE_COMPILER_HOME env var by checking for > ROYALE_COMPILER_HOME\lib\jsc.jar. It probably should not be there

RE: How to build users project using ANT to JS only

in-js\royale-asjs\js\lib\ śr., 8 kwi 2020 o 15:20 Yishay Weiss napisał(a): > > > >I should not have that jsc.jar inside downloaded sdk? > > It should not exist under > > > c:\MoonshineSDKs\Royale_SDK\apache-royale-0.9.7-bin-js\royale-asjs\lib\jsc.jar > > It should

RE: How to build users project using ANT to JS only

Taken from build_example.xml From: Yishay Weiss Sent: Wednesday, April 8, 2020 4:25:56 PM To: dev@royale.apache.org Subject: RE: How to build users project using ANT to JS only So it does not exist under c:\MoonshineSDKs\Royale_SDK\apache-royale-0.9.7-bin-js

RE: Layouts: Changing widthChanged/heightChanged/sizeChanged event rules

MX|Panel From: Yishay Weiss Sent: Monday, March 16, 2020 10:08:49 AM To: dev@royale.apache.org Subject: RE: Layouts: Changing widthChanged/heightChanged/sizeChanged event rules I’ve just updated Royale and am seeing weird behavior in Panel layout

RE: Layouts: Changing widthChanged/heightChanged/sizeChanged event rules

I’ve just updated Royale and am seeing weird behavior in Panel layout. The content is taking up all the space and obliterating the title and the rest of the chrome elements. Not sure if it’s related to these changes. Will try to isolate it. From: Alex Harui

RE: Some info from the current CI server emails

uot; steps will go away and some of the instructions in the remaining steps will be simpler. -Alex On 4/1/20, 8:37 AM, "Carlos Rovira" wrote: Hi Yishay thanks go ahead, and report you findings :) El mié., 1 abr. 2020 a las 14:28, Yishay Weiss () escrib

RE: [DISCUSS] Coming back to collect requirements for the release process

nue to > > support having more Maven and less Ant in the release process have not > > stepped up to examine the build-tools release candidate, one of the > > outcomes of these Maven changes that you wanted to see. Instead, this > > effort has cost me considerable time that could

RE: [royale-compiler] 01/01: Works on given test case. Hope I didn't break anything.

Hi, Changing to emitClosureStart(); emitAssignedValue(assignedNode); MemberAccessExpressionNode maenode = (MemberAccessExpressionNode)assignedNode;

RE: Releasing: Finally giving up

I think the focus should be to agree on the requirements. Whether an RM uses the tool created by Chris or Alex can be a matter of choice. From: Carlos Rovira Sent: Wednesday, March 25, 2020 5:18 PM To: Apache Royale Development

RE: Numbers not initialized to NaN

not initialized to NaN Numbers should be initialized to NaN, unless you've added -js-default-initializers=false to your compiler options. -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Thu, Mar 26, 2020 at 9:17 AM Yishay Weiss wrote: > I think this might have come up in one

RE: Numbers not initialized to NaN

it would matter if the value was undefined or initialized to NaN. And thus, I'm not sure why the code went in the wrong direction. On 3/26/20, 9:45 AM, "Yishay Weiss" wrote: isNaN(undefined) is actually true, same as isNaN(NaN). From: Yishay Weiss<mailto:yishayj...@hotmail.

RE: Numbers not initialized to NaN

isNaN(undefined) is actually true, same as isNaN(NaN). From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Thursday, March 26, 2020 6:27 PM To: dev@royale.apache.org<mailto:dev@royale.apache.org> Subject: RE: Numbers not initialized to NaN Ok, I’ll investigate why it’s undefin

RE: Numbers not initialized to NaN

height in different phases of the layout due to its positioner.offsetHeight changing. The weird thing is that positioner looks exactly the same [1], whether its offsetHeight is 19 or 34. Any ideas would be welcome. [1] 3 From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Thursday, Ma

Numbers not initialized to NaN

I think this might have come up in one of my previous posts so my apologies if I’m repeating a question. In Flex.as we have the following code: if (!isNaN(percentHeight) && child.includeInLayout) {

RE: Releasing: Finally giving up

it. El jue., 26 mar. 2020 a las 19:50, Alex Harui () escribió: > @Yishay Weiss > > Let's wait until the set of Maven steps are available from Chris and > Carlos. Then I will try to find some cycles to help you. Because of where > I live, where the schools are closed, and my kids s

RE: Some info from the current CI server emails

Chris has done a good job of gathering the abstract requirements. We have one issue which is not agreed on by Alex, and having understood things better, myself. I think we need to vote on that. El mié., 1 abr. 2020 a las 11:07, Yishay Weiss () escribió: > I was hoping the technical requiremen

RE: Some info from the current CI server emails

I was hoping the technical requirements thread would spawn a vote on the remaining issues. If the result is that the maven solution as it stands today does not meet the agreed requirements then we will have no choice but to use the CI server process. Assuming that’s the situation, I will wait

RE: [DISCUSS] Coming back to collect requirements for the release process

ight actually make the process longer. Am 01.04.20, 11:00 schrieb "Yishay Weiss" : Let’s keep this thread about the technical requirements. We can start a new thread about what to do next. Although people feel like we’re going around in circles, I personally have gained a much be

RE: Some info from the current CI server emails

ok with the evidences Chris reported various times about that the new standard process is all what we need? He responded again some minutes ago to the other list Thanks Carlos El mié., 1 abr. 2020 a las 11:19, Yishay Weiss () escribió: > > >If we are discussing if we can use just

RE: Royale zip package of Nightly build missing some empty folders

Hi Piotr, Is HelloWorld example building for you with Ant? Yishay From: Piotr Zarzycki Sent: Friday, April 3, 2020 3:10 PM To: Apache Royale Development Subject: Royale zip package of Nightly build missing some empty folders Hi

RE: Royale zip package of Nightly build missing some empty folders

s Hi Yishay, No changes here. It doesn't build. I don't know why. I will ask more question regarding mxmlc in different thread once above will be resolved. pt., 3 kwi 2020 o 15:04 Yishay Weiss napisał(a): > Hi Piotr, > > Is HelloWorld example building for you with Ant? > > Yish

Can't Push to GitHub

Is anyone else having trouble with GitHub? It’s slow and I keep getting the authentication window and then fatal: TaskCanceledException encountered. A task was canceled.

RE: Can't Push to GitHub

to use gitbox urls, what make all worked again. Try the gitbox alternative urls and check if it works for you El sáb., 28 mar. 2020 a las 18:41, Yishay Weiss () escribió: > Is anyone else having trouble with GitHub? It’s slow and I keep getting > the authentication window and then >

RE: Can't Push to GitHub

This looks like a problem in my network connection. GitHub is especially slow but so are other sites. From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Saturday, March 28, 2020 10:36 PM To: dev@royale.apache.org<mailto:dev@royale.apache.org> Subject: RE: Can't Push to GitH

RE: Can't Push to GitHub

tbox instead? Chris Am 29.03.20, 13:24 schrieb "Yishay Weiss" : This looks like a problem in my network connection. GitHub is especially slow but so are other sites. From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Saturday, March 28, 2020 10:36 PM

RE: [DISCUSS] Coming back to collect requirements for the release process

ify that these scripts work? I may be missing something… Am 31.03.20, 17:59 schrieb "Yishay Weiss" : > - Some tooling could be added to validate artifacts created by any form of distribution with ones built by Ant If I understand Alex’s concern correctly he wants

RE: [DISCUSS] Coming back to collect requirements for the release process

convenience. (Of course you shouldn't be shipping broken things) Chris Am 31.03.20, 19:05 schrieb "Yishay Weiss" : > Ideally it wouldn't matter if you build it with Ant or Maven. As I understand it, the scenario is that a developer makes a change and needs to package that c

RE: [DISCUSS] Coming back to collect requirements for the release process

> the right thing is to actually run "ant release" at some point in the > release process. In which case, you might as well use the resulting > artifacts. > > My 2 cents, > -Alex > > On 3/30/20, 12:11 PM, "Yishay Weiss" wrote:

RE: [DISCUSS] Coming back to collect requirements for the release process

have CI pipelines for continuously checking that the builds work. I wouldn't expect too many RCs to be cancelled for such reasons. Chris Am 31.03.20, 19:55 schrieb "Yishay Weiss" : Chris, is this how you see it too? >Chris wants to put the verification of the build.xml fi

RE: [DISCUSS] Coming back to collect requirements for the release process

Chris, is this how you see it too? >Chris wants to put the verification of the build.xml files on the voters. On 3/31/20, 10:05 AM, "Yishay Weiss" wrote: > Ideally it wouldn't matter if you build it with Ant or Maven. As I understand it, the scenario is that a

RE: Releasing: Finally giving up

nks El dom., 29 mar. 2020 a las 15:59, Yishay Weiss () escribió: > Ok, I’m ready. What’s next? Do I need to cancel an RC? How do I login to > Jenkins? Where do I start? > > From: Alex Harui<mailto:aha...@adobe.com> > Sent: Thursday, March 26, 2020 8:50 PM > To: dev@royale.apa

RE: [royale-asjs] branch develop updated: Make sure mx combobox shows label

Fair enough. I copied that from the spark implementation, maybe they could both use refactoring. From: Alex Harui Sent: Sunday, March 29, 2020 11:07 PM To: dev@royale.apache.org;

RE: [DISCUSS] Coming back to collect requirements for the release process

> Ant artifacts are reproducible by running the Ant scripts. Again, the > scenario is that if an Ant user wants to try a local change in an IDE or NPM > we want >to ensure that they can run the Ant "release" target and get the > tar.gz or .zip they need. “Again” suggests you’ve already given

RE: Can't Push to GitHub

/asf/royale-asjs.git Chris Am 29.03.20, 13:39 schrieb "Yishay Weiss" : Hi Chris, I’m not familiar with GitBox. How does that work? Thanks. From: Christofer Dutz<mailto:christofer.d...@c-ware.de> Sent: Sunday, March 29, 2020 2:26 PM To: dev@royale.apach

RE: Releasing: Finally giving up

Ok, I’m ready. What’s next? Do I need to cancel an RC? How do I login to Jenkins? Where do I start? From: Alex Harui<mailto:aha...@adobe.com> Sent: Thursday, March 26, 2020 8:50 PM To: dev@royale.apache.org<mailto:dev@royale.apache.org>; Yishay Weiss<mailto:yishayj...@hotmail.c

RE: [DISCUSS] Coming back to collect requirements for the release process

:26, Yishay Weiss () escribió: > > >Why "must" a RM built with all supported build systems and not just be > able to choose the >one he wants? > > To ensure that every developer is able to test his Royale changes on his > choice IDE. Part of the release is scripts th

RE: Royale Releases

Chris, I think you’re missing Alex’s point. We’re not running Ant to make sure it doesn’t blow up. We’re running it to make sure the resultant tar.gz/zip files are identical to the ones created by Maven. Alex, please correct me if I’m wrong. From: Christofer

RE: Royale Releases

I’m fine with that. Thanks. From: Harbs Sent: Thursday, April 2, 2020 4:50:40 PM To: dev@royale.apache.org Subject: Re: Royale Releases I spent over an hour with Alex on the Zoom last night trying to understand all the different technical points. One point

RE: Releasing: Finally giving up

Hi All, I too, feel very uncomfortable participating in these threads. While grateful to Carlos and Chris for their work I’m very annoyed with the tone of ultimatums and doom and gloom. Alex has put in a lot of work into this and I trust his concerns are technical, rather than protecting his

RE: [royale-compiler] 01/01: Works on given test case. Hope I didn't break anything.

goal should be something like this: org.apache.royale.utils.Language.closure(this.parentApplication.buttonFunction, this.parentApplication, ' buttonFunction'); I can't spend more time on that right now, but if you want to try that might help On Mon, Apr 6, 2020 at 9:16 AM Yishay Weiss wrote: > H

RE: How to build users project using ANT to JS only

Also, see if c:\MoonshineSDKs\Royale_SDK\apache-royale-0.9.7-bin-js\royale-asjs\lib\jsc.jar exists, and if it does, where it comes from. My nightly download doesn’t have it. From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Monday, April 6, 2020 2:57 PM To: dev@royale.apache.org<m

RE: How to build users project using ANT to JS only

> Piotr > > > > > > pt., 3 kwi 2020 o 18:40 Alex Harui > > > > napisał(a): > > > > > > > Download 0.9.6 and see what it has. > > > > > > >

RE: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

Awesome From: aha...@apache.org Sent: Monday, April 27, 2020 8:56:00 AM To: comm...@royale.apache.org Subject: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails This is an automated email from the ASF dual-hosted git repository. aharui

RE: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

asjs] branch release/0.9.7 updated: add retry task if wagon fails Hi all, a week ago a new version of Wagon was released ... perhaps worth updating to 3.4.0? Chris Am 27.04.20, 11:58 schrieb "Yishay Weiss" : Awesome From: aha...@apache

RE: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

Actually, I think I got the syntax wrong here. If you see an error message such as “Try mvn "" -rf :royale-typedefs-googlemaps” Then you should do ant -f releasesteps.xml retryUploadSWCs -Drf_arg=:royale-typedefs-googlemaps Where :royale-typedefs-googlemaps serves here as an example, but

RE: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

Royale Development<mailto:dev@royale.apache.org> Subject: Re: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails Yishay, In the other words you experienced same issue as me and others on Windows... Nothing changed. On Mon, Apr 27, 2020, 12:21 PM Yishay Weiss wrote: > I

RE: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

he CI server before we can find out. -Alex On 4/28/20, 1:57 AM, "Yishay Weiss" wrote: I think it should be possible to do this in powershell, with: $password = Read-Host "Enter Password" -AsSecureString And pass $pass as the param. Are you suggesting to

RE: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

the chances it passes are pretty high. In the end, if things would go south exactly 5 times for every artifact it would sort of be like if you tried running the bunch 6000 times. Chris Am 28.04.20, 18:21 schrieb "Yishay Weiss" : Hi Chris, I just did an upload test and it came out

RE: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

2.8.2 6 Perhaps that could help? Chris Am 28.04.20, 10:57 schrieb "Yishay Weiss" : I think it should be possible to do this in powershell, with: $password = Read-Host "Enter Password" -AsSecureString

RE: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

"). I have suggested using Wagon to upload individual folders -Alex On 4/27/20, 3:07 AM, "Christofer Dutz" wrote: Hi all, a week ago a new version of Wagon was released ... perhaps worth updating to 3.4.0? Chris Am 27.04.20, 11:58 sch

RE: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

>Don't know what the best workflow is until we try a few things. There are at >least two workflows: > >1) Upload the artifacts from CI and RM uploads only the asc files as you >suggested >2) RM uploads asc files to the CI server and everything gets uploaded to >staging from CI. How do you

RE: wagon:upload problems

apache.releases.https https://repository.apache.org/service/local/staging/deploy/maven2 From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Wednesday, April 29, 2020 5:08 PM To: dev@royale.apache.org<mailto:dev@royale.apache.org

RE: [royale-asjs] branch release/0.9.7 updated: add retry task if wagon fails

ice outages or extended unresponsiveness. Chris Am 29.04.20, 08:24 schrieb "Yishay Weiss" : I read that retry was only implemented in wagon 3.4.0 and up. So I replaced the pom.xml entry according to Alex’s suggestion but I’m getting [exec] [DEBUG] Resolving pl

wagon:upload problems

Even uploading the 534 asc files which are about 1k fails, so something is definitely weird. I think it might be repeating the upload for each project. For example, there’s only one zip.asc file, which is under

Optimize wagon:upload

Has anyone got this [1] to work? Didn’t for me. I got [exec] [ERROR] Failed to execute goal org.codehaus.mojo:wagon-maven-plugin:2.0.0:upload (default-cli) on project royale-framework-parent: Error handling resource : Wagon https does not support optimize upload -> [Help 1] [exec]

RE: wagon:upload problems

I suspect this might be related to recent maven profile changes not meshing well with the release script targets. I’ll see what I can dig up. From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Thursday, April 30, 2020 9:32 PM To: dev@royale.apache.org<mailto:dev@royale.apache.org

RE: wagon:upload problems

> > Alex, do you remember why you did this? Could it be related? From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Wednesday, April 29, 2020 5:11 PM To: dev@royale.apache.org<mailto:dev@royale.apache.org> Subject: RE: wagon:upload problems This is what _r

RE: wagon:upload problems

>I think it might be repeating the upload for each project. Upload happens 67 times [1] in a loop. That explains why even on the CI server after 5.5 hours it finally failed [2]. [1] https://paste.apache.org/zh3rj [2] [exec] [INFO] BUILD FAILURE [exec] [INFO]

RE: Optimize wagon:upload

pushing all of the binary bits. -Alex On 4/29/20, 7:18 AM, "Yishay Weiss" wrote: Has anyone got this [1] to work? Didn’t for me. I got [exec] [ERROR] Failed to execute goal org.codehaus.mojo:wagon-maven-plugin:2.0.0:upload (default-cli) on project royale-framework-

RE: Optimize wagon:upload

cating well with the staging server. Also, is it really "hanging" as in you have to kill maven or does it just fail at some point? And if it fails does it give you the option to continue where it failed? -Alex On 4/29/20, 10:05 AM, "Yishay Weiss" wrote: I put the flag

RE: wagon:upload problems

Subject: Re: wagon:upload problems I couldn't tell from the snippet of output that it was uploading the source-release.zip.asc again. I think it will visit each project. -Alex On 4/29/20, 7:08 AM, "Yishay Weiss" wrote: Even uploading the 534 asc files which are about 1k fails, so so

RE: wagon:upload problems

. Good luck, -Alex On 4/30/20, 11:34 AM, "Yishay Weiss" wrote: I suspect this might be related to recent maven profile changes not meshing well with the release script targets. I’ll see what I can dig up. From: Yishay Weiss<mailto:yishayj..

RE: wagon:upload problems

pload to see if it did the same thing? -Alex On 4/30/20, 2:26 PM, "Yishay Weiss" wrote: > My hunch is that specifying causes this loop. That wasn’t it. It completed one run and went on to the next run. I now realize that instead of waiting for it to finish and seeing whether

RE: wagon:upload problems

indows machine in the US vs your computer outside the US. Anyway, I think you can test locally with the .asc files and figure out the right params. Good luck, -Alex On 4/30/20, 11:34 AM, "Yishay Weiss" wrote: I suspect this might

RE: wagon:upload problems

>You're running the wagon:upload in a maven reactor. This means it's executed >once for every module in the reactor. Is this what’s changed? Did it not used to be run in a maven reactor? How else would I run it?

RE: wagon:upload problems

ly with the .asc files and figure out the right params. Good luck, -Alex On 4/30/20, 11:34 AM, "Yishay Weiss" wrote: I suspect this might be related to recent maven profile changes not meshing well with the release script targets. I’ll see what I can dig

RE: wagon:upload problems

Anyway, I think you can test locally with the .asc files and figure out the right params. Good luck, -Alex On 4/30/20, 11:34 AM, "Yishay Weiss" wrote: I suspect this might be related to recent maven profile cha

Modules in IE

Has anyone seen this work? To me it’s stuck in UIModuleUtils in COMPILE::JS protected function loadDepsHandler():void { // wait for other scripts to load if (window[moduleName] == null) { setTimeout(loadDepsHandler,

RE: Optimize wagon:upload

nternet push to staging. -Alex On 4/29/20, 10:36 AM, "Yishay Weiss" wrote: It ‘hangs’, no message. I can do the Git test, but I’d be really surprised if that failed. From: Alex Harui<mailto:aha...@adobe.com.INVALID> Sent: Wednesday, April 29, 2020 8:10 PM To: dev@

RE: wagon:upload problems

nt to > have them also build the SWF parts, you enable "witt-swf" profile and > nothing is built at all ... now you manually need to enable the > buildMainModules profile too to continue. That's just bad style. > > So if the maven folks have to live with thi

RE: wagon:upload problems

And if you adjust the "include" pattern back to "**/*.asc" then it should deploy all asc files. I would also expect this to be the root cause of the general deployment problems ... I could imagine if you deploy every artifact 160 times that Nexus might k

RE: wagon:upload problems

Yishay on how he spends his time on this and we should all be grateful for his patience and effort. IMO, the next thing to try may be specifying the “-pl royale-framework-parent" so we can at least see what it does. My 2 cents, -Alex On 5/1/20, 4:20 AM, "Yishay Weiss" wrote: T

RE: wagon:upload problems

, then they went away, presumably because I stopped streaming video while doing the upload, so maybe right now there is less data on the network you are using. Thanks, -Alex On 5/1/20, 9:58 PM, "Yishay Weiss" wrote: Ok, got it. I was indeed using 2 different connections for asjs and

RE: wagon:upload problems

r and royale-typedefs again (and add -N) HTH, -Alex On 5/1/20, 10:57 AM, "Yishay Weiss" wrote: It finished successfully after 1:40 using my slow cellular connection. Looks like infra in Israel is not the issue. I looked at the staging repo and it looks good to me

RE: wagon:upload problems

rk, but it also seems to have examples and manualtests this time around as well. But maybe they won't be there now that we're not uploading on every submodule. HTH, -Alex On 5/1/20, 9:53 AM, "Yishay Weiss" wrote: The whole thing. I wanted to review things on the staging repo

RE: Prioritize Release Jobs on CI

Tue, Apr 21, 2020 at 10:16 AM Yishay Weiss wrote: > > >Yishay, can you please confirm that your release jobs are running without > >being hindered by CI jobs? > > So far so good. Also, connection to CI server is much faster now, I’m > assuming it’s because of the extra ag

RE: Prioritize Release Jobs on CI

I don’t see any jobs configured to run on agent2. Not sure what I’m missing. From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Saturday, May 2, 2020 1:43 PM To: dev@royale.apache.org<mailto:dev@royale.apache.org> Subject: RE: Prioritize Release Jobs on CI Step 12 was block

RE: Prioritize Release Jobs on CI

Success email for step 12 was sent to dev but I’m not seeing it. I wonder if Jenkins mails are being filtered out. @Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>, could this be related to your correspondence with infra on Jenkins? From: Yishay Weiss<mailto:yishayj...@hotmail.

RE: Prioritize Release Jobs on CI

Piotr, ignore this for now, looks like email.txt is empty. From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Saturday, May 2, 2020 2:19 PM To: dev@royale.apache.org<mailto:dev@royale.apache.org>; Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com> Subject: RE: Prioritize

RE: Modules in IE

should make an appearance as the deps are loaded and evaluated. -Alex On 4/29/20, 8:19 PM, "Yishay Weiss" wrote: Yes, it works on Chrome and FF. window[this.modulename] is undefined. Didn’t check what happens in other browsers. From: Alex Harui<mailto:aha...@ad

Release Step 13 -Ant Build Failing

compile-swf: [echo] Compiling libs/Basic.swc [echo] ROYALE_HOME: c:\temp_asjs_ant\sources\royale-asjs [echo] ROYALE_SWF_COMPILER_HOME: c:\temp_asjs_ant\sources\royale-asjs [echo] ROYALE_COMPILER_HOME: c:\temp_asjs_ant\sources\royale-asjs/js [java] args: [java]

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

main,utils" Jenkinsfile:bat "mvn -U clean ${mavenGoal} ${mavenLocalRepo} -s C:\\.m2\\settings.xml -P -main,utils -Dcom.adobe.systemIdsForWhichTheTermsOfTheA dobeLicenseAgreementAreAccepted=3c9041a9,3872fc1e" README:mvn clean instal

Re: [DISCUSS] Discuss Release Apache Royale 0.9.7

most of the steps, that would be best, but will delay the release and I'm not sure it is worth it. We have online release notes to make corrections. I think it is mostly up to you though. -Alex On 5/3/20, 10:42 PM, "Yishay Weiss" wrote: I think we should continue the vote. If mor

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

.mvn folder exists in GitHub but not in SVN. Could that be related? From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Monday, May 4, 2020 6:40 PM To: dev@royale.apache.org<mailto:dev@royale.apache.org> Subject: RE: [DISCUSS] Discuss Release Apache Royale 0.9.7 Look

RE: [DISCUSS] Discuss Release Apache Royale 0.9.7

low message, But running the same command from the git repo C:\dev\flexjs\royale-compiler [release/0.9.7 =]> mvn clean install Does not fail. Any ideas? From: Yishay Weiss<mailto:yishayj...@hotmail.com> Sent: Monday, May 4, 2020 3:04 PM To: dev@royale.apache.org<mailto:dev@ro

<    1   2   3   4   5   6   7   8   9   10   >