Re: Possibility to control the prefix for source-map urls?

FYI, the Apache Royale CLI serves even the local app from a server https://apache.github.io/royale-docs/get-started/royale-cli On Sun, Sep 27, 2020 at 2:24 PM Piotr Zarzycki wrote: > Hi, > > This is nothing new that most of the JS frameworks currently are coming > with build in server, which is

Re: Build failed in Jenkins: royale-asjs-agent2 #234

Muppirala wrote: > Disabled! > > Thanks, > Om > > On Thu, Jun 11, 2020 at 12:31 PM OmPrakash Muppirala > wrote: > >> Agent 2 has several jobs which work fine: >> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/computer/agent2/ >> >> <htt

Re: Build failed in Jenkins: royale-asjs-agent2 #234

Disabled! Thanks, Om On Thu, Jun 11, 2020 at 12:31 PM OmPrakash Muppirala wrote: > Agent 2 has several jobs which work fine: > http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/computer/agent2/ > > <http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/computer/agent2/>

Re: Build failed in Jenkins: royale-asjs-agent2 #234

Agent 2 has several jobs which work fine: http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/computer/agent2/ The only one we haven't figured out end to end is the job: royale-asjs-agent2

Re: Implressions coming back ... Was: Hi and sorry for the mess ...

> > Am 29.05.20, 17:42 schrieb "OmPrakash Muppirala" : > > On Fri, May 29, 2020 at 7:12 AM Christofer Dutz < > christofer.d...@c-ware.de> > wrote: > > > Exactly ... > > > > understanding the Strands

Re: Implressions coming back ... Was: Hi and sorry for the mess ...

On Fri, May 29, 2020 at 7:12 AM Christofer Dutz wrote: > Exactly ... > > understanding the Strands and Beads is something I would mention. Still > haven't 100% understood this. > > Other thing is that I usually made heavy use of spark skinning ... so in > my past applications I used this quite a

Re: Separate mailing list for Jenkins notifications

gt;>>>> > > > > > >>>>>> > > > > And if we were a busier project, we might > >>>>>> have rules on > >>>>>> > > whether you > >>>>>&

Re: Build failed in Jenkins: royale-asjs #1209

I've tried a lot. For some reason the tests keep failing at a certain point. If the release rush is over, maybe we can move everything to agent1 to unblock this issue? On Sun, May 17, 2020, 8:18 AM Alex Harui wrote: > Without looking too much, I assumed this was because the jobs are split >

Re: Build failed in Jenkins: royale-asjs #1140

On Sat, Apr 25, 2020 at 1:50 PM Alex Harui wrote: > OK, I think the CI server is caught in the middle. The compiler is now > being built on agent2 and so this build doesn't have access to a recent > compiler. I guess I will turn off its scheduling. Eventually it will go > away when we fix the

Re: royale-asjs build error

ou need the mm.cfg in the appropriate place > with the appropriate settings. Try taking the one from my VM. > I had already copied the one in your VM. I copied the trust file from your VM as well. Trying again now. > > HTH, > -Alex > > On 4/24/20, 6:52 PM, "OmPraka

Re: royale-asjs build error

It definitely went farther along. Now it is breaking at something else. I will keep debugging this over the weekend. On Fri, Apr 24, 2020 at 6:51 PM OmPrakash Muppirala wrote: > > > On Fri, Apr 24, 2020 at 5:43 PM Alex Harui > wrote: > >> Om, the next difference between

Re: royale-asjs build error

ade was to change the drive letter for the workspace > from c: to C:. That was the only obvious difference between the successful > job on royale-asjs and the failing job on agent2 and that change made a > difference for Maven as well. > > HTH, > -Alex > > On 4/24

Re: royale-asjs build error

uot;Alex Harui" wrote: > > I made a change to agent2 and started royale-asjs-agent2. Let's see > if it gets past that point of failure. > > -Alex > > On 4/23/20, 10:34 PM, "OmPrakash Muppirala" > wrote: > > On Thu, Apr 23, 2020 at 10

Re: royale-asjs build error

o be passing now :-| > > Maybe you can add some debugging output to the royaleunit-ant-tasks. > > HTH, > -Alex > > On 4/23/20, 9:41 PM, "OmPrakash Muppirala" wrote: > > On Thu, Apr 23, 2020 at 8:55 PM Alex Harui > wrote: > > > We starte

Re: royale-asjs build error

indeed successful. Wonder what's causing the non-deterministic behavior. > -Alex > > On 4/23/20, 5:55 PM, "OmPrakash Muppirala" wrote: > > Hmm, I decided to execute royale-asjs on agent1 and it is failing with > a > similar but different error m

Re: royale-asjs build error

ack to see what it is trying to do. > org.apache.royale.test.ant.tasks.TestRun.run(TestRun.java:77) > > HTH, > -Alex > > On 4/22/20, 11:46 PM, "OmPrakash Muppirala" wrote: > > On Wed, Apr 22, 2020 at 12:36 AM Alex Harui > wrote: > > > I’m stoppin

Re: royale-asjs build error

k about trust info or sockets. Thanks, Om > > Good luck, > -Alex > > From: OmPrakash Muppirala > Reply-To: "dev@royale.apache.org" > Date: Wednesday, April 22, 2020 at 12:30 AM > To: Apache Royale Development > Subject: Re: royale-asjs build error > > > On

Re: Separate mailing list for Jenkins notifications

INFRA-15722 > > > > > > > > > > > > > > > > > > On 4/20/20, 2:45 PM, "Piotr Zarzycki" < > > > > piotrzarzyck...@gmail.com> > > > > > wrote: > &

Re: royale-asjs build error

On Tue, Apr 21, 2020 at 9:01 PM Alex Harui wrote: > Flash Player Trust files? > > I copied these two files from he master Jenkins server. It still seems to fail on the same error: [image: image.png] > On 4/21/20, 5:08 PM, "OmPrakash Muppirala" wrote: > >

royale-asjs build error

This is part of my port of certain jobs from Master to Agent2 on the Jenkins CI server. I am seeing this error. Any idea what could be going wrong here? BUILD FAILEDc:\jenkins\workspace\royale-asjs\build.xml:667: The following error occurred while executing this line:

Re: Prioritize Release Jobs on CI

the extra agent. Thanks for this. > That's good to know. Thanks for the confirmation! > > On Mon, Apr 20, 2020 at 12:05 AM OmPrakash Muppirala > > wrote: > > > > > On Mon, Apr 20, 2020 at 12:01 AM Alex Harui > > wrote: > > > >> I see compiler-jx/

Re: Prioritize Release Jobs on CI

ing > the release job). > > -Alex > > On 4/20/20, 10:53 PM, "OmPrakash Muppirala" > wrote: > > Update - royale-asjs_jsonly successfully build on my agent VM. > > Right now, we have 3 jobs running on this VM: >

Re: Prioritize Release Jobs on CI

On Mon, Apr 20, 2020 at 11:08 PM OmPrakash Muppirala wrote: > I see. I was waiting for the build to be fixed before moving it over. Or > have folks run into a dead-end trying to figure out what is wrong with > royale-asjs ? > Hah! Never mind. Looks like royale-asjs is building

Re: Prioritize Release Jobs on CI

without being hindered by CI jobs? Thanks, Om On Mon, Apr 20, 2020 at 12:05 AM OmPrakash Muppirala wrote: > > On Mon, Apr 20, 2020 at 12:01 AM Alex Harui > wrote: > >> I see compiler-jx/lib in the Workspace for royale-compiler on my VM. If >> you are talking about

Re: Separate mailing list for Jenkins notifications

We already have issues@ and commits@. Can we redirect the emails to one of the lists? On Mon, Apr 20, 2020 at 11:54 AM Alex Harui wrote: > IMO, if we do create a new list, all committers must be subscribed. > > My 2 cents, > -Alex > > On 4/20/20, 1:53 AM, "Piotr Zarzycki" wrote: > > Hi

Re: Build failed in Jenkins: royale-asjs_jsonly #1335

This is on the Agent2 virtual machine I am in the process of setting up. I will fix this soon. Please check the `Prioritize Release Jobs on CI` thread where I am posting details on my progress with this. Thanks, Om On Mon, Apr 20, 2020 at 7:57 AM Piotr Zarzycki wrote: > Maybe it's just some

Re: Prioritize Release Jobs on CI

royale-compiler seems to have fixed that problem. Now royale-typedefs passes as well! Next up royale-asjs_jsonly... > I'm done for tonight. Good luck, > -Alex > > On 4/19/20, 11:50 PM, "OmPrakash Muppirala" wrote: > > On Sun, Apr 19, 2020 at 11:37 PM Alex Harui

Re: Prioritize Release Jobs on CI

I've never found enough > time and energy to try to make changes like that since most of us do have > all of the folders as siblings. > > HTH, > -Alex > > On 4/19/20, 11:31 PM, "OmPrakash Muppirala" wrote: > > I am now getting this error on royale-typedefs build:

Re: Prioritize Release Jobs on CI

OmPrakash Muppirala wrote: > On Sun, Apr 19, 2020 at 11:08 PM Alex Harui > wrote: > >> Congratulations! But does that mean that JAVA_HOME is pointing at a JRE >> instead of a JDK? If you have other issues that might be a factor. >> > > Yeah, I messed up initially

Re: Prioritize Release Jobs on CI

corrected it. But for some reason Ant still thinks that JAVA_HOME is the jre directory. I don't know how to fix this, hence the hack :-| > > HTH, > -Alex > > On 4/19/20, 10:50 PM, "OmPrakash Muppirala" wrote: > > I copied tools.jar from jdk/lib to the jre/lib. Th

Re: Prioritize Release Jobs on CI

I copied tools.jar from jdk/lib to the jre/lib. That seems to have fixed the issue. We now have a successful build of the royale-compiler on the new Agent machine!! On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala wrote: > Restart dint help. Although Serkan's reply made me look at

Re: Prioritize Release Jobs on CI

mp;& exit %%ERRORLEVEL%%" Unable to locate tools.jar. Expected to find it in C:\Program Files\Java\jre1.8.0_251\lib\tools.jar I am pretty sure this is related to this issue. On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala wrote: > > > On Sun, Apr 19, 2020 at 10:15 PM Alex Harui &

Re: Prioritize Release Jobs on CI

On Sun, Apr 19, 2020 at 10:05 PM serkan wrote: > It should be related with the shell which ant is executed in. > > It seems like you should set PATH for that shell. > Thanks for the reply! I'm not sure how I would do that? > > > 20.04.2020 07:36 tarihinde OmPrakash Mup

Re: Prioritize Release Jobs on CI

g. I will give the rebooting of the VM a shot . Thanks, Om > -Alex > > On 4/19/20, 10:01 PM, "OmPrakash Muppirala" wrote: > > On Sun, Apr 19, 2020 at 9:55 PM Alex Harui > wrote: > > > Should be here: > > > > > https://nam04.safelin

Re: Prioritize Release Jobs on CI

c is what is failing. > > > HTH, > -Alex > > From: OmPrakash Muppirala > Reply-To: "dev@royale.apache.org" > Date: Sunday, April 19, 2020 at 9:37 PM > To: Apache Royale Development > Subject: Re: Prioritize Release Jobs on CI > > I'm a bit stumpe

Re: Prioritize Release Jobs on CI

Google Closure Library I am not sure how this executable call works without the full path. I checked the env variables, I do have both the git/bin and git/cmd directory in the PATH: [image: image.png] What am I missing? Thanks, Om On Sat, Apr 18, 2020 at 11:54 PM OmPrakash Muppirala wr

Re: Prioritize Release Jobs on CI

building on my VM, we can figure out how to divide the load between the master and agent. Thanks, Om On Sat, Apr 18, 2020 at 8:59 AM OmPrakash Muppirala wrote: > We could achieve the same by creating a new agent (separate vm) and > attaching it as a slave to the current Jenkins server. > >

Re: Prioritize Release Jobs on CI

currently the plan? > > -Alex > > On 4/18/20, 12:43 AM, "OmPrakash Muppirala" wrote: > > Makes sense to me. I will set parallel executors back to 1. > > And start working on a new Jenkins instance. > > Thanks, > Om > > > On Sat

Re: Prioritize Release Jobs on CI

e trying to run tests with the shared Flash Player > Debugger, for > > example, you won't get consistent results. > > > > -Alex > > > > On 4/17/20, 11:23 PM, "OmPrakash Muppirala" > wrote: > > > > I just re

Re: Prioritize Release Jobs on CI

d jobs took forever. If > two jobs are trying to run tests with the shared Flash Player Debugger, for > example, you won't get consistent results. > > -Alex > > On 4/17/20, 11:23 PM, "OmPrakash Muppirala" wrote: > > I just realized that we have only one

Re: Prioritize Release Jobs on CI

oritize Release Jobs on CI > > Alex, > > I believe this is your personal Azure subscription right? Any chance > I can > get access to it so I can try to copy the image out the machine and > redeploy it somewhere else? > > Thanks, > Om &g

Re: Prioritize Release Jobs on CI

ttps://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse > > From: 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: Priorit

Re: Prioritize Release Jobs on CI

call and do a screen share so I can walk you through it. Let me know when a good time is for you is? Thanks, Om > > -Alex > > On 4/13/20, 12:34 AM, "OmPrakash Muppirala" wrote: > > You wont have to share your MSDN credentials. You can add me as a > user in

Re: Prioritize Release Jobs on CI

Alex, I believe this is your personal Azure subscription right? Any chance I can get access to it so I can try to copy the image out the machine and redeploy it somewhere else? Thanks, Om On Sun, Apr 12, 2020 at 6:18 PM OmPrakash Muppirala wrote: > I can help set this up on Azure. Give

Re: Prioritize Release Jobs on CI

I can help set this up on Azure. Give me some time to work out the details? Thanks, Om On Sun, Apr 12, 2020, 11:49 AM Harbs wrote: > OK. Good to know. > > > On Apr 12, 2020, at 9:45 PM, Alex Harui > wrote: > > > > FWIW, I just looked and the longest job in the release steps so far is 8 >

Re: Releasing: Finally giving up

> > > > > We are passing in the timestamp (slightly different format, however still > correct as we also adjusted the format-string). When building locally, the > timestamp is exactly as the timestamp string tells the compiler. On the CI > however there’s this 60 minute offset. I have explicitly

Re: Reporting back (Was: Re: About release 0.9.7 and how to fix and streamline the process)

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7Caaac0c3693294c72c62608d7cb614ad0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637201491043736972sdata=p3GFZuKOAdosdIUUK6YQ7pyrQLAGCrdulrcyfAHUq%2FE%3Dreserved=0 > > > > > On Wed, Mar

Re: Reporting back (Was: Re: About release 0.9.7 and how to fix and streamline the process)

Carlos, Chris, There is nothing stopping you from building something from scratch. There is no need to convince anyone. Please start committing. I think Alex and others have made their points clearly. I don't see a reason to continue rehashing the same points over and over. As long as the

Re: About release 0.9.7 and how to fix and streamline the process

My 2 cents: I don't think we need to go back to the Ant vs Maven discussion. If the Maven build/stage/release scripts works flawlessly, an Ant task can simply call it. There is no reason both cannot be worked on continuously. In the same way, if Maven users want, they can call Ant scripts as

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

I'm sorry I missed this thread from a while ago. I tried Alex's suggested fix on my current npm installation, but I am still getting the same error. Here is the pastbein: https://pastebin.com/raw/t4v8CWYe Maybe I am doing it wrong? Thanks, Om On Mon, Oct 14, 2019 at 10:31 AM Alex Harui

Re: SWCs directory?

Does it make sense to push out a new release with those changes? Thanks, Om > > -- > Josh Tynjala > Bowler Hat LLC <https://bowlerhat.dev> > > > On Sun, Feb 2, 2020 at 10:34 AM OmPrakash Muppirala > wrote: > > > The latest npm installation shows all the framewo

Re: SWCs directory?

rs as before. > > > On Feb 2, 2020, at 10:44 PM, Harbs wrote: > > > > Set targets to JSRoyale > > > > In asconfig: > > "targets": ["JSRoyale”], > > > > In ant: > > > > > > Not sure where to stick that in in yo

Re: SWCs directory?

nes. > > Does that make sense? > > > On Feb 2, 2020, at 8:34 PM, OmPrakash Muppirala > wrote: > > > > The latest npm installation shows all the framework swcs here: > > > > > /Users/om/.nvm/versions/node/v8.14.1/lib/node_modules/@apache

SWCs directory?

The latest npm installation shows all the framework swcs here: /Users/om/.nvm/versions/node/v8.14.1/lib/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/js/libs But as per

Re: Jewel TodoMVC Example

Carlos, This is simply amazing. Great job on porting the standard TodoMVC app to Royale! Om On Thu, Jan 30, 2020 at 2:27 PM Carlos Rovira wrote: > Hi All, > > just upload a first version of TodoMVC to the website. It implements all > functionality, with Routing and Local Storage included. >

Re: Welcome Greg Dove to Apache Royale's PMC

Welcome Greg! I am really glad you accepted :-D Thanks, Om On Tue, Oct 29, 2019 at 1:01 PM Greg Dove wrote: > > Thanks everyone, much appreciated! > > > On Wed, Oct 30, 2019 at 3:56 AM Josh Tynjala > wrote: > >> Welcome, Greg! >> >> -- >> Josh Tynjala >> Bowler Hat LLC

Welcome Andrew Wetmore to Apache Royale's PMC

It is with great pleasure that I announce that the Apache Royale PMC members have voted in Andrew Wetmore to the PMC. Please join us in welcoming him. This is a recognition of Andrew's great work in helping out with Apache Royale's documentation among other things. Regards, Om (On behalf of

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

On Tue, Oct 1, 2019 at 8:32 AM Alex Harui wrote: > The releasecandidate.xml script will tell you what to do on > repository.apache.org to release the Maven stuff, and release the npm > stuff as well. The whole point of these scripts is so you don't have to > ask for help. If you do end up

Re: [royale-asjs] branch release/0.9.6 updated: Update RELEASE_NOTES.md

This can always go in the next release :-) Thanks, Om On Mon, Sep 16, 2019 at 4:32 AM Piotr Zarzycki wrote: > I know Andrew. No problem ! :) > > pon., 16 wrz 2019 o 12:39 Andrew Wetmore napisał(a): > > > The hurricane and is aftermath slowed me down. Anyhow all my edits were > > minor. > > >

Re: Discuss of release steps preparation

I tested the installation (beta 10) and the subsequent steps using royale-cli and everything seems to be working. Thanks for all the fixes, Alex. Regards, Om On Fri, Sep 13, 2019 at 10:33 AM Greg Dove wrote: > Oh thanks, Josh! I will do that later today. > > > On Sat, Sep 14, 2019 at 5:32 AM

Re: Discuss of release steps preparation

Let me do some more testing of the npm flow pls. Thanks, Om On Wed, Sep 11, 2019, 7:04 PM Alex Harui wrote: > I may have fixed the NPM issues. You can gamble and start the RC now or > wait until folks do more testing. > > -Alex > > On 9/9/19, 10:23 PM, "Piotr Zarzycki" wrote: > > Ok I

Re: Testing the npm install error fixes

he DMG. I have tested that setup on my Mac as well. Although I dont have objections if you want to change that. Thanks, Om > Thanks, > -Alex > > On 9/10/19, 7:29 PM, "Alex Harui" wrote: > > I think I got it working... > > On 9/10/19, 5:18 PM, "

Re: Testing the npm install error fixes

/download_dependencies.js` > > npm ERR! Exit status 1 > > npm ERR! > > npm ERR! Failed at the @apache-royale/royale-js-swf@0.9.6-beta0 > > postinstall script. > > npm ERR! This is probably not a problem with npm. There is likely

Re: Testing the npm install error fixes

mand line. The command line is already in the error log above this > thread. There's something like this: > > macbookpro:~ carlosrovira$ npm i @apache-royale/royale-js-swf@0.9.6-beta0 > -g > > best > > C. > > > El lun., 9 sept. 2019 a las 17:43, OmPrakash Muppirala

Re: Testing the npm install error fixes

Huh? Did you use the - g switch? Your path indicates that you probably did not.. On Mon, Sep 9, 2019, 7:10 AM Carlos Rovira wrote: > Hi Om, > > the path is: "*/npm/js-swf/dependencies/*" > > HTH > Carlos > > El vie., 6 sept. 2019 a las 19:41, OmPrakash M

Re: Testing the npm install error fixes

che.org/p/pomzf > > and dependencies.js > > https://paste.apache.org/p/6nu70 > > > HTH > > Carlos > > > > > > > El jue., 5 sept. 2019 a las 18:32, OmPrakash Muppirala (< > bigosma...@apache.org>) escribió: > > > If you have to use sudo

Re: Discuss of release steps preparation

On Fri, Sep 6, 2019 at 3:59 AM Carlos Rovira wrote: > Hi, > > maybe is not so bad to end this 0.9.6 manually, since there was many > progress in that front. Does not need necessarily be "all or nothing". Or > 100% success. > Releasing now 0.9.6 can make lower the stress a bit and make a the

Re: Testing the npm install error fixes

-g on MacOS you need sudo. However, I don't think > that's the issue here. > I think Carlos should post his: > - dependencies/download_dependencies.js` > - /Users/carlosrovira/.npm/_logs/2019-09-05T09_39_50_359Z-debug.log > > HTH, > -Alex > > On 9/5/19, 7:28 AM

Re: Testing the npm install error fixes

And oh, what is your node version? On Thu, Sep 5, 2019, 7:27 AM OmPrakash Muppirala wrote: > We should never have to install any npm package with sudo. > > I will dig deeper into this and see what I can do. > > Thanks for testing! > > Om > > > On Thu, Sep 5, 2019,

Re: Testing the npm install error fixes

ad (internal/modules/cjs/loader.js:506:25) > > > > > >at Function.Module.runMain (internal/modules/cjs/loader.js:741:12) > > > > > >at startup (internal/bootstrap/node.js:285:19) > > > > > >at bootstrapNodeJSCore (internal/bootstrap/node.js:73

Re: Testing the npm install error fixes

t; that I must go to some example project like Tour de Jewel and try to > compile in terminal with mxmlc right? Can you provide a command line to use > for test for example that particular case? > > Thanks! > > > > El mar., 3 sept. 2019 a las 19:52, OmPrakash Muppirala (< > b

Re: Testing the npm install error fixes

:52 PM OmPrakash Muppirala wrote: > Just a heads up, I will be doing some test publishes of the royale npm > package. I will be using the version number: 0.9.6.beta.1 (0.9.6.beta.2, > etc if needed) > > These fixes are related to these tickets: > > https://github.com/apache/r

Re: Successfully published @apache-royale/royale-js-swf@0.9.6-beta0

ing commit: >> https://github.com/apache/royale-asjs/commit/f25d30ae3730ca023b97a17211d51f8594d0beee >> >> >> Om if you put something more in the next days unfortunately I won't >> include it, unless RC1 will fail in voting. >> >> wt., 3 wrz 2019 o 18:45 OmPra

Testing the npm install error fixes

Just a heads up, I will be doing some test publishes of the royale npm package. I will be using the version number: 0.9.6.beta.1 (0.9.6.beta.2, etc if needed) These fixes are related to these tickets: https://github.com/apache/royale-asjs/issues/428

Re: Website - create Showcase section

If we can mimic how the Flex showcase works, that would be a good starting point. http://flex.apache.org/community-showcase.html Thanks, Om On Wed, Jul 24, 2019, 9:51 AM Yishay Weiss wrote: > Sounds good, thanks. > > > > > From: Carlos Rovira > Sent:

Re: Embedded Assets (was Re: AIR and Royale)

In recent applications using React/Webpack, I have seen defaults of using base64 embedding of files less than 10k in size. I guess the tradeoff is in between firing off several http requests for small files vs embedding them is a less efficient format. I think a similar strategy would work for

Re: Let's bump Royale version to 1.0

On Fri, Apr 26, 2019 at 7:37 PM Dany Dhondt wrote: > I’m all for buikding a knowledge base in Stack Overflow! The mailing list > should only be used for developing Royale. Questions about using Royale > should go to SO > > The competitors of Royale are React, Vue, Angular, ... > Lots of

Re: 0.9.6 Release

mages available but that requires host machine to be windows. Which defeats the purpose of using docker. > -Alex > > On 3/8/19, 8:41 AM, "OmPrakash Muppirala" wrote: > > A quick update from my side regarding the docker experiments: > > The biggest block I ha

Re: 0.9.6 Release

other server. I'm not going to involve Docker at > this > > point. My main goal is just to see if I can create a workflow of many > > discrete steps that isn't horribly painful. Once we see what these steps > > turn out to be, then we can worry about server portability of t

Re: 0.9.6 Release

Alex, Just to be clear, I am following the steps from here to try and setup a docker container. https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes Is this doc up to date? Thanks, Om On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala wrote: > One approach is to have each s

Re: 0.9.6 Release

s or replace Flash with AIR. > > > > Thanks, > > -Alex > > > > On 2/6/19, 10:54 AM, "Carlos Rovira" > wrote: > > > >Hi Om, that would be great! waiting for your experience with a > that! :) > >

Re: 0.9.6 Release

think we should try to avoid that scenario, and branches are the best > way. If we do this way, we'll benefit of more reliable develop branch. > > Thanks and good to know of this plan :) > > Carlos > > > El mar., 5 feb. 2019 a las 23:19, Harbs (

Re: 0.9.6 Release

I was wondering if we can use docker images to setup and seal the RM environment. Then other RMs simply need to run the image locally and run the release scripts. Might be easier. If folks like this plan, I can try to put something together. Thanks, Om On Tue, Feb 5, 2019 at 1:40 PM Harbs

Re: BevelFilter

It seems like using the feConvolveMatrix lets you achieve bevel (and other kinds of effects) The basic approach is described here: https://vanseodesign.com/web-design/svg-filter-primitives-feconvolvematrix/ This article points to this one: http://setosa.io/ev/image-kernels/ where you can

Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

> You may be able to use 0.9.5-next. Technically, in semver, the dash is > supposed to be used for prerelease builds, but I don't think that it's > enforced. This should still be considered a different version number than > 0.9.5, I think, and no special install command is required. >

Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

sion number than > 0.9.5, I think, and no special install command is required. > > You are right, that makes sense! > - Josh > > On 2018/11/19 19:50:26, OmPrakash Muppirala wrote: > > Okay, I unpublished 0.9.5 and published 0.9.4. Looks like we are okay &g

Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

On Mon, Nov 19, 2018 at 11:36 AM Alex Harui wrote: > IMO, if we aren't going to use 0.9.5, no need to unpublish it, just > publish a 0.9.4 for now and we'll skip 0.9.5 > > My 2 cents, > -Alex > > On 11/19/18, 10:57 AM, "OmPrakash Muppirala" > wrote: > >

Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

o publish the bits as 0.9.4 if they have time. I > don't want to take the time to do that. I will bump the dev branches to > 0.9.6 this week sometime. Our next release will have to be 0.9.6, just > like we skipped 0.9.3. > > -Alex > > On 11/19/18, 7:25 AM, &qu

Re: NPM (was Re: [VOTE] Release Apache Royale 0.9.4 RC2)

Yeah, there is no way to unpublish it. I'm guessing that the the version number get bumped twice? On Mon, Nov 19, 2018 at 2:18 AM Harbs wrote: > Ouch. Am I correct in assuming that there’s no way to “unpublish” 0.9.5? > > Why did this happen again? > > Harbs > > > On Nov 19, 2018, at 2:54 AM,

Re: [VOTE] Release Apache Royale 0.9.4 RC2

+1 (binding) Package https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/apache-royale-0.9.4-src.tar.gz Java 1.8 OS: Mac OS X x86_64 10.13.6 Source kit signatures match: y Source kit builds: y README is ok: y RELEASE_NOTES is ok: y NOTICE is ok: y LICENSE is ok: y No unapproved

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

> -Alex > > On 11/16/18, 11:29 AM, "OmPrakash Muppirala" > wrote: > > Hmm interesting. I am getting this output from the approval script: > > approve: > > > -1 > > Package > > https://na01.safelinks.protection.outlook.com/?url

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

Hmm interesting. I am getting this output from the approval script: approve: -1 Package https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/apache-royale-0.9.4-src.tar.gz Java 1.8 OS: Mac OS X x86_64 10.13.6 Source kit signatures match: y Source kit builds: y README is ok: y

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

ng issue is upload/download issues. > Thanks for getting the scripts to this shape! Regards, Om > > Thanks, > -Alex > > On 11/14/18, 10:36 PM, "OmPrakash Muppirala" > wrote: > > Personally, I am not sure why we are uploading stuff to maven central > a

Re: Lets talk a bit about the release process (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2)

Personally, I am not sure why we are uploading stuff to maven central as part of the RC process. Can we simply bundle the source files and create a release candidate? Folks who want to test maven can run the maven scripts locally which would copy stuff to the local .m2 repo instead. That way we

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

es of uploading stuff. I dont do this kind of uploading for my regular work, so that is probably I have never hit this issue before. I still think that looking into the 'resume-from' directive in maven is worthwhile. Thanks, Om > > -Alex > > On 10/3/18, 2:11 PM, "OmPrakash Mu

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

uot; Java(TM) SE Runtime Environment (build 1.8.0_181-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) > > -Alex > > On 10/4/18, 1:14 AM, "OmPrakash Muppirala" wrote: > > DSL via AT :-) > Although this morning was a different connection

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

gt; Harbs > > > > > On Oct 4, 2018, at 11:09 AM, Piotr Zarzycki < > piotrzarzyck...@gmail.com> > > wrote: > > > > > > Neverending story ;) What's your internet connection actually? > > > > > > On Thu, Oct 4, 2018, 10:

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

DSL via AT :-) Although this morning was a different connection (at work) On Thu, Oct 4, 2018 at 1:09 AM Piotr Zarzycki wrote: > Neverending story ;) What's your internet connection actually? > > On Thu, Oct 4, 2018, 10:04 AM OmPrakash Muppirala > wrote: > > > Hmm, failed

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

NFO] On Wed, Oct 3, 2018 at 2:10 PM OmPrakash Muppirala wrote: > > > On Wed, Oct 3, 2018 at 2:02 PM Alex Harui > wrote: > >> Hi Om, >> >> Does anything deploy, or is that the first thing that

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

> > There should be Ant targets for starting only on royale-asjs if > royale-compiler and royale=typedefs worked ok. > > HTH, > -Alex > > On 10/3/18, 11:58 AM, "OmPrakash Muppirala" wrote: > > Another suggestion I have is - can we do all the pushes to remote a

  1   2   3   >