Re: 0.9.3 Release

It might be that we decide that DataGroup does belong in Core with a “core” package path, but I don’t even think there’s a list of classes which were changed. Maybe there are too many. Maybe there are others which should be changed. Maybe we’ll decide that it’s not worth it to change any. I

Re: 0.9.3 Release

It's not about the minor changes in his app in my opinion. In the result of the discussion it may end up that you will revert everything and solution will be completely different. What will be the experience of the created app on the user sight ? 2018-05-17 10:05 GMT+02:00 Carlos Rovira

Re: 0.9.3 Release

Hi Harbs, that was returned to the old way, actually we have the same than before refactor: import org.apache.royale.html.Group; public class NodeElementBase extends Group Maybe the problem is that we don't have any example of ButtonBar in examples? and thus I was not aware of that concrete

Re: 0.9.3 Release

I believe it’s 88cffe995de541584024cbf38eb016acfc677f98. There are some later commits that we might want to apply to the 0.9.3 branch, but that shouldn’t be a big deal. If it’s easier, you can also branch off feature/revert-refactor. That takes 88cffe9 and has a few commits applied to it.

Re: 0.9.3 Release

I do mean let's have it radical changes, but not partially as it is now. It looks like discussion may bring us some solution. Thanks, Piotr On Thu, May 17, 2018, 8:50 AM Harbs wrote: > Having trouble getting this email to “take”. Trying a paste link instead... > > It

Re: 0.9.3 Release

Having trouble getting this email to “take”... It looks like it does have issues. I just pulled the 0.9.3 branch. I get a lot of these warnings when I compile the framework: [java]

Re: 0.9.3 Release

F231=02%7C01%7Caharui%40adobe.com%7C148581f8c5044ef904ff08d5bb5d5ed2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636620932105097613=VOKTeSnHdtVN2KmYI%2FvNfS7u%2BrgcnlcIJf%2BhhKyG3RE%3D=0 > < > >> > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%

Re: 0.9.3 Release

8d5bb5d5ed2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636620932105097613=VOKTeSnHdtVN2KmYI%2FvNfS7u%2BrgcnlcIJf%2BhhKyG3RE%3D=0> >>> >>> Thanks, >>> Om >>> >>> >>>> >>>> >>>> Thanks, >>>>

Re: 0.9.3 Release

different *swcs* (I really need to turn off auto-correct…) > On May 16, 2018, at 10:33 PM, Harbs wrote: > > different secs

Re: 0.9.3 Release

ould be fine. It looks like the new version of >>>>> maven-scm will be released imminently. Let's wait for it :-) >>>>> >>>>> If you are going to do the release, can you make sure that you create >>>>> upgrade to the latest versions of nod

Re: 0.9.3 Release

hould hopefully fix: >>> https://github.com/apache/royale-asjs/issues/231 < >> https://github.com/apache/royale-asjs/issues/231> >>> >>> Thanks, >>> Om >>> >>> >>>> >>>> >>>> Thanks, >>>

Re: 0.9.3 Release

://github.com/apache/royale-asjs/issues/231 < > https://github.com/apache/royale-asjs/issues/231> > > > > Thanks, > > Om > > > > > >> > >> > >> Thanks, > >> > >> -Alex > >> > >> > >

Re: 0.9.3 Release

half of OmPrakash > Muppirala <bigosma...@gmail.com> > *Date: *Monday, May 7, 2018 at 11:23 AM > > *To: *Alex Harui <aha...@adobe.com> > *Cc: *"dev@royale.apache.org" <dev@royale.apache.org> > *Subject: *Re: 0.9.3 Release > > > > I was running this co

Re: 0.9.3 Release

> Date: Monday, May 7, 2018 at 11:23 AM To: Alex Harui <aha...@adobe.com> Cc: "dev@royale.apache.org" <dev@royale.apache.org> Subject: Re: 0.9.3 Release I was running this command: > ant -f releasecandidate.xml "-Drelease.version=0.9.3" -Drc=1 maven > -Db

Re: 0.9.3 Release

lem and anything else? > > Thanks, > -Alex > > From: OmPrakash Muppirala <bigosma...@gmail.com> > Date: Friday, May 4, 2018 at 2:00 PM > To: Alex Harui <aha...@adobe.com> > Cc: "dev@royale.apache.org" <dev@royale.apache.org> >

Re: 0.9.3 Release

*Alex Harui <aha...@adobe.com> > *Cc: *"dev@royale.apache.org" <dev@royale.apache.org> > *Subject: *Re: 0.9.3 Release > > > > I have tried to get this working for the last several days. I think i am > ready to give up on this. I don't want to mess things up a

Re: 0.9.3 Release

? -Alex From: "omup...@gmail.com" <omup...@gmail.com> on behalf of OmPrakash Muppirala <bigosma...@gmail.com> Date: Friday, May 4, 2018 at 12:04 PM To: Alex Harui <aha...@adobe.com> Cc: "dev@royale.apache.org" <dev@royale.apache.org> Subject: Re: 0.9

Re: 0.9.3 Release

ate: *Monday, April 30, 2018 at 1:15 AM > *To: *"dev@royale.apache.org" <dev@royale.apache.org> > *Cc: *Alex Harui <aha...@adobe.com> > *Subject: *Re: 0.9.3 Release > > > > The first step went through fine. I am getting this error on the second > step. I

Re: 0.9.3 Release

rakash Muppirala <bigosma...@gmail.com> Date: Monday, April 30, 2018 at 1:15 AM To: "dev@royale.apache.org" <dev@royale.apache.org> Cc: Alex Harui <aha...@adobe.com> Subject: Re: 0.9.3 Release The first step went through fine. I am getting this error on the second step. I

Re: 0.9.3 Release

ppirala <bigosma...@gmail.com> > *Date: *Sunday, April 29, 2018 at 5:40 PM > *To: *Alex Harui <aha...@adobe.com> > *Subject: *Fwd: 0.9.3 Release > > > > > > -- Forwarded message - > From: OmPrakash Muppirala <bigosma...@gmail.com>

Re: 0.9.3 Release

Royale isn't really going to do [Last Call] like Flex did. We hope to make the release process quick enough that it doesn't really matter whether something gets into the release or not. The next release should be a few weeks away. So, go for it! -Alex On 4/27/18, 10:51 PM,

Re: 0.9.3 Release

Okay, I have started looking into this. Should I start a new [Last Call] thread or is this it? Thanks, Om On Wed, Apr 25, 2018 at 12:43 AM, Alex Harui wrote: > Yep, that's what we have for you to work with. I expect there will be > things missing or needing

Re: 0.9.3 Release

On Wed, Apr 25, 2018 at 12:19 AM, Piotr Zarzycki wrote: > Om, > > I believe this is some starting point [1] > > [1] https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes > > Piotr > That link looks great. Thanks! > > 2018-04-25 9:12 GMT+02:00 OmPrakash

Re: 0.9.3 Release

Okay that works. 0.9.3 gets installed and it works fine with VSCode. Can you point me to where I need to start with the release process? I am going to try and get some work done on my ECharts + Jewel theme integration in the meantime. Thanks, Om On Tue, Apr 24, 2018 at 12:59 PM, Alex Harui

Re: 0.9.3 Release

I think I have this working correctly. I also fixed up a bunch of other issues. Wait until the CI server catches up and try it again to verify. If it does, then I think you are all clear to start the release. HTH, -Alex On 4/24/18, 9:28 AM, "Alex Harui" wrote:

Re: 0.9.3 Release

On 4/24/18, 8:56 AM, "OmPrakash Muppirala" wrote: On Tue, Apr 24, 2018, 12:58 AM Alex Harui wrote: > I think that's been broken forever. But I don't want to take the time to > find out. > > Try this one:

Re: 0.9.3 Release

On Tue, Apr 24, 2018, 12:58 AM Alex Harui wrote: > I think that's been broken forever. But I don't want to take the time to > find out. > > Try this one: >

Re: 0.9.3 Release

I think that's been broken forever. But I don't want to take the time to find out. Try this one: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/lastSuccessfulBuild/artifact/out/apache-royale-0.9.3-bin-js.tar.gz If that works, that will confirm the problem, which is that

Re: 0.9.3 Release

Still seeing the same issue. Screenshot here: https://snag.gy/jBxIZs.jpg Command used to install: npm install http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/artifact/out/apache-royale-0.9.3-bin-js.tar.gz -g Expected: Install js-only Royale SDK,

Re: 0.9.3 Release

If you are still having problems, please be more specific about what you mean by "build" and what js-swf artifacts are being pulled down. Thanks, -Alex On 4/23/18, 9:29 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote:

Re: 0.9.3 Release

a. The js-only build was pulling down the js-swf artifacts b. It was not recognized by Visual Studio as a valid sdk I'm guessing these two are related. This was right after Carlos published his new List component. Will give it a shot soon and let you know. Thanks, Om On Mon, Apr 23, 2018 at

Re: 0.9.3 Release

Hi Om, AIUI, your issue is that the nightly JS-Only build wasn't a valid Flex SDK. I just tried the nightly, and FB said it was a valid SDK. I guess I will try bringing it down via NPM next. When was the last time you tried this? -Alex On 4/23/18, 8:09 PM, "omup...@gmail.com on behalf of

Re: 0.9.3 Release

Alex, Any updates on the build issues? Thanks, Om On Fri, Apr 20, 2018 at 10:56 PM, Carlos Rovira wrote: > Hi my main concern is that all theme projects needs additional 3' of build, > and that use to be only first time, since people doesn't need to rebuild it >

Re: 0.9.3 Release

Hi my main concern is that all theme projects needs additional 3' of build, and that use to be only first time, since people doesn't need to rebuild it (think that themes now are just a single .CSS file bundled in a .SWC. And this is more for people like us that are building royale. Folks working

Re: 0.9.3 Release

OK. I will have limited time this weekend but will look into build issues and give an all clear after verifying the nightly builds and fix the Maven build. I don't have any deadline in mind for the release. I'd rather prove that someone else can use the release scripts to cut a release.

Re: 0.9.3 Release

On Fri, Apr 20, 2018 at 9:33 AM, Alex Harui wrote: > Jewel is in the develop branch and some updates are in MXRoyale that I > will merge to develop after I finish reviewing Alina's PRs from last night. > > What problems are you having with the nightly? We should iron

Re: 0.9.3 Release

I merged MXRoyale to develop. It built in Ant and Maven for me. I didn't build examples though. Thanks, -Alex On 4/20/18, 9:59 AM, "Alex Harui" wrote: If we don't separate themes from the build for this release, it isn't that big a deal, IMO. But if we do

Re: 0.9.3 Release

If we don't separate themes from the build for this release, it isn't that big a deal, IMO. But if we do separate it out, it will impact the instructions on how to build "everything" and releasecandidate.xml script will need updating as well to include the new Maven profile otherwise versions

Re: 0.9.3 Release

Alex, I was considering this part from Carlos: " If we do this, we should let people know that they must first build themes and then build royale-asjs." It looks like it is nothing what's actually impact Emulation. I did understand it wrong. Thanks, Piotr 2018-04-20 17:53 GMT+02:00 Alex Harui

Re: 0.9.3 Release

Jewel is in the develop branch and some updates are in MXRoyale that I will merge to develop after I finish reviewing Alina's PRs from last night. What problems are you having with the nightly? We should iron those out before starting an RC. You are more than welcome to be the RM, especially

Re: 0.9.3 Release

I would really like to see Jewel in this release. The nightly builds dont work for me and I am blocked because of this. BTW, can I be the release manager for this one? Thanks, Om On Fri, Apr 20, 2018, 8:53 AM Alex Harui wrote: > Hi Piotr, > > What kinds of impact

Re: 0.9.3 Release

Hi Alex, 2018-04-20 5:05 GMT+02:00 Alex Harui : > So much for releasing early each month ;-) > > yep! :))) > I merged develop and uibase-classname branches into the MXRoyale branch. > I'm thinking of merging MXRoyale into develop and cutting a release. We > will

<    1   2