Welcome Andrew Wetmore to Apache Royale's PMC

2019-10-03 Thread OmPrakash Muppirala
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 Apache Royale PMC)


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-01 Thread OmPrakash Muppirala
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 needing help, then the scripts need
> improving.  We want to capture knowledge in these scripts and on the wiki.
>
>
Alex, did you merge your fixes to the npm related stuff into the release
branch?  If yes, I think we should be good to go.

Thanks,
Om


> -Alex
>
> On 10/1/19, 12:30 AM, "Piotr Zarzycki"  wrote:
>
> Hi Om,
>
> What I need to do in order to release stuff on npm. Can you do this
> for me
> once I push release to svn ?
>
> Thanks,
> Piotr
>
> wt., 1 paź 2019 o 09:25 Piotr Zarzycki 
> napisał(a):
>
> > Hi Harbs,
> >
> > I think we have enough votes. I still have to gather info how
> actually
> > release Maven artifacts. However I'm going to push binaries today in
> svn.
> >
> > Thanks,
> > Piotr
> >
> > sob., 28 wrz 2019 o 20:02 Harbs  napisał(a):
> >
> >> FYI, I will not be able to test the release until Wednesday.
> >>
> >> If the vote is still open, I plan on testing then.
> >>
> >> Thanks,
> >> Harbs
> >>
> >> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >> wrote:
> >> >
> >> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript
> >> myself
> >> > yet, but will do that tomorrow or next week.
> >> >
> >> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
> >> apacheroyal...@gmail.com>
> >> > napisał(a):
> >> >
> >> >> This is the discussion thread.
> >> >>
> >> >> Thanks,
> >> >> Piotr
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> > Piotr Zarzycki
> >> >
> >> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> >> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> >*
> >>
> >>
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> >*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> >*
>
>
>


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

2019-09-16 Thread OmPrakash Muppirala
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.
> >
> > On Mon, Sep 16, 2019, 7:01 AM Piotr Zarzycki,  >
> > wrote:
> >
> > > Hi Andrew,
> > >
> > > I'm sorry but I already started preparing artifacts, so this probably
> > won't
> > > go to 0.9.6.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > pon., 16 wrz 2019 o 11:55  napisał(a):
> > >
> > > > This is an automated email from the ASF dual-hosted git repository.
> > > >
> > > > andreww pushed a commit to branch release/0.9.6
> > > > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> > > >
> > > >
> > > > The following commit(s) were added to refs/heads/release/0.9.6 by
> this
> > > > push:
> > > >  new 4136e54  Update RELEASE_NOTES.md
> > > > 4136e54 is described below
> > > >
> > > > commit 4136e543b3dba11bfadb08d9ce357cbb36d7b9a4
> > > > Author: Andrew Wetmore 
> > > > AuthorDate: Mon Sep 16 06:55:05 2019 -0300
> > > >
> > > > Update RELEASE_NOTES.md
> > > >
> > > > Many small text edits.
> > > > ---
> > > >  RELEASE_NOTES.md | 62
> > > > 
> > > >  1 file changed, 31 insertions(+), 31 deletions(-)
> > > >
> > > > diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
> > > > index a4a4bb0..9e8ec3c 100644
> > > > --- a/RELEASE_NOTES.md
> > > > +++ b/RELEASE_NOTES.md
> > > > @@ -1,38 +1,38 @@
> > > >  Apache Royale 0.9.6
> > > >  ===
> > > >
> > > > -- Compiles faster
> > > > -- For applications targeting JavaScript, you can now incorporate the
> > > vast
> > > > resources available in existing, free, JavaScript libraries.
> > > > -- Many additional components available:
> > > > -  - for Jewel: Wizard, PopUp, TabBar, Module, ModuleLoader,
> FooterBar,
> > > > Badge, ScrollableSectionContent, HorizontalListScroll
> > > > -- Emulations of many other components available
> > > > -- Many improvements and fixes in Jewel UI Set:
> > > > -  - DateField/DateChooser full implememtation.
> > > > -  - Fixes to make components work right on IE11 and Android/iOS
> mobile
> > > > devices.
> > > > -  - Many improvements to all themes included (styles for new
> > components,
> > > > added more styles like disabled missing in some components,...)
> > > > -  - Many beads included for Jewel set:
> > > > -- Added search filter bead on Jewel ComboBox
> > > > -- Added SearchFilterForList bead to use with Jewel List and
> > > TextInput.
> > > > +- Compiles faster.
> > > > +- For applications targeting JavaScript, you can now incorporate the
> > > vast
> > > > resources available in existing, free JavaScript libraries.
> > > > +- Many additional components are available:
> > > > +  - for the Jewel component set, Wizard, PopUp, TabBar, Module,
> > > > ModuleLoader, FooterBar, Badge, ScrollableSectionContent, and
> > > > HorizontalListScroll are now available.
> > > > +- Emulations of many other components are available.
> > > > +- Many improvements and fixes in the Jewel component set:
> > > > +  - Full implementation of DateField/DateChooser.
> > > > +  - Components now work correctly on IE11 and on Android/iOS mobile
> > > > devices.
> > > > +  - Many improvements to all themes, such as styles for new
> components
> > > > and a disabled style that was missing in some components.
> > > > +  - Many beads have been added for Jewel components:
> > > > +- Search filter bead on Jewel ComboBox
> > > > +- SearchFilterForList bead to use with Jewel List and TextInput
> > > >  - RequiredSelection for DropDownList
> > > > -  - Improvements on focus handling
> > > > -  - Button now extends from new BasicButton
> > > > -- Many improvements on Tour De Jewel demo app to show all new
> > components
> > > > and beads developed in this version.
> > > > -- Added BrowserOrientation bead
> > > > -- Added loadCSS, to load external CSS dinamically.
> > > > -- Added generation of source-maps to all Royale libs for better
> > > debugging
> > > > framework code.
> > > > +  - Improvements to focus handling.
> > > > +  - Button now extends from new BasicButton.
> > > > +- Many improvements on Tour De Jewel demo app to show components and
> > > > beads introduced in this version.
> > > > +- Added BrowserOrientation bead.
> > > > +- Added loadCSS, to load external CSS dynamically.
> > > > +- Added generation of source-maps to all Royale libs for better
> > > debugging
> > > > of framework code.
> > > >  - Added new [RoyaleUnit](
> > > > https://apache.github.io/royale-docs/testing/royaleunit.html)
> library
> > > for
> > > > unit testing.
> > > > -- Improvements to AMF / RemoteObject Support
> > > > +- Improvements to AMF / RemoteObject Support.
> > > >  - AMFBinaryData api now matches flash.utils.ByteArray, (the missing
> > > > feature is non-UTF String 

Re: Discuss of release steps preparation

2019-09-13 Thread OmPrakash Muppirala
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 Josh Tynjala 
> wrote:
>
> > In royale-compiler, I already added my release notes from develop into
> > release/0.9.6. I simply forgot to do the same for royale-asjs. I added
> > that
> > line about RoyaleUnit just now. Go ahead and add yours too, Greg. We'll
> be
> > merging release/0.9.6 back into develop later, so if you put them
> directly
> > in release/0.9.6, they won't be lost.
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Fri, Sep 13, 2019 at 10:24 AM Greg Dove  wrote:
> >
> > > Hi Piotr,
> > >
> > > I'm not so familiar with the release process. Do you want additions to
> go
> > > directly into the release branch or should that be added to develop
> > > (assuming you would merge into release)?
> > >
> > > I see Josh added note about RoyalUnit in develop [1], which is not yet
> in
> > > release.[2] . So perhaps you will merge from develop? I'm not sure how
> > this
> > > all needs to work.
> > >
> > > I'm thinking to add the following to 0.9.6 release notes (changes since
> > > 0.9.4) for some of the things I worked on:
> > >
> > > -Improvements to AMF / RemoteObject Support
> > > -AMFBinaryData api now matches flash.utils.ByteArray, (the missing
> > feature
> > > is non-UTF String encoding support). It therefore now works for deep
> > > cloning via readObject/writeObject and registerClassAlias.
> > > -Updates to Royale collections library with support for sorting and
> > > filtering via ArrayListView. Simple example added to Tour de Jewel
> > > -A conforming runtime implementation of AS3 Vector (typed Arrays) was
> > added
> > > for javascript output, with options for avoiding certain runtime
> checks.
> > > -int, uint, Class are now represented as simple, distinct types (Class
> is
> > > now not 'Object', int is now not 'Number' for example), and these
> support
> > > indirect 'as' or 'is' type checking and instantiation, matching swf
> > > behavior.
> > > -General Improvements and additions in Reflection library
> > > -New Apache Royale Crux MVC/DI/IOC application architecture library
> > (based
> > > on Swiz Framework) was added, with some simple examples
> > >
> > > If it's too late to add those, no worries, I can add that to the
> 'Updates
> > > to the RELEASE_NOTES discovered after this file was packaged' wiki
> > >
> > > 1. https://github.com/apache/royale-asjs/blob/develop/RELEASE_NOTES.md
> > > 2.
> > >
> >
> https://github.com/apache/royale-asjs/blob/release/0.9.6/RELEASE_NOTES.md
> > >
> > >
> > > Thanks,
> > > Greg
> > >
> > > On Fri, Sep 13, 2019 at 8:49 PM Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > > wrote:
> > >
> > > > Hi Guys,
> > > >
> > > > I would like to cut RC1 again on Monday, so if anything should be
> > tested
> > > or
> > > > added please do so before Monday.
> > > >
> > > > Let me know if anything is against that.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > On Fri, Sep 13, 2019, 12:32 AM Alex Harui 
> > > > wrote:
> > > >
> > > > > I pushed changes to update the config.xml files.  It seemed to work
> > for
> > > > > me.  Try beta10 if you want to test it.
> > > > >
> > > > > npm install  @apache-royale/royale-js-swf@0.9.6-beta10 -g
> > > > >
> > > > > Thanks,
> > > > > -Alex
> > > > >
> > > > > On 9/12/19, 10:56 AM, "Alex Harui" 
> > wrote:
> > > > >
> > > > > I guess that’s expected.  I didn’t realize I had a
> > > PLAYERGLOBAL_HOME
> > > > > environment variable that was overriding.
> > > > >
> > > > > The post install script would have to go replace the
> > target-player
> > > in
> > > > > every -config.xml file (like royale-config.xml).  If you add
> > > > > -target-player=25.0, that will get you past it.
> > > > >
> > > > > Another option is to have the install download 11.1 instead of
> > > 25.0.
> > > > >
> > > > > Thoughts?
> > > > > -Alex
> > > > >
> > > > >
> > > > > On 9/12/19, 10:30 AM, "Carlos Rovira"  >
> > > > wrote:
> > > > >
> > > > > Hi Alex,
> > > > >
> > > > > I uninstall then install again. Commented all my paths
> > (royale,
> > > > > flash
> > > > > player, AIR,...) in my .bash_profile. Then open a new
> > terminal
> > > > > window.
> > > > >
> > > > > Results:
> > > > >
> > > > > macbookpro:~ carlosrovira$ mxmlc
> > > > >
> > > > > Using Royale Compiler codebase:
> > > > >
> > > > >
> > > >
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../..
> > > > >
> > > > > Using Royale SDK:
> > > > >
> > > > >
> > > >
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/../..
> > > > >
> > > > > MXMLJSC
> > > > >
> > > > >
> > > > >
> > > >
> > >

Re: Discuss of release steps preparation

2019-09-11 Thread OmPrakash Muppirala
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 will wait, but I will at least try to revert changes which Maven
> did
> so I could perform steps properly.
>
> wt., 10 wrz 2019 o 07:21 Alex Harui 
> napisał(a):
>
> > I'm pretty sure you have to revert the changes made by Maven
> otherwise the
> > version numbers will be off.  And delete the tags as well.  The only
> thing
> > you don't want to do is delete and re-create the release branches.
> So make
> > sure you don't run those Jenkins steps.  I think you have to start
> with the
> > Maven Prepare steps so it creates a new tag for the Perform steps.
> >
> > I just tried Om's NPM changes on MacOS and am having the same
> problem as
> > Carlos.  IMO, we should hold off on another RC until that is
> resolved.
> >
> > My 2 cents,
> > -Alex
> >
> >
> > On 9/9/19, 10:16 PM, "Piotr Zarzycki" 
> wrote:
> >
> > What I understand now is that since I have updated release
> branches I
> > need
> > to perform maven artifacts builds, but not only - tag for RC1
> should be
> > changed as well. Probably I need to start perform for each
> repository
> > step
> > which creates for me tag, but before this is happening I need to
> remove
> > existing one. Am I right?
> >
> > wt., 10 wrz 2019 o 07:00 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > napisał(a):
> >
> > > Hi Alex,
> > >
> > > Ok I have updated each branches with newest changes from
> develop by
> > cherry
> > > pickup. What actually now ? Should I perform without reverting
> > anything ?
> > > [1] - I will try that today - it shouldn't break anything.
> > >
> > > [1]
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Steps-Jobs-On-Jenkins%23fail-and-revertdata=02%7C01%7Caharui%40adobe.com%7Ca3ef8d389f7e4f6ff40508d735af0d80%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637036898328967212sdata=6mHpIj33OvwPYqn2NZKEj8Gn2nUHpx0Nt3dOZKRqAGU%3Dreserved=0
> > >
> > >
> > > Thanks,
> > > Piotr
> > >
> > > sob., 7 wrz 2019 o 17:51 Alex Harui 
> > napisał(a):
> > >
> > >> Hi Piotr,
> > >>
> > >> Sure, time limitations may affect how much "development" you
> can
> > do, but
> > >> consider that if everyone ends up taking the same approach,
> then
> > every
> > >> future RM is going to spend time running into these issues,
> or make
> > >> mistakes manually uploading the artifacts and cause people to
> spend
> > time
> > >> examining more than one release candidate.  This is the key
> > difference that
> > >> I am pointing out.  I've definitely seen you work through
> tough
> > problems,
> > >> but most coding issues don't have as much impact on the
> others on
> > the team.
> > >>
> > >> There is no one right answer to how much sacrifice you should
> make
> > for
> > >> the project, but I asked several times for console output and
> never
> > got
> > >> it.  It might have been nice for you to report how long these
> steps
> > took on
> > >> your Windows computer so future RM's could plan ahead or we
> could
> > >> investigate optimizations or breaking steps into other
> pieces.  Now
> > the
> > >> next RM will have the responsibility for experiencing these
> long
> > builds and
> > >> sharing that information.
> > >>
> > >> Regarding the current RC, I will try it later today, but I
> agree
> > with
> > >> Andrew Wetmore that we need to have current RELEASE_NOTES, so
> this
> > RC
> > >> should not be the one released, but I will run other checks
> on it
> > to see if
> > >> there are other issues.  Andrew's proposal for the release
> notes
> > sounds
> > >> good to me so he or you should commit it to the release branch
> > along with
> > >> the link I used in prior release notes that point to our wiki.
> > That way we
> > >> can note other things later.
> > >>
> > >> For sure, thank you for the time and effort to get this far.
> > >>
> > >> -Alex
> > >>
> > >> On 9/7/19, 12:28 AM, "Piotr Zarzycki" <
> piotrzarzyck...@gmail.com>
> > wrote:
> > >>
> > >> Hi Alex,
> > >>
> > >> That is only partially true what you are saying. Cause I'm
> > definitely
> > >> not
> 

Re: Testing the npm install error fixes

2019-09-11 Thread OmPrakash Muppirala
On Tue, Sep 10, 2019, 11:25 PM Alex Harui  wrote:

> Om, why did you change the path to download_dependencies.js in the js-swf
> package.json?  Changing it back gets the script to run for me on Mac.


Ah I guess I was trying to fix things locally and checked that in by
mistake.  Good that you figured it out.


I then discovered that the download script only downloads the Windows AIR
> SDK so I'm currently trying to have it get the DMG for Mac before trying it
> on Windows.
>

We use the same SDK for the Mac and fix the file endings etc.  It should be
the same as downloading the 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, "OmPrakash Muppirala" 
> wrote:
>
> Damn I dint know about that.  I would be okay doing it manually
> this time
> and fixing the scripts for next release
> Unless Alex, you want to power through it this time.
>
> Om
>
> On Tue, Sep 10, 2019 at 4:53 PM Alex Harui
>  wrote:
>
> > I was going to try to publish another test package, but the
> npm/publish.js
> > script is not working for me.  Om, did you use it?  It appears
> that npm has
> > removed the registry API and we are supposed to use an
> > npm-publish-programmatically module instead?
> >
> > I may play with that today, so if you see more notifications
> about
> > publishing npm packages that's probably me.
> >
> > -Alex
> >
> > On 9/10/19, 10:17 AM, "Carlos Rovira" 
> wrote:
> >
> > Hi,
> >
> > I'm all for homebrew in Mac, when I have time and reinstall
> it to avoid
> > sudo, I'll do with homebrew for sure. I have all installed
> that way.
> >
> > El mar., 10 sept. 2019 a las 7:26, Alex Harui
> > ()
> > escribió:
> >
> > > I tried to remove node and npm and re-install it without
> sudo via
> > homebrew.
> > >
> > > I think I got the same results as Carlos.  FWIW, there is
> no
> > > @apache_royale folder in node_modules.
> > >
> > > ~$ npm i @apache-royale/royale-js-swf@0.9.6-beta0 -g
> > > /usr/local/bin/asjscompc ->
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscompcnpm
> > > /usr/local/bin/mxmlc ->
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/mxmlcnpm
> > > /usr/local/bin/asjsc ->
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscnpm
> > > /usr/local/bin/compc ->
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/compcnpm
> > > /usr/local/bin/asnodec ->
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asnodecnpm
> > > /usr/local/bin/externc ->
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/externcnpm
> > >
> > > > @apache-royale/royale-js-swf@0.9.6-beta0 postinstall
> > > /usr/local/lib/node_modules/@apache-royale/royale-js-swf
> > > > node dependencies/download_dependencies.js
> > >
> > > internal/modules/cjs/loader.js:775
> > > throw err;
> > > ^
> > >
> > > Error: Cannot find module
> > >
> >
> '/usr/local/lib/node_modules/@apache-royale/royale-js-swf/dependencies/download_dependencies.js'
> > > at Function.Module._resolveFilename
> > > (internal/modules/cjs/loader.js:772:15)
> > > at Function.Module._load
> (internal/modules/cjs/loader.js:677:27)
> > > at Function.Module.runMain
> > (internal/modules/cjs/loader.js:999:10)
> > > at internal/main/run_main_module.js:17:11 {
> > >   code:

Re: Testing the npm install error fixes

2019-09-10 Thread OmPrakash Muppirala
Damn I dint know about that.  I would be okay doing it manually this time
and fixing the scripts for next release
Unless Alex, you want to power through it this time.

Om

On Tue, Sep 10, 2019 at 4:53 PM Alex Harui  wrote:

> I was going to try to publish another test package, but the npm/publish.js
> script is not working for me.  Om, did you use it?  It appears that npm has
> removed the registry API and we are supposed to use an
> npm-publish-programmatically module instead?
>
> I may play with that today, so if you see more notifications about
> publishing npm packages that's probably me.
>
> -Alex
>
> On 9/10/19, 10:17 AM, "Carlos Rovira"  wrote:
>
> Hi,
>
> I'm all for homebrew in Mac, when I have time and reinstall it to avoid
> sudo, I'll do with homebrew for sure. I have all installed that way.
>
> El mar., 10 sept. 2019 a las 7:26, Alex Harui
> ()
> escribió:
>
> > I tried to remove node and npm and re-install it without sudo via
> homebrew.
> >
> > I think I got the same results as Carlos.  FWIW, there is no
> > @apache_royale folder in node_modules.
> >
> > ~$ npm i @apache-royale/royale-js-swf@0.9.6-beta0 -g
> > /usr/local/bin/asjscompc ->
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscompcnpm
> > /usr/local/bin/mxmlc ->
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/mxmlcnpm
> > /usr/local/bin/asjsc ->
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscnpm
> > /usr/local/bin/compc ->
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/compcnpm
> > /usr/local/bin/asnodec ->
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asnodecnpm
> > /usr/local/bin/externc ->
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/externcnpm
> >
> > > @apache-royale/royale-js-swf@0.9.6-beta0 postinstall
> > /usr/local/lib/node_modules/@apache-royale/royale-js-swf
> > > node dependencies/download_dependencies.js
> >
> > internal/modules/cjs/loader.js:775
> > throw err;
> > ^
> >
> > Error: Cannot find module
> >
> '/usr/local/lib/node_modules/@apache-royale/royale-js-swf/dependencies/download_dependencies.js'
> > at Function.Module._resolveFilename
> > (internal/modules/cjs/loader.js:772:15)
> > at Function.Module._load (internal/modules/cjs/loader.js:677:27)
> > at Function.Module.runMain
> (internal/modules/cjs/loader.js:999:10)
> > at internal/main/run_main_module.js:17:11 {
> >   code: 'MODULE_NOT_FOUND',
> >   requireStack: []
> > }
> > npm ERR! code ELIFECYCLE
> > npm ERR! errno 1
> > npm ERR! @apache-royale/royale-js-swf@0.9.6-beta0 postinstall: `node
> > dependencies/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
> > additional logging output above.
> >
> > npm ERR! A complete log of this run can be found in:
> > npm ERR!
>  /Users/aharui/.npm/_logs/2019-09-10T05_01_13_653Z-debug.log
> >
> >
> >
> > On 9/5/19, 9:32 AM, "OmPrakash Muppirala" 
> wrote:
> >
> > If you have to use sudo that usually means that your node/npm is
> not
> > setup
> > correctly.
> >
> > Some more info here :
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmedium.com%2F%40ExplosionPills%2Fdont-use-sudo-with-npm-still-66e609f5f92data=02%7C01%7Caharui%40adobe.com%7C31522b49bf6a4dc99edb08d73612bbda%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637037326406595828sdata=Vn%2FhX91xKLe3o65gVNaTxoQnOeqCqmAZGbYw18BQAbA%3Dreserved=0
> >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fa%2F18296178data=02%7C01%7Caharui%40adobe.com%7C31522b49bf6a4dc99edb08d73612bbda%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637037326406605829sdata=1T4ME4268RkdBV0TpRmxe0cQGkXVSq0e%2BTkjvny2rbA%3Dreserved=0
> >
> > That said, this issue is not related to sudo or otherwise.
> >
> > But it is a good idea to n

Re: Testing the npm install error fixes

2019-09-09 Thread OmPrakash Muppirala
Carlos,

Sorry, I was not clear.

We run the dependencies.js script after the installation as a `postInstall`
script.  It assumes that the @apache-royale/royale-js-swf directory is
created inside your global npm node_module directories.
You can verify if the package installed correctly in the first place by
running:

ls $(npm prefix -g)/lib/node_modules

Can you please run it and see if @apache-royale is listed there?

Thanks,
Om

On Mon, Sep 9, 2019 at 9:59 AM Carlos Rovira 
wrote:

> Hi Om,
>
> this is just a path you asked me for "dependencies.js" file, not the
> command 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 ( >)
> escribió:
>
> > 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 Muppirala (<
> > > bigosma...@gmail.com>) escribió:
> > >
> > > > Thanks Carlos, this is useful!
> > > >
> > > > Can you send the path for the dependencies.js file you have shown
> here?
> > > >
> > > > Regards,
> > > > Om
> > > >
> > > > On Fri, Sep 6, 2019 at 12:42 AM Carlos Rovira <
> carlosrov...@apache.org
> > >
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I'll try to see Om links as I have time. In the mean while here is
> > the
> > > > log:
> > > > >
> > > > > https://paste.apache.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 that usually means that your node/npm is
> > not
> > > > > setup
> > > > > > correctly.
> > > > > >
> > > > > > Some more info here :
> > > > > >
> > > > >
> > > >
> > >
> >
> https://medium.com/@ExplosionPills/dont-use-sudo-with-npm-still-66e609f5f92
> > > > > >
> > > > > > https://stackoverflow.com/a/18296178
> > > > > >
> > > > > > That said, this issue is not related to sudo or otherwise.
> > > > > >
> > > > > > But it is a good idea to not sudo anything related to npm.  For
> > > > instance,
> > > > > > our installation scripts downloads and does a bunch of things
> > during
> > > > the
> > > > > > installation.  Imagine allowing a random script sudo access to
> your
> > > > > > computer.
> > > > > >
> > > > > > Thanks,
> > > > > > Om
> > > > > >
> > > > > > On Thu, Sep 5, 2019, 9:00 AM Alex Harui  >
> > > > > wrote:
> > > > > >
> > > > > > > Pretty sure if you use -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, "OmPrakash Muppirala" <
> bigosma...@gmail.com
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > And oh, what is y

Re: Testing the npm install error fixes

2019-09-09 Thread OmPrakash Muppirala
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 Muppirala (<
> bigosma...@gmail.com>) escribió:
>
> > Thanks Carlos, this is useful!
> >
> > Can you send the path for the dependencies.js file you have shown here?
> >
> > Regards,
> > Om
> >
> > On Fri, Sep 6, 2019 at 12:42 AM Carlos Rovira 
> > wrote:
> >
> > > Hi,
> > >
> > > I'll try to see Om links as I have time. In the mean while here is the
> > log:
> > >
> > > https://paste.apache.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 that usually means that your node/npm is not
> > > setup
> > > > correctly.
> > > >
> > > > Some more info here :
> > > >
> > >
> >
> https://medium.com/@ExplosionPills/dont-use-sudo-with-npm-still-66e609f5f92
> > > >
> > > > https://stackoverflow.com/a/18296178
> > > >
> > > > That said, this issue is not related to sudo or otherwise.
> > > >
> > > > But it is a good idea to not sudo anything related to npm.  For
> > instance,
> > > > our installation scripts downloads and does a bunch of things during
> > the
> > > > installation.  Imagine allowing a random script sudo access to your
> > > > computer.
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Thu, Sep 5, 2019, 9:00 AM Alex Harui 
> > > wrote:
> > > >
> > > > > Pretty sure if you use -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, "OmPrakash Muppirala" 
> > > wrote:
> > > > >
> > > > > And oh, what is your node version?
> > > > >
> > > > > On Thu, Sep 5, 2019, 7:27 AM OmPrakash Muppirala <
> > > > bigosma...@gmail.com
> > > > > >
> > > > > 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, 2:41 AM Carlos Rovira <
> > > > carlosrov...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > >> Thanks Harbs,
> > > > > >> that seems not to fix the problem:
> > > > > >>
> > > > > >> macbookpro:~ carlosrovira$ sudo npm i
> > > > > >> @apache-royale/royale-js-swf@0.9.6-beta0 -g
> > > > > >>
> > > > > >> Password:
> > > > > >>
> > > > > >> /usr/local/bin/asjsc ->
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscnpm
> > > > > >>
> > > > > >> /usr/local/bin/asjscompc ->
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscompcnpm
> > > > &g

Re: Testing the npm install error fixes

2019-09-06 Thread OmPrakash Muppirala
Thanks Carlos, this is useful!

Can you send the path for the dependencies.js file you have shown here?

Regards,
Om

On Fri, Sep 6, 2019 at 12:42 AM Carlos Rovira 
wrote:

> Hi,
>
> I'll try to see Om links as I have time. In the mean while here is the log:
>
> https://paste.apache.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 that usually means that your node/npm is not
> setup
> > correctly.
> >
> > Some more info here :
> >
> https://medium.com/@ExplosionPills/dont-use-sudo-with-npm-still-66e609f5f92
> >
> > https://stackoverflow.com/a/18296178
> >
> > That said, this issue is not related to sudo or otherwise.
> >
> > But it is a good idea to not sudo anything related to npm.  For instance,
> > our installation scripts downloads and does a bunch of things during the
> > installation.  Imagine allowing a random script sudo access to your
> > computer.
> >
> > Thanks,
> > Om
> >
> > On Thu, Sep 5, 2019, 9:00 AM Alex Harui 
> wrote:
> >
> > > Pretty sure if you use -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, "OmPrakash Muppirala" 
> wrote:
> > >
> > > And oh, what is your node version?
> > >
> > > On Thu, Sep 5, 2019, 7:27 AM OmPrakash Muppirala <
> > bigosma...@gmail.com
> > > >
> > > 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, 2:41 AM Carlos Rovira <
> > carlosrov...@apache.org>
> > > > wrote:
> > > >
> > > >> Thanks Harbs,
> > > >> that seems not to fix the problem:
> > > >>
> > > >> macbookpro:~ carlosrovira$ sudo npm i
> > > >> @apache-royale/royale-js-swf@0.9.6-beta0 -g
> > > >>
> > > >> Password:
> > > >>
> > > >> /usr/local/bin/asjsc ->
> > > >>
> > > >>
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscnpm
> > > >>
> > > >> /usr/local/bin/asjscompc ->
> > > >>
> > > >>
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscompcnpm
> > > >>
> > > >> /usr/local/bin/mxmlc ->
> > > >>
> > > >>
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/mxmlcnpm
> > > >>
> > > >> /usr/local/bin/asnodec ->
> > > >>
> > > >>
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asnodecnpm
> > > >>
> > > >> /usr/local/bin/compc ->
> > > >>
> > > >>
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/compcnpm
> > > >>
> > > >> /usr/local/bin/externc ->
> > > >>
> > > >>
> > >
> >
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/externcnpm
> > > >>
> > > >>
> > > >> > @apache-royale/royale-js-swf@0.9.6-beta0 postinstall
> > > >> /usr/local/lib/node_modules/@apache-royale/royale-js-swf
> > > >>
> > > >> > node dependencies/download_dependencies.js
> > > >>
> > > >>
> > > >> internal/modules/cjs/loader.js:582
> > > >>
> > > >> throw err;
> > > &

Re: Discuss of release steps preparation

2019-09-06 Thread OmPrakash Muppirala
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 0.9.7 in
> few more weeks catch the final problems. As soon as we have this working
> and documentation more polished we can go to 1.0. We can even go from 0.9.7
> to 1.0 without necessarily do releases for 0.9.8 and 0.9.9
>
> just my 2ctns
>

+1

Having gone through the same process unsuccessfully a few months ago, I can
relate to Piotr's state of mind :-)
Let's get through the last bits manually, document what happened and
continue to improve the automated process in the next releases.

Thanks,
Om



>
>
>
> El vie., 6 sept. 2019 a las 11:00, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Alex,
> >
> > I would love to encourage more people to be RM, but unfortunately my time
> > which I should spend on that release was exceeded at least double. I
> prefer
> > make now manually commit than deal with it - I'm sorry about that.
> >
> > As for console output - you are saying that previous steps matters to
> that
> > one ? I sounds like I should do previous step in the same console window
> > cause it's influences current one.
> >
> > Thanks,
> > Piotr
> >
> > śr., 4 wrz 2019 o 18:52 Alex Harui 
> napisał(a):
> >
> > > Piotr,
> > >
> > > Well, I can't tell you what to do, but if we want to encourage more
> > > frequent releases and more people volunteering to be the RM, at some
> > point,
> > > somebody else besides me has to either create a rather complex
> > step-by-step
> > > manual/runbook or help debug these scripts.  I'm willing to help with
> the
> > > latter, but I cannot without seeing the console output of prior steps.
> > > This is a process or sequence.  The steps you run before matter to the
> > step
> > > you are trying to run now.
> > >
> > > -Alex
> > >
> > > On 9/4/19, 9:19 AM, "Piotr Zarzycki" 
> wrote:
> > >
> > > Hi Alex,
> > >
> > > I know that is the goal, but I simply failed to meet those goals
> and
> > I
> > > gave
> > > up on that. I have artifacts and I would like to release Royale -
> > > that's
> > > may goal, whether I do this in 90% automatically and 10% manually
> > > after so
> > > many hours of work it doesn't matter to me now.
> > >
> > > You are seeing full console output actually. Nothing more happen
> > there.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > śr., 4 wrz 2019 o 18:11 Alex Harui 
> > > napisał(a):
> > >
> > > > Again, the goal is here to debug the scripts, not to skip them.
> > > >
> > > > And it is hard to help without console output to examine.
> > > >
> > > > Yes, you have set the variables, but have the other steps run
> that
> > > > generate an SVN working copy at that destination?  Show the
> console
> > > output
> > > > related to it.
> > > >
> > > > HTH,
> > > > -Alex
> > > >
> > > > On 9/4/19, 9:01 AM, "Piotr Zarzycki" 
> > > wrote:
> > > >
> > > > From that point I will probably upload artifacts manually and
> > > run RC1.
> > > >
> > > > śr., 4 wrz 2019 o 16:30 Piotr Zarzycki <
> > > piotrzarzyck...@gmail.com>
> > > > napisał(a):
> > > >
> > > > > It looks like I have another problems. Target for uploading
> > ant
> > > > artifacts
> > > > > is failing:
> > > > >
> > > > > ant -f releasesteps_asjs.xml Release_Step_013_Upload
> > > > > -Drelease.version=0.9.6 -Drc=1
> > > > >
> > > > > Buildfile:
> > /Users/piotr/Downloads/royale/releasesteps_asjs.xml
> > > > >
> > > > > check-name-and-svn:
> > > > >  [echo] Name: 'Piotr Zarzycki'
> > > > >  [echo] svn.dist.dev:
> > > /Users/piotr/Downloads/royale/dist/dev
> > > > >  [echo] svn.dist.release:
> > > > /Users/piotr/Downloads/royale/dist/release
> > > > >  [echo] svn: /usr/bin/svn
> > > > >
> > > > > BUILD FAILED
> > > > > /Users/piotr/Downloads/royale/releasesteps_asjs.xml:1537:
> The
> > > > svn.dist.dev
> > > > > property is not set to the working copy for
> > > > >
> > > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdevdata=02%7C01%7Caharui%40adobe.com%7C7a223df6f5d4435c17c008d731539953%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637032107443413136sdata=Et8HJHapB3FvMonYzhnsfNoonvUfRd1VNr5GUktMcDs%3Dreserved=0
> > > > .
> > > > >
> > > > > As you can see above I have all properties setup cause I
> made
> > > an
> > > > echo. I
> > > > > don't understand what is happening...
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > śr., 4 wrz 2019 o 13:13 Piotr 

Re: Testing the npm install error fixes

2019-09-05 Thread OmPrakash Muppirala
If you have to use sudo that usually means that your node/npm is not setup
correctly.

Some more info here :
https://medium.com/@ExplosionPills/dont-use-sudo-with-npm-still-66e609f5f92

https://stackoverflow.com/a/18296178

That said, this issue is not related to sudo or otherwise.

But it is a good idea to not sudo anything related to npm.  For instance,
our installation scripts downloads and does a bunch of things during the
installation.  Imagine allowing a random script sudo access to your
computer.

Thanks,
Om

On Thu, Sep 5, 2019, 9:00 AM Alex Harui  wrote:

> Pretty sure if you use -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, "OmPrakash Muppirala"  wrote:
>
> 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, 2:41 AM Carlos Rovira 
> > wrote:
> >
> >> Thanks Harbs,
> >> that seems not to fix the problem:
> >>
> >> macbookpro:~ carlosrovira$ sudo npm i
> >> @apache-royale/royale-js-swf@0.9.6-beta0 -g
> >>
> >> Password:
> >>
> >> /usr/local/bin/asjsc ->
> >>
> >>
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscnpm
> >>
> >> /usr/local/bin/asjscompc ->
> >>
> >>
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscompcnpm
> >>
> >> /usr/local/bin/mxmlc ->
> >>
> >>
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/mxmlcnpm
> >>
> >> /usr/local/bin/asnodec ->
> >>
> >>
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asnodecnpm
> >>
> >> /usr/local/bin/compc ->
> >>
> >>
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/compcnpm
> >>
> >> /usr/local/bin/externc ->
> >>
> >>
> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/externcnpm
> >>
> >>
> >> > @apache-royale/royale-js-swf@0.9.6-beta0 postinstall
> >> /usr/local/lib/node_modules/@apache-royale/royale-js-swf
> >>
> >> > node dependencies/download_dependencies.js
> >>
> >>
> >> internal/modules/cjs/loader.js:582
> >>
> >> throw err;
> >>
> >> ^
> >>
> >>
> >> Error: Cannot find module
> >>
> >>
> '/usr/local/lib/node_modules/@apache-royale/royale-js-swf/dependencies/download_dependencies.js'
> >>
> >> at Function.Module._resolveFilename
> >> (internal/modules/cjs/loader.js:580:15)
> >>
> >> at Function.Module._load (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:739:3)
> >>
> >> npm ERR! code ELIFECYCLE
> >>
> >> npm ERR! errno 1
> >>
> >> npm ERR! @apache-royale/royale-js-swf@0.9.6-beta0 postinstall:
> `node
> >> dependencies/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
> >> additional logging output above.
> >>
> >>
> >> npm ERR! A complete log of this run can be found in:
> >>
> >> npm ERR!
> >> /Users/carlosrovira/.npm/_logs/2019-09-05T09_39_50_359Z-debug.log
> >>
&g

Re: Testing the npm install error fixes

2019-09-05 Thread OmPrakash Muppirala
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, 2:41 AM Carlos Rovira 
> wrote:
>
>> Thanks Harbs,
>> that seems not to fix the problem:
>>
>> macbookpro:~ carlosrovira$ sudo npm i
>> @apache-royale/royale-js-swf@0.9.6-beta0 -g
>>
>> Password:
>>
>> /usr/local/bin/asjsc ->
>>
>> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscnpm
>>
>> /usr/local/bin/asjscompc ->
>>
>> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscompcnpm
>>
>> /usr/local/bin/mxmlc ->
>>
>> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/mxmlcnpm
>>
>> /usr/local/bin/asnodec ->
>>
>> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asnodecnpm
>>
>> /usr/local/bin/compc ->
>>
>> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/compcnpm
>>
>> /usr/local/bin/externc ->
>>
>> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/externcnpm
>>
>>
>> > @apache-royale/royale-js-swf@0.9.6-beta0 postinstall
>> /usr/local/lib/node_modules/@apache-royale/royale-js-swf
>>
>> > node dependencies/download_dependencies.js
>>
>>
>> internal/modules/cjs/loader.js:582
>>
>> throw err;
>>
>> ^
>>
>>
>> Error: Cannot find module
>>
>> '/usr/local/lib/node_modules/@apache-royale/royale-js-swf/dependencies/download_dependencies.js'
>>
>> at Function.Module._resolveFilename
>> (internal/modules/cjs/loader.js:580:15)
>>
>> at Function.Module._load (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:739:3)
>>
>> npm ERR! code ELIFECYCLE
>>
>> npm ERR! errno 1
>>
>> npm ERR! @apache-royale/royale-js-swf@0.9.6-beta0 postinstall: `node
>> dependencies/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
>> additional logging output above.
>>
>>
>> npm ERR! A complete log of this run can be found in:
>>
>> npm ERR!
>> /Users/carlosrovira/.npm/_logs/2019-09-05T09_39_50_359Z-debug.log
>>
>> macbookpro:~ carlosrovira$
>>
>>
>>
>>
>>
>> El jue., 5 sept. 2019 a las 11:32, Harbs ()
>> escribió:
>>
>> > Try sudo.
>> >
>> > > On Sep 5, 2019, at 12:24 PM, Carlos Rovira 
>> > wrote:
>> > >
>> > > Hi Om,
>> > >
>> > > I tried to install now with : npm i
>> > @apache-royale/royale-js-swf@0.9.6-beta0
>> > > -g
>> > >
>> > > I get this:
>> > >
>> > > Last login: Fri Aug 30 00:01:50 on ttys000
>> > >
>> > > macbookpro:~ carlosrovira$ npm i
>> @apache-royale/royale-js-swf@0.9.6-beta0
>> > -g
>> > >
>> > > /usr/local/bin/asjsc ->
>> > >
>> >
>> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscnpm
>> > >
>> > > /usr/local/bin/asnodec ->
>> > >
>> >
>> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asnodecnpm
>> > >
>> > > /usr/local/bin/mxmlc ->
>> > >
>> >
>> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/mxmlcnpm
>> > >
>> > > /usr/local/bin/asjscompc ->
>> > >
>> >
>> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/asjscompcnpm
>> > >
>> > > /usr/local/bin/compc ->
>> > >
>> >
>> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-asjs/js/bin/compcnpm
>> > >
>> > > /usr/local/bin/externc ->
>> > >
>> >
>> /usr/local/lib/node_modules/@apache-royale/royale-js-swf/royale-a

Re: Testing the npm install error fixes

2019-09-05 Thread OmPrakash Muppirala
; (internal/modules/cjs/loader.js:580:15)
> > >
> > >at Function.Module._load (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:739:3)
> > >
> > > npm ERR! code ELIFECYCLE
> > >
> > > npm ERR! errno 1
> > >
> > > npm ERR! @apache-royale/royale-js-swf@0.9.6-beta0 postinstall: `node
> > > dependencies/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
> > > additional logging output above.
> > >
> > >
> > > npm ERR! A complete log of this run can be found in:
> > >
> > > npm ERR!
> > > /Users/carlosrovira/.npm/_logs/2019-09-05T09_23_42_762Z-debug.log
> > >
> > > macbookpro:~ carlosrovira$
> > >
> > >
> > >
> > >
> > >
> > > El mar., 3 sept. 2019 a las 21:55, OmPrakash Muppirala (<
> > > bigosma...@gmail.com>) escribió:
> > >
> > >> Carlos,
> > >>
> > >> A nice way to test if your installation is working correctly is to try
> > it
> > >> with the npm cli tool.
> > >>
> > >> You can install the cli using the command:
> > >>
> > >> npm i @apache-royale/cli -g
> > >>
> > >> Basically install the royale package, then install the cli package.
> And
> > >> follow the instructions here:
> > >> https://www.npmjs.com/package/@apache-royale/cli
> > >>
> > >> Thanks,
> > >> Om
> > >>
> > >> On Tue, Sep 3, 2019 at 11:11 AM Carlos Rovira <
> carlosrov...@apache.org>
> > >> wrote:
> > >>
> > >>> Hi Om,
> > >>>
> > >>> since I don't know too much about NPM, I want to know some few things
> > >> about
> > >>> the Royale NPM version. Just uninstalled old version successfully.
> > >>>
> > >>> Now, I'm on Mac. if I install the new one, how this affects my
> > >> environment?
> > >>> I suppose that my installation of repos to build from source code is
> > >>> independent, and NPM installs mxmlc in Terminal (command line level).
> > >>>
> > >>> Then, some easy way to give a quick test that all is working ok? I
> > >> suppose
> > >>> 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 (<
> > >>> bigosma...@gmail.com>) escribió:
> > >>>
> > >>>> Hi folks,
> > >>>>
> > >>>> Can you please test the beta release and report any errors you are
> > >>> seeing?
> > >>>>
> > >>>> You can test it with these commands:
> > >>>>
> > >>>> npm uninstall @apache-royale/royale-js-swf -g (in case you already
> > have
> > >>> it
> > >>>> installed)
> > >>>> npm i @apache-royale/royale-js-swf@0.9.6-beta0 -g
> > >>>>
> > >>>> Thanks,
> > >>>> Om
> > >>>>
> > >>>> On Sun, Sep 1, 2019 at 7:52 PM OmPrakash Muppirala <
> > >> bigosma...@gmail.com
> > >>>>
> > >>>> 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/royale-asjs/issues/428
> > >>>>> https://github.com/apache/royale-asjs/issues/450
> > >>>>> https://github.com/apache/royale-asjs/issues/231
> > >>>>>
> > >>>>> Thanks,
> > >>>>> Om
> > >>>>>
> > >>>>
> > >>>
> > >>>
> > >>> --
> > >>> Carlos Rovira
> > >>> http://about.me/carlosrovira
> > >>>
> > >>
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


Re: Testing the npm install error fixes

2019-09-03 Thread OmPrakash Muppirala
Carlos,

A nice way to test if your installation is working correctly is to try it
with the npm cli tool.

You can install the cli using the command:

npm i @apache-royale/cli -g

Basically install the royale package, then install the cli package.  And
follow the instructions here:
https://www.npmjs.com/package/@apache-royale/cli

Thanks,
Om

On Tue, Sep 3, 2019 at 11:11 AM Carlos Rovira 
wrote:

> Hi Om,
>
> since I don't know too much about NPM, I want to know some few things about
> the Royale NPM version. Just uninstalled old version successfully.
>
> Now, I'm on Mac. if I install the new one, how this affects my environment?
> I suppose that my installation of repos to build from source code is
> independent, and NPM installs mxmlc in Terminal (command line level).
>
> Then, some easy way to give a quick test that all is working ok? I suppose
> 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 (<
> bigosma...@gmail.com>) escribió:
>
> > Hi folks,
> >
> > Can you please test the beta release and report any errors you are
> seeing?
> >
> > You can test it with these commands:
> >
> > npm uninstall @apache-royale/royale-js-swf -g (in case you already have
> it
> > installed)
> > npm i @apache-royale/royale-js-swf@0.9.6-beta0 -g
> >
> > Thanks,
> > Om
> >
> > On Sun, Sep 1, 2019 at 7: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/royale-asjs/issues/428
> > > https://github.com/apache/royale-asjs/issues/450
> > > https://github.com/apache/royale-asjs/issues/231
> > >
> > > Thanks,
> > > Om
> > >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


Re: Testing the npm install error fixes

2019-09-03 Thread OmPrakash Muppirala
Hi folks,

Can you please test the beta release and report any errors you are seeing?

You can test it with these commands:

npm uninstall @apache-royale/royale-js-swf -g (in case you already have it
installed)
npm i @apache-royale/royale-js-swf@0.9.6-beta0 -g

Thanks,
Om

On Sun, Sep 1, 2019 at 7: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/royale-asjs/issues/428
> https://github.com/apache/royale-asjs/issues/450
> https://github.com/apache/royale-asjs/issues/231
>
> Thanks,
> Om
>


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

2019-09-03 Thread OmPrakash Muppirala
(Moving discussion to dev@ since there is no reason why this discussion
needs to be on private@)

Piotr,

That is fine.  We can always do a manual release.

In that case, please disable the automatic publish to npm during the
release stage.

Thanks,
Om

On Tue, Sep 3, 2019 at 10:38 AM Carlos Rovira 
wrote:

> ok Thanks for clarifying! :)
>
> El mar., 3 sept. 2019 a las 18:52, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
>> Just to make it clear if I will be successful finally on Mac with
>> building ANT artifacts we will have RC1 from following 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 OmPrakash Muppirala 
>> napisał(a):
>>
>>> That is correct.  This is only a test.
>>> I'm making sure that all the npm related issues are fixed before our
>>> next release.
>>>
>>> Thanks,
>>> Om
>>>
>>> On Tue, Sep 3, 2019, 8:36 AM Josh Tynjala 
>>> wrote:
>>>
>>>> Om explained on dev@ that he'd be doing some test publishes to verify
>>>> that some changes were working correctly.
>>>>
>>>> --
>>>> Josh Tynjala
>>>> Bowler Hat LLC <https://bowlerhat.dev>
>>>>
>>>>
>>>> On Tue, Sep 3, 2019 at 8:34 AM Carlos Rovira 
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> should I post about this publication in twitter, facebook...
>>>>> or is just a test?
>>>>>
>>>>> thanks
>>>>>
>>>>
>
>


Testing the npm install error fixes

2019-09-01 Thread OmPrakash Muppirala
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
https://github.com/apache/royale-asjs/issues/450
https://github.com/apache/royale-asjs/issues/231

Thanks,
Om


Re: Website - create Showcase section

2019-07-24 Thread OmPrakash Muppirala
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: Wednesday, July 24, 2019 7:35:54 PM
> To: dev@royale.apache.org 
> Subject: Re: Website - create Showcase section
>
> Hi Yishay,
>
> good to know! ok we can start posting.
> In our case, I was thinking yesterday in make white brand version of our
> app to avoid conflicts with our clients, since the important thing is to
> showcase and put screenshots available to browse.
> For All apps we'll need some screenshots in concrete sizes-dimensions, in
> case we want to show case as screenshots. Other than that, could be post
> some video or gif animation, but I think the screen shot option will be
> more elegant to generate good visuals.
>
> I can revisit that part of the website and post soon info and material that
> app creators must provide in order to fill its own page.
>
> Also, I have in my plate the page for Third party companies that wants to
> be listed in our site to sell services and consultancy around Apache
> Royale.
>
> thanks
>
>
> El mié., 24 jul. 2019 a las 8:17, Yishay Weiss ()
> escribió:
>
> > Hi,
> >
> > Is it time to have a production showcase section?
> >
> > We have Harbs [1] and Justin [2] in production. Hopefully Carlos, Alina,
> > Andrew, et al join them soon.
> >
> > Tour de Flex and documentation app can also be made to be showcase
> worthy,
> > although perhaps in a different section.
> >
> > What do you all think?
> >
> > Yishay
> >
> > [1] https://marketinginflection.com/printui-demo.php
> > [2] https://rest-swf.prominic.net/Royale/Native/1.0.3/index.html
> >
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


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

2019-06-06 Thread OmPrakash Muppirala
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 Royale.

Thanks,
Om

On Thu, Jun 6, 2019, 3:32 AM Carlos Rovira  wrote:

> Hi,
>
> I think in the case of HTML, does not have sense to me the concept of Embed
> like in Flex. Maybe of SWF target or others (don't know if WebAsm could
> benefit from something like this)
> Maybe for HTML use something like Embed metadata, could just copy the
> assets to the resources folder to be available, since like Alex said, a
> request per asset is needed and making other kind of big file seems strange
> in this case (maybe not). Although we have solved the copying of assets in
> different ways through compiler for libraries and ANT/MAVEN automation in
> Application.
>
> for me this could be something to investigate in the future, but with low
> priority, since I think we still have bigger fish to fry
>
> just my 2...
>
>
> El mié., 5 jun. 2019 a las 18:07, Alex Harui ()
> escribió:
>
> > Regarding embedded assets in Royale:
> >
> > There is no embedded asset support at this time because it is not obvious
> > to me it will be worth it.  We need a volunteer to devise a strategy that
> > works and implement it.
> >
> > In Flex/Flash, my understanding is that folks embedded assets to save on
> > server requests for assets like images.  That makes sense because, since
> a
> > SWF is a compressed binary and most assets are compressed binaries, you
> can
> > essentially append the assets to the SWF.
> >
> > However, for Royale in the browser, every implementation of "embedding"
> > I've seen seems to Base64 encode the asset, converting it to text and
> > increasing the number of bytes.  And the resulting Base64 bytes may
> > deteriorate the gzip compression of the .html file.
> >
> > Flash also had frames in the SWF and assets could be embedded on later
> > frames allowing a download progress bar to show up before all of the rest
> > of the SWF is downloaded.  I don't know what the equivalent for that is
> > without Flash.
> >
> > I believe another advantage of embedding in Flash was that the asset was
> > ready to be instantiated and placed on the display list right away.  I'm
> > not clear that an embedded Base64 image can be used in an  tag and
> > prevent "popping" given that Royale generates the  tags dynamically.
> >
> > So, we need a volunteer to create some examples of how to use browser
> > embedding in dynamically generated  tags so we can see if there will
> > be any benefit or not.  And if not, possibly explore other options, such
> as
> > delivering all assets in one true binary blob somehow.
> >
> > HTH,
> > -Alex
> >
> > On 6/5/19, 7:05 AM, "Frost, Andrew"  wrote:
> >
> > Yes, me :-)
> >
> > I'm pushing Royale internally, I think it has a lot of promise -
> > although I still do find it a little frustrating at times internally! In
> > terms of what support you can give, the sorts of things you're already
> > doing are great, but yes it might mean we lean a little more on this
> > mailing list if we're facing tricky issues.
> >
> > We have one sales case in particular at the moment which has the
> > potential to be very big, we're hoping they move forwards with a proof of
> > concept project which would take a small part of their app and port this
> to
> > Royale. A few issues we've found so far from investigations:
> > - their flex code is embedding icons that are contained within a SWF.
> > Royale compiler didn't seem to like this, not sure whether it's just
> syntax
> > or whether we need to pull all the assets out (not a big job, we can
> > automate that..)
> > - they have binding using functions e.g.
> > text="{localizationHelper.getString('fieldName')}", which caused an issue
> > when generating the JavaScript code as the string-within-a-string seemed
> to
> > upset the parser. We can look at this later perhaps though..
> > - when we got it compiling, the main thing was with responsiveness
> > i.e. trying to get the app to resize and for all the internal elements to
> > then resize. We may use the MX emulation classes for this but it still
> > looked like more support is needed - although we only looked briefly at
> > this.
> >
> > Once those issues are sorted though, we would have one big task (to
> > recreate a very advanced data grid control that they'd developed in
> > Flex/Flash) and a lot of the rest - around the AS3 logic - should fall
> into
> > place! I'm hoping we can convince them to go with this solution..
> >
> >
> > thanks
> >
> >Andrew
> >
> >
> >
> > -Original Message-
> > From: Harbs [mailto:harbs.li...@gmail.com]
> > Sent: 04 June 2019 14:41
> > To: dev@royale.apache.org
> > Subject: [EXTERNAL] Re: AIR and Royale
> >
> > Well 

Re: Let's bump Royale version to 1.0

2019-04-29 Thread OmPrakash Muppirala
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 developers are now used to those workflows.
> In case of React, create-react-app sets you up with a brand new, ready to
> go project in less than 30 seconds. That should be a benchmark for Royale
> imo.
>
> Dany
>
>
The Royale CLI is modeled closely after the create-react-app.  The docs for
the alpha version is available here:
https://github.com/apache/royale-asjs/tree/develop/npm/cli
If I get more feedback, I am keep improving this tool.

Thanks,
Om



> Verstuurd vanaf mijn iPhone
>
> > Op 26 apr. 2019 om 12:42 heeft Frost, Andrew 
> het volgende geschreven:
> >
> > One other thought ... currently the way people ask for support is via
> these mailing lists. Which are okay but I'm always conscious that I'm
> potentially spamming people, plus the volume of mails is such that I have a
> rule to push all these into a folder that I then review every day or two..
> >
> > But if I want to find something out, I tend not to go search the mailing
> list, I tend to search online. Looking through mailing list threads isn't
> the easiest (and search engines don't necessarily pick things up from them
> very well) but a major source of support is Stack Overflow... I use this a
> lot with my other work and there's a lot of information there.
> >
> > Apache Royale doesn't appear to have a tag; when I search for "royale"
> all I got was stuff about "Clash Royale"; there are however 8 questions
> with "flexjs" tags.
> >
> > But wouldn't it be good for people to add questions and to contribute
> answers there, both from the user perspective and perhaps also the dev
> perspective? Would be interested in people's thoughts... (and perhaps I'll
> have to dig out my SO credentials to start contributing there)
> >
> > thanks
> >
> >  Andrew
> >
> >
> > -Original Message-
> > From: Carlos Rovira [mailto:carlosrov...@apache.org]
> > Sent: 26 April 2019 10:39
> > To: dev@royale.apache.org
> > Subject: [EXTERNAL] Re: Let's bump Royale version to 1.0
> >
> > Hi Angelo, that's great! :)
> >
> > any help here is very appreciated.
> >
> > Share in a new mail a concrete contribution before starting to work on
> it, so we can know about it and help you on the task so your work fit
> perfectly in the overall picture.
> >
> > I'd like to create videos too, and people asked about it in facebook and
> twitter. Do you have skills in creating videos?
> >
> >
> >
> > El vie., 26 abr. 2019 a las 10:47, Angelo Lazzari (<
> lazzari.ang...@gmail.com>)
> > escribió:
> >
> >> Yes, i can give some slots to help with documentation or example
> >> project or so... I think tutorial videos could be help to understand
> >> rapidly the platform and could help new user to get ready in a few
> >> hours to start build their project.
> >>
> >> Angelo
> >>
> >> On Fri, Apr 26, 2019 at 10:42 AM Carlos Rovira
> >> 
> >> wrote:
> >>
> >>> Agree with latest comments.
> >>>
> >>> I think we should work in docs and ease the start of new users to
> >>> target
> >>> 1.0
> >>> And in the process fix some few things (i.e: don't want to reach 1.0
> >>> with Jewel Table in its current state and API)
> >>>
> >>> What do you think?
> >>>
> >>> If you all agree could you think on how to contribute to that
> >>> effort? Can we have as a near goal to bring 1.0 planing ourselves to
> >>> donate some
> >> hours
> >>> to Apache Royale to make this happen? If some of us help in the
> >>> current state I think we can get to it sooner.
> >>>
> >>> Thanks
> >>>
> >>>
> >>> El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari (<
> >>> lazzari.ang...@gmail.com>)
> >>> escribió:
> >>>
>  I am completely agree with Olaf: start using a new platform where
>  the documentation is not complete, clean and updated it is a
>  really bad thing...and it would be a potential reason to increase
>  the difficulty
> >> to
>  adopt the platform...
> 
>  Angelo
> 
>  El vie., 26 abr. 2019 8:54, Olaf Krueger 
> >>> escribió:
> 
> > Hi,
> >
> > Basically, I think it's important to provide a great developer
>  experience.
> > IMO, that's more important than trying to implement missing features.
> >
> > One thing to achieve this is documentation of course.
> > Thanks to all of you there already exist a lot of docs, but it
> > feels
> >> a
>  bit
> > messy because they are hosted at different places, e.g.:
> >
> > - royale-docs repo
> > - royale-asjs wiki
> > - royale-asjs Readme
> > -
> > https://clicktime.symantec.com/3SEvxFs2HbjNAgsLBEtNLr17Vc?u=http
> > s%3A%2F%2Froyale.apache.org
> > - ...?
> >
> > As a user, it's hard to get an overview of what is available...
> > and
>  where.
> 

Re: 0.9.6 Release

2019-03-08 Thread OmPrakash Muppirala
On Fri, Mar 8, 2019, 9:17 AM Alex Harui  wrote:

> Om,
>
> Why is Linux required?  I thought Docker worked on Windows.  Or does it
> create a Linux VM in the Windows Docker container?
>

Almost all base docker images are based on some variant of Linux.  There
are some windows images 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 have right now is to get the AIR runtime working
> inside
> a linux container.
>
> There are a few hacks available to try amd force it, but I could never
> get
> it to work unfortunately.
>
> Thanks,
> Om
>
> On Fri, Mar 8, 2019, 2:13 AM Carlos Rovira 
> wrote:
>
> > Hi Alex,
> >
> > amazing work! congrats to reach to this point! :)
> >
> > I need to put my head on all of this, but count on me to be a RM. I
> think
> > the best thing should be that you be the first RM to try your own
> > development at least for the first time, and then the rest of us will
> > follow you on the next releases. With all this on place we maybe
> could
> > release once a month or every two months...
> >
> > Thanks for doing this :)
> >
> > Carlos
> >
> >
> > El vie., 8 mar. 2019 a las 1:55, Alex Harui
> ()
> > escribió:
> >
> > > OK, I've now seen Jenkins perform the steps to build the release
> > > artifacts.  Folks interested in Docker-izing the steps are welcome
> to
> > look
> > > at the jobs on the "Royale Release" tab on the CI server.
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%3A8080%2Fview%2FRoyale%2520Release%2Fdata=02%7C01%7Caharui%40adobe.com%7C883e07bd09204902f46808d6a3e4d6db%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876600643816569sdata=xhRB2A%2BHzgFpnk02yiEc71xLYO15yZU851nlN0mRBDQ%3Dreserved=0
> > >
> > > These steps assume that the RM can run the basic Maven and Ant
> build on
> > > the RM's computer. I think that's a fair requirement since all of
> us on
> > the
> > > PMC need to able to do that to build the RC in order to vote on it.
> > >  Jenkins does other tasks like run the Maven release plugin steps.
> > >
> > > Currently that results in binaries on Jenkins that are downloaded
> to the
> > > RM's computer.  These binaries need to be verified by the RM which
> is the
> > > next phase I will be starting on now.  The RM verifies the bits
> and then
> > > PGP signs them.  And then the bits are uploaded off the RM's
> computer to
> > > Maven Staging or dist.a.o/dev.   If that uploading turns out to be
> a
> > point
> > > of failure, we have the option of having Jenkins upload the big
> files and
> > > have the RM only upload PGP signature files.  Or finding a way for
> > Jenkins
> > > to get the signature files from the RM.  The uploads worked fine
> for me,
> > > but then again, so did the old script's uploads.
> > >
> > > Therefore, once I get the binary verification phase completed, I
> think
> > > someone other than me should be the RM and try to use these steps
> to
> > > generate the release and help debug the process for the next RM.
> So,
> > > please try to carve out some time to be the RM.  One advantage of
> doing
> > > most of the work on Jenkins is that it frees up my computer to do
> other
> > > things while Jenkins is cranking away.
> > >
> > > I think we're at least a week away from binary verification, maybe
> two,
> > so
> > > it is time to start thinking about what is going in this release.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 3/7/19, 4:15 PM, "Alex Harui"  wrote:
> > >
> > > In case you haven't guessed, I'm testing out Jenkins and its
> ability
> > > to create the artifacts and send emails.  Please ignore any email
> that
> > > looks like a vote or discuss thread.
> > >
> > > Thanks,
> > > -Alex
> > >
> > > On 2/10/19, 8:44 PM, "Alex Harui" 
> wrote:
>   

Re: 0.9.6 Release

2019-03-08 Thread OmPrakash Muppirala
would be interested in using Docker to make each of these many discrete
> > steps portable to another 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 those
> steps.
> >
> > Either way, we want to know about running Browser+Selenium for
> > sure.  And maybe FlashPlayerDebugger or AIR.  I would want to know, for
> > example, how you debug a failing checkintest in a Docker container.
> >
> > Thanks,
> > -Alex
> >
> >
> > On 2/10/19, 5:18 PM, "OmPrakash Muppirala"  >
> > wrote:
> >
> > Alex,
> >
> > Just to be clear, I am following the steps from here to try
> > and setup a
> > docker container.
> >
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notesdata=02%7C01%7Caharui%40adobe.com%7C9a4f659f80694687c3cd08d6a35b378d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636876009505592396sdata=rJsHtgUQ%2BH5iQOXlZc%2FCEvtxH0Lm25fGn0wlAe6oqSs%3Dreserved=0
> >
> > Is this doc up to date?
> >
> > Thanks,
> > Om
> >
> > On Wed, Feb 6, 2019 at 12:02 PM OmPrakash Muppirala <
> > bigosma...@gmail.com>
> > wrote:
> >
> > > One approach is to have each step in the process spin up a
> > docker image.
> > > And use docker-compose to run each step.  All the images
> can
> > be made to
> > > share a common volume where all the artifacts are stored
> > across steps.
> > >
> > > You are right about the networking issue though.  Any
> > network related
> > > failure that occurs on the host machine will most likely
> > occur in the
> > > docker container.  Although, I am not clear how we can
> > guarantee that the
> > > same issues will not occur on the Jenkins server.  I mean,
> > what is special
> > > about the Jenkins server that makes it immune to these
> > networking issues?
> > >
> > > Thanks,
> > > Om
> > >
> > > On Wed, Feb 6, 2019 at 11:48 AM Alex Harui
> > 
> > > wrote:
> > >
> > >> Again, I don't know anything about Docker, but before we
> > spend a lot of
> > >> time on Docker, I also want to point out that the process
> > to create a
> > >> release cannot really be thought of as "one application".
> > It will be a
> > >> series of "steps" to run.How many steps depends on
> > whether we think we
> > >> can isolate enough stuff via Docker to be able to run
> > Docker on the RM's
> > >> computer instead of some shared computer.  On a shared
> > computer there will
> > >> be dozens of steps because the RM will need to enter
> > passwords to commit
> > >> stuff.  On a local computer I guess the RM can supply
> > passwords but I think
> > >> there will be stopping points where the Maven artifacts
> are
> > deployed and
> > >> the staging repo is closed, and another stopping point for
> > the vote.  It
> > >> seems like Docker works by downloading dependencies.
> Given
> > that the
> > >> problem the RMs had last time involved downloads and
> > uploads, why do we
> > >> think Docker will really solve this for creating releases
> > on local machines?
> > >>
> > >> The reason to do this on a shared machine is so that new
> > RMs don't have
> > >> to do as much setup.  But then I wonder about the
> > efficiency of kicking off
> > >> that many Docker images.  Jenkins can manage that already.
> > Does Docker
> > >> have some sort of similar Dashboard or would we use
> Jenkins
> > to kick off
> > >> Docker steps?  I can't quite picture what is the outermost
> >   

Re: 0.9.6 Release

2019-02-10 Thread OmPrakash Muppirala
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 step in the process spin up a docker image.
> And use docker-compose to run each step.  All the images can be made to
> share a common volume where all the artifacts are stored across steps.
>
> You are right about the networking issue though.  Any network related
> failure that occurs on the host machine will most likely occur in the
> docker container.  Although, I am not clear how we can guarantee that the
> same issues will not occur on the Jenkins server.  I mean, what is special
> about the Jenkins server that makes it immune to these networking issues?
>
> Thanks,
> Om
>
> On Wed, Feb 6, 2019 at 11:48 AM Alex Harui 
> wrote:
>
>> Again, I don't know anything about Docker, but before we spend a lot of
>> time on Docker, I also want to point out that the process to create a
>> release cannot really be thought of as "one application".  It will be a
>> series of "steps" to run.How many steps depends on whether we think we
>> can isolate enough stuff via Docker to be able to run Docker on the RM's
>> computer instead of some shared computer.  On a shared computer there will
>> be dozens of steps because the RM will need to enter passwords to commit
>> stuff.  On a local computer I guess the RM can supply passwords but I think
>> there will be stopping points where the Maven artifacts are deployed and
>> the staging repo is closed, and another stopping point for the vote.  It
>> seems like Docker works by downloading dependencies.  Given that the
>> problem the RMs had last time involved downloads and uploads, why do we
>> think Docker will really solve this for creating releases on local machines?
>>
>> The reason to do this on a shared machine is so that new RMs don't have
>> to do as much setup.  But then I wonder about the efficiency of kicking off
>> that many Docker images.  Jenkins can manage that already.  Does Docker
>> have some sort of similar Dashboard or would we use Jenkins to kick off
>> Docker steps?  I can't quite picture what is the outermost
>> control/dashboard.
>>
>> -Alex
>>
>> On 2/6/19, 11:03 AM, "Harbs"  wrote:
>>
>> A quick search turns up this:
>>
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testingdata=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700sdata=5wwLQFM5nPZtALgsrzdXKMxbBxyenWFhU9EBUojLB5M%3Dreserved=0
>> <
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testingdata=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700sdata=5wwLQFM5nPZtALgsrzdXKMxbBxyenWFhU9EBUojLB5M%3Dreserved=0
>> >
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-dockerdata=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700sdata=2iGtMmdkiH57E2U6SZZ7t7t%2BoyetJ69pMYVmb%2BzO8og%3Dreserved=0
>> <
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-dockerdata=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700sdata=2iGtMmdkiH57E2U6SZZ7t7t%2BoyetJ69pMYVmb%2BzO8og%3Dreserved=0
>> >
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-seleniumdata=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700sdata=XwBOh%2FrpNch5DRWwFCOnYmkJ9EGFumxBuYR9EF7EfTU%3Dreserved=0
>> <
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-seleniumdata=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700sdata=XwBOh%2FrpNch5DRWwFCOnYmkJ9EGFumxBuYR9EF7EfTU%3Dreserved=0
>> >
>>
>> > On Feb 6, 2019, at 8:59 PM, Alex Harui 
>> wrote:
>> >
>> > Thanks for volunteering to try it Om.  IMO, even more important
>> than Firefox+Flash is SomeBrowser+Selenium.  We may also need to run Adobe
>> AIR's adb.  W

Re: 0.9.6 Release

2019-02-06 Thread OmPrakash Muppirala
One approach is to have each step in the process spin up a docker image.
And use docker-compose to run each step.  All the images can be made to
share a common volume where all the artifacts are stored across steps.

You are right about the networking issue though.  Any network related
failure that occurs on the host machine will most likely occur in the
docker container.  Although, I am not clear how we can guarantee that the
same issues will not occur on the Jenkins server.  I mean, what is special
about the Jenkins server that makes it immune to these networking issues?

Thanks,
Om

On Wed, Feb 6, 2019 at 11:48 AM Alex Harui  wrote:

> Again, I don't know anything about Docker, but before we spend a lot of
> time on Docker, I also want to point out that the process to create a
> release cannot really be thought of as "one application".  It will be a
> series of "steps" to run.How many steps depends on whether we think we
> can isolate enough stuff via Docker to be able to run Docker on the RM's
> computer instead of some shared computer.  On a shared computer there will
> be dozens of steps because the RM will need to enter passwords to commit
> stuff.  On a local computer I guess the RM can supply passwords but I think
> there will be stopping points where the Maven artifacts are deployed and
> the staging repo is closed, and another stopping point for the vote.  It
> seems like Docker works by downloading dependencies.  Given that the
> problem the RMs had last time involved downloads and uploads, why do we
> think Docker will really solve this for creating releases on local machines?
>
> The reason to do this on a shared machine is so that new RMs don't have to
> do as much setup.  But then I wonder about the efficiency of kicking off
> that many Docker images.  Jenkins can manage that already.  Does Docker
> have some sort of similar Dashboard or would we use Jenkins to kick off
> Docker steps?  I can't quite picture what is the outermost
> control/dashboard.
>
> -Alex
>
> On 2/6/19, 11:03 AM, "Harbs"  wrote:
>
> A quick search turns up this:
>
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testingdata=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700sdata=5wwLQFM5nPZtALgsrzdXKMxbBxyenWFhU9EBUojLB5M%3Dreserved=0
> <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodingsans.com%2Fblog%2Fselenium-with-docker-testingdata=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700sdata=5wwLQFM5nPZtALgsrzdXKMxbBxyenWFhU9EBUojLB5M%3Dreserved=0
> >
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-dockerdata=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700sdata=2iGtMmdkiH57E2U6SZZ7t7t%2BoyetJ69pMYVmb%2BzO8og%3Dreserved=0
> <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.blazemeter.com%2Fblog%2Fhow-to-run-selenium-tests-in-dockerdata=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700sdata=2iGtMmdkiH57E2U6SZZ7t7t%2BoyetJ69pMYVmb%2BzO8og%3Dreserved=0
> >
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-seleniumdata=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700sdata=XwBOh%2FrpNch5DRWwFCOnYmkJ9EGFumxBuYR9EF7EfTU%3Dreserved=0
> <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSeleniumHQ%2Fdocker-seleniumdata=02%7C01%7Caharui%40adobe.com%7C7ef1e328bfba4963adc108d68c65c25d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636850766018892700sdata=XwBOh%2FrpNch5DRWwFCOnYmkJ9EGFumxBuYR9EF7EfTU%3Dreserved=0
> >
>
> > On Feb 6, 2019, at 8:59 PM, Alex Harui 
> wrote:
> >
> > Thanks for volunteering to try it Om.  IMO, even more important than
> Firefox+Flash is SomeBrowser+Selenium.  We may also need to run Adobe AIR's
> adb.  We could probably turn off the Flash tests 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! :)
> >
> >El mié., 6 feb. 2019 a las 19:31, OmPrakash Muppirala (<
> bigosma...@gmail.com>)
> >escribió:
> >
> >> Yes, I agree with Alex about not be

Re: 0.9.6 Release

2019-02-06 Thread OmPrakash Muppirala
Yes, I agree with Alex about not being able to run UI out of docker
containers.  I never thought of the checkintests when I made the
suggestion.

The firefox-flash image that Yishay pointed out looks promising.  I will
poke around with it and see if that works for us.

Thanks,
Om

On Wed, Feb 6, 2019 at 12:41 AM Yishay Weiss  wrote:

> I’ll let Om or someone else with docker experience tell us if this [1] is
> relevant.
>
>
>
> [1] https://hub.docker.com/r/beli/firefox-flash/
>
>
>
> 
> From: Alex Harui 
> Sent: Wednesday, February 6, 2019 10:05:54 AM
> To: dev@royale.apache.org
> Subject: Re: 0.9.6 Release
>
> I don't anything about docker, but in 15 minutes of reading I ran into
> this:
>
> https://www.channelfutures.com/open-source/when-not-to-use-docker-understanding-the-limitations-of-containers
>
> Which says: Docker can't " Run applications with graphical interfaces".
> If you want Royale to use Docker for releases, show that it can run
> checkintests with Flash and the Browser.  Then I will look into it more.
>
> The highest level goal is to make it as easy as possible for someone to
> volunteer to be an RM.  Any requirement of "install this (Docker, etc) on
> your computer" is, IMO, another barrier to entry.  Yeah, RMs will have to
> have Maven installed and maybe Ant, but you should already have those
> installed to be a committer/PMC member.
>
> That said, a good takeaway from the Docker idea is to try to find a way to
> make an "Image" of whatever we end up with on whatever server we end up
> using so if the image can be copied and used on other servers.  I'm not
> exactly sure how to do that with Azure, which hosts my CI server.  I will
> spend a few more minutes researching that.
>
> I could not quickly find any way to get a free VM on Azure or AWS that
> isn't a free-trial-start-paying-after-a-year.  So, unless someone comes up
> with a free server we can use "forever", I'm going to just start with my
> Azure VM.
>
> -Alex
>
> On 2/5/19, 10:59 PM, "Carlos Rovira"  wrote:
>
> Hi.
>
> the plan sounds very good to me. Just my 2 thoughts on this:
>
> 1.- As I was reading I was thinking as well on something like Docker
> and
> see Om as well thinking on the same. Maybe is the way to this with the
> actual technology. Seems VMs are stepping out a bit this days in favor
> of
> things like Docker. Maybe the same did Git over Svn, and today Svn is
> an
> old remembrance. I must say that I have no experience with Docker, so
> doing
> that will require acquire that knowledge, but seems it could be worth
> it.
>
> 2.- Maybe is not possible, but I want to propose to do this work I a
> separate branch, so it could be in parallel to other developments. I
> think
> work over develop is practical if there's something tiny that could be
> done
> in a commit. But as we need more than one, or is a long process (like
> this), chances are to make develop branch unstable and even for some
> days.
> I 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 ()
> escribió:
>
> > I’ve never used Docker myself, but that might be a good plan.
> >
> > > On Feb 6, 2019, at 12:07 AM, OmPrakash Muppirala <
> bigosma...@gmail.com>
> > wrote:
> > >
> > > 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 
> wrote:
> > >
> > >> In a recent discussion, it looks like other projects have gotten
> > resources
> > >> from AWS.
> > >>
> > >> Whatever service we use, could setup a “shared” Royale account
> that all
> > >> PMC members could have access to.
> > >>
> > >> I don’t know if there’s some way we could leverage Gitlab’s
> integration
> > >> pipelines
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.gitlab.com%2Fee%2Fci%2FREADME.htmldata=02%7C01%7Caharui%40adobe.com%7Cef2b34e531b

Re: 0.9.6 Release

2019-02-05 Thread OmPrakash Muppirala
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  wrote:

> In a recent discussion, it looks like other projects have gotten resources
> from AWS.
>
> Whatever service we use, could setup a “shared” Royale account that all
> PMC members could have access to.
>
> I don’t know if there’s some way we could leverage Gitlab’s integration
> pipelines https://docs.gitlab.com/ee/ci/README.html <
> https://docs.gitlab.com/ee/ci/README.html>
>
> > On Feb 5, 2019, at 11:33 PM, Alex Harui 
> wrote:
> >
> > Well, the big hole in this plan is that I think we have to use someone's
> personal VM account (in this case, mine).  I can't think of a way we can
> run interactive commands like git push on builds@.  But that reminds me
> to go see what are current options are for free/cheap compute servers.
> >
> > On 2/5/19, 1:20 PM, "Piotr Zarzycki"  wrote:
> >
> >Sounds like best plan ever. Using the same PC by everyone is awesome!
> >
> >On Tue, Feb 5, 2019, 8:39 PM Harbs  >
> >> A big +1 from me!
> >>
> >> Looking forward!
> >>
> >>> On Feb 5, 2019, at 9:34 PM, Alex Harui 
> wrote:
> >>>
> >>> Hi,
> >>>
> >>> We are coming up on 3 months since 0.9.4.  I have finished the changes
> >> to get production Royale modules to work in Tour De Flex.  Lots of other
> >> good changes have been contributed.
> >>>
> >>> There were emails around the 0.9.4 release about others stepping up to
> >> cut the next release, but that hasn't happened.  I tried and failed to
> get
> >> Apache Infra to allow us to run our release packaging on the Jenkins
> >> servers.  They felt there were too many security concerns with having
> the
> >> servers push changes to Git and PGP sign artifacts.
> >>>
> >>> However, we MUST find a way for other RMs to be successful.  There is
> no
> >> way I should or want to be the only RM.  But I have an idea that
> involves
> >> creating a long list of Jenkins jobs on my CI server that add up to the
> >> release.  The RM would log into Jenkins and run some job titled "Apache
> >> Royale Release Step 1", then wait for an email indicating that it
> completed
> >> and follow instructions in the email, such as logging into the CI server
> >> via Remote Desktop, opening a command prompt and running "git push" and
> >> entering his/her username and password.  Then run the next job and so
> on.
> >> There will be a point where the RM has to download the build artifacts,
> >> verify them, then PGP sign them, and upload them.  That will be a likely
> >> point of failure, but that step should be a single Maven command and
> thus
> >> can be restarted until it finally succeeds.  Then more Jenkins jobs
> will be
> >> run.  But if this works then folks won't have to setup their computers
> to
> >> be an RM.
> >>>
> >>> So, prepare for lots of commits and reverts as I try to put this
> >> together.  I'm guessing it won't actually work until the last week of
> >> February at the earliest so there is no big rush to get other stuff in
> for
> >> this release, and if we get it to work, hopefully we'll release more
> often
> >> with other folks being the RM.
> >>>
> >>> -Alex
> >>>
> >>
> >>
> >
> >
>
>


Re: BevelFilter

2019-01-09 Thread OmPrakash Muppirala
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 experiment with live images to figure the matrix and tweak it for a
given set of effects.

Some documentation on the feConvolveMatrix:
https://developer.mozilla.org/en-US/docs/Web/SVG/Element/feConvolveMatrix

Hope this helps.

Thanks,
Om

On Wed, Jan 9, 2019 at 11:52 AM Alex Harui  wrote:

> IMO, the parameters in Flash or PS affect the 3D model.  PS might use
> pixel-based edge detection, not sure about Flash.  The key piece is the
> "extrusion".
>
> I would guess that Flash does not control the direction of the extrusion
> while PS does with its "Direction" property.
> In PS, it looks like "depth" is how thick the extrusion is.  That might be
> the same as Flash's "strength".
> In PS, it looks like "size" is the number of pixels of beveling.  That
> might be Flash's "distance".
> PS's "soften" is probably "Flash's "blur".
>
> I think the way it works is, given the outline of a shape, if you had a
> pile of soft bricks of clay, you would:
> -Fill the shape with a layer of bricks.  Put on as many layers of bricks
> as the "depth" or "strength".
> -Based on the depth, look at the "size" or "distance" and remove bricks or
> slice off parts of the bricks along the edge so that the layers of bricks
> don't go straight up, they are angled/beveled.
> -Position your lights of the correct colors.
> -Apply a soften/blur effect on the edges.
>
> HTH,
> -Alex
>
> On 1/9/19, 12:45 AM, "Yishay Weiss"  wrote:
>
> I did skim through that one. What I really wanted was what Anonymous
> asked for in the comments section, but maybe it’s worth trying to implement
> something according to the explanation that’s there and test to see how
> different it is to the flash implementation.
>
>
>
> To answer your other questions, we want to solve the generic problem
> (we’re writing an editor, so we can’t assume users will only use a certain
> shape) for SVG.
>
>
>
> Thanks.
>
>
>
> 
> From: Alex Harui 
> Sent: Wednesday, January 9, 2019 10:24:05 AM
> To: dev@royale.apache.org
> Subject: Re: BevelFilter
>
> This is not my area of expertise at all, but have you seen this?
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rw-designer.com%2Fbevel-effect-explaineddata=02%7C01%7Caharui%40adobe.com%7C5bb8051c78a444adf4e408d6760ecf0c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636826203305954160sdata=xWAx5RmvSCU2hB7ButzRXgogv4B9bemiHm%2BqpNxbvjU%3Dreserved=0
>
> IIRC, there are vector effects, and pixel effects.  Vector effects
> basically alter the vectors that compose the graphic.  Pixel effects
> post-process the drawn pixels.
>
> I think a basic Bevel effect may be a vector effect.  The Flash one
> might require pixel effects as well to implement blur.  The article I
> linked to implies that the basic bevel effect is a 3D modeling problem.  Do
> you have to use SVG or can you use WebGL or some 3D library?
>
> Also consider whether you have to bevel "anything" or something
> simple.  To bevel a rectangular border can be relatively simple, IIRC.
>
> HTH,
> -Alex
>
> On 1/8/19, 11:54 PM, "Yishay Weiss"  wrote:
>
> [1]
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3schools.com%2Fgraphics%2Fsvg_filters_intro.aspdata=02%7C01%7Caharui%40adobe.com%7C5bb8051c78a444adf4e408d6760ecf0c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636826203305954160sdata=KuKtmtrDSwsMIaq4lMkz6b9OomWSHT1YMRZMghNCqb4%3Dreserved=0
>
>
>
> 
> From: Yishay Weiss 
> Sent: Wednesday, January 9, 2019 9:53:32 AM
> To: dev@royale.apache.org
> Subject: RE: BevelFilter
>
> Hi Olaf,
>
>
>
> Well, I was hoping to write a Royale bead rather than use a third
> party library. I’m more interested in the alogorithm used for flash and
> Photoshop, assuming that’s easily translatable to SVG [1] filters.
>
>
>
> Yishay
>
>
>
> 
> From: Olaf Krueger 
> Sent: Tuesday, January 8, 2019 1:55:09 PM
> To: dev@royale.apache.org
> Subject: Re: BevelFilter
>
> Hi Yishay,
> maybe it's worth to give GreenSock/GSAP a try [1][2]?
> They provided a BevelFilterPlugin for AS3, maybe they ported it to
> SVG?
> I am not sure about the license...
>
> Olaf
>
> [1]
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgreensock.com%2Fgsapdata=02%7C01%7Caharui%40adobe.com%7C5bb8051c78a444adf4e408d6760ecf0c%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636826203305954160sdata=1cW23T%2Bt06XyjSQV4gLKoDq1%2FkA1qkT0wx2UOPiossk%3Dreserved=0
>
> [2]
>
> 

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

2018-11-20 Thread OmPrakash Muppirala
On Mon, Nov 19, 2018 at 3:19 PM Alex Harui  wrote:

> IMO, we should just go with 0.9.6. That way we can continue to test the
> release scripts.
>

+1


>
> -Alex
>
> On 11/19/18, 3:17 PM, "Josh Tynjala"  wrote:
>
> You probably don't want to use 0.9.5@next. The @ sign denotes a "tag"
> in the npm registry, and users would need to install that particular
> version of Royale like this:
>
> npm install -g @apache-royale/royale-js@next
>
> Instead of this:
>
> npm install -g @apache-royale/royale-js
>
> 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.
>
> - 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 for
> > now.  (It wouldn't let me publish 0.9.4 because 0.9.5 was already
> there)
> >
> > I suggest that for the next release, we can choose to skip 0.9.5 or
> for NPM
> > alone, we publish it as 0.9.5@next (or something like that)
> >
> > Thanks,
> > Om
> >
> > 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:
> > >
> > > Turns out we can unpublish a version within 72 hours.  Let me
> try to
> > > unpublish 0.9.5 and publish 0.9.4 if that is possible.
> > > Although we still may not be able to publish 0.9.5 next time
> as per the
> > > docs here:
> > >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.npmjs.com%2Fcli%2Funpublishdata=02%7C01%7Caharui%40adobe.com%7Ce0a228debe684196045a08d64e753902%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782662705454521sdata=Clg7YGqIGCNjlYxh00ZJH5356ZnVufWGaZhQjyXqmiI%3Dreserved=0
> > >
> > > Thanks,
> > > Om
> > >
> > > On Mon, Nov 19, 2018 at 9:34 AM Alex Harui
> 
> > > wrote:
> > >
> > > > In the past discussion, I suggested a change to the release
> script
> > > that
> > > > apparently never happened and I did not check to see that it
> > > happened.  I
> > > > have made the suggested change and we'll see if that change
> helps on
> > > the
> > >     > next release.
> > > >
> > > > I think someone could also 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, "OmPrakash Muppirala" <
> bigosma...@gmail.com>
> > > wrote:
> > > >
> > > > 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 <
> harbs.li...@gmail.com>
> > > 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, Alex Harui
> > > 
> > > > > wrote:
> > > > > >
> > > > > > Artifacts have been pushed, but it looks like NPM
> again has
> > > the
> > > > wrong
> > > > > version number.
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
>
>
>


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

2018-11-20 Thread OmPrakash Muppirala
On Mon, Nov 19, 2018 at 3:17 PM Josh Tynjala  wrote:

> You probably don't want to use 0.9.5@next. The @ sign denotes a "tag" in
> the npm registry, and users would need to install that particular version
> of Royale like this:
>
> npm install -g @apache-royale/royale-js@next
>
> Instead of this:
>
> npm install -g @apache-royale/royale-js
>
> 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.
>
>
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
> for
> > now.  (It wouldn't let me publish 0.9.4 because 0.9.5 was already there)
> >
> > I suggest that for the next release, we can choose to skip 0.9.5 or for
> NPM
> > alone, we publish it as 0.9.5@next (or something like that)
> >
> > Thanks,
> > Om
> >
> > 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:
> > >
> > > Turns out we can unpublish a version within 72 hours.  Let me try
> to
> > > unpublish 0.9.5 and publish 0.9.4 if that is possible.
> > > Although we still may not be able to publish 0.9.5 next time as
> per the
> > > docs here:
> > >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.npmjs.com%2Fcli%2Funpublish=02%7C01%7Caharui%40adobe.com%7Cde9e6b6d5418455a3c9108d64e50e5b3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782506692307805=hRImWrDaIU7sOvZW0bxMHpaPyj9U1jGqeYdtBp%2BLe00%3D=0
> > >
> > > Thanks,
> > > Om
> > >
> > > On Mon, Nov 19, 2018 at 9:34 AM Alex Harui
> 
> > > wrote:
> > >
> > > > In the past discussion, I suggested a change to the release
> script
> > > that
> > > > apparently never happened and I did not check to see that it
> > > happened.  I
> > > > have made the suggested change and we'll see if that change
> helps on
> > > the
> > > > next release.
> > > >
> > > > I think someone could also 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, "OmPrakash Muppirala" <
> bigosma...@gmail.com>
> > > wrote:
> > > >
> > > > 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, Alex Harui
> > > 
> > > > > wrote:
> > > > > >
> > > > > > Artifacts have been pushed, but it looks like NPM again
> has
> > > the
> > > > wrong
> > > > > version number.
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
>


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

2018-11-19 Thread OmPrakash Muppirala
Okay, I unpublished 0.9.5 and published 0.9.4.  Looks like we are okay for
now.  (It wouldn't let me publish 0.9.4 because 0.9.5 was already there)

I suggest that for the next release, we can choose to skip 0.9.5 or for NPM
alone, we publish it as 0.9.5@next (or something like that)

Thanks,
Om

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:
>
> Turns out we can unpublish a version within 72 hours.  Let me try to
> unpublish 0.9.5 and publish 0.9.4 if that is possible.
> Although we still may not be able to publish 0.9.5 next time as per the
> docs here:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.npmjs.com%2Fcli%2Funpublishdata=02%7C01%7Caharui%40adobe.com%7Cde9e6b6d5418455a3c9108d64e50e5b3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636782506692307805sdata=hRImWrDaIU7sOvZW0bxMHpaPyj9U1jGqeYdtBp%2BLe00%3Dreserved=0
>
> Thanks,
> Om
>
> On Mon, Nov 19, 2018 at 9:34 AM Alex Harui 
> wrote:
>
> > In the past discussion, I suggested a change to the release script
> that
> > apparently never happened and I did not check to see that it
> happened.  I
> > have made the suggested change and we'll see if that change helps on
> the
> > next release.
> >
> > I think someone could also 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, "OmPrakash Muppirala" 
> wrote:
> >
> > 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, Alex Harui
> 
> > > wrote:
> > > >
> > > > Artifacts have been pushed, but it looks like NPM again has
> the
> > wrong
> > > version number.
> > >
> > >
> >
> >
> >
>
>
>


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

2018-11-19 Thread OmPrakash Muppirala
Turns out we can unpublish a version within 72 hours.  Let me try to
unpublish 0.9.5 and publish 0.9.4 if that is possible.
Although we still may not be able to publish 0.9.5 next time as per the
docs here: https://docs.npmjs.com/cli/unpublish

Thanks,
Om

On Mon, Nov 19, 2018 at 9:34 AM Alex Harui  wrote:

> In the past discussion, I suggested a change to the release script that
> apparently never happened and I did not check to see that it happened.  I
> have made the suggested change and we'll see if that change helps on the
> next release.
>
> I think someone could also 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, "OmPrakash Muppirala"  wrote:
>
> 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, Alex Harui 
> > wrote:
> > >
> > > Artifacts have been pushed, but it looks like NPM again has the
> wrong
> > version number.
> >
> >
>
>
>


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

2018-11-19 Thread OmPrakash Muppirala
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, Alex Harui 
> wrote:
> >
> > Artifacts have been pushed, but it looks like NPM again has the wrong
> version number.
>
>


Re: [VOTE] Release Apache Royale 0.9.4 RC2

2018-11-16 Thread OmPrakash Muppirala
+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 licenses or archives: y

No unapproved binaries: y

On Fri, Nov 16, 2018 at 12:45 AM Harbs  wrote:

> +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.12.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 licenses or archives: y
> No unapproved binaries: y
>
> Package
> https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/binaries/apache-royale-0.9.4-bin-js-swf.tar.gz
> Binary kit signatures match: y
> NOTICE is ok: y
> LICENSE is ok: y
> No unapproved licenses or archives in binary package: y
> No unapproved binaries in binary package: y
>
> Harbs


Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

2018-11-16 Thread OmPrakash Muppirala
Hahaha you set traps to catch lazy ppl.  Although in my defense I checked
everything the first time, but the build failed after that.  The second I
kept hitting enter without reading.  TIL.

Thanks,
Om

On Fri, Nov 16, 2018 at 11:41 AM Alex Harui 
wrote:

> The default answer for some of the rat checks is "n".  So that means you
> can't just hit "Enter" all the way through the script.  I had a good reason
> for doing that, but I can't remember why.  Maybe it was just to make sure
> people were actually looking at the output instead of just hitting Enter.
>
> -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=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fapache-royale-0.9.4-src.tar.gzdata=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185sdata=Tthv90BnjMScTq%2BhUibnA6jkwG4lixaZMcljf1XFFRA%3Dreserved=0
>
> 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 licenses or archives: y
>
> No unapproved binaries: n
>
>
> Package
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.4%2Frc2%2Fbinaries%2Fapache-royale-0.9.4-bin-js-swf.tar.gzdata=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185sdata=tFHKiRf0Q9O1pljLLcak7fweZmV1C%2BZ3n0eEgmtd9R4%3Dreserved=0
>
> Binary kit signatures match: y
>
> NOTICE is ok: y
>
> LICENSE is ok: y
>
> No unapproved licenses or archives in binary package: y
>
> No unapproved binaries in binary package: n
>
>
>
>
> BUILD FAILED
>
> /Users/om/p/os/royale/rc/ApproveRoyale.xml:1103: condition satisfied
>
>
> Looking at the rat report, I do see these files marked as B which
> might be
> causing this?
>
>   B
>
> /Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/favicon.ico
>
>   B
>
> /Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/mx/controls/assets/flexinstaller.mp4
>
>   B
>
> /Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/mx/effects/assets/OpenSans-Regular.ttf
>
>   B
>
> /Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/components/assets/FlexInstaller.mp4
>
>   B
>
> /Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/controls/assets/FlexInstaller.mp4
>
>   B
>
> /Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/tlf/textEditBar/assets/icon_align_end.PNG
>
>   B
>
> /Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/tlf/textEditBar/assets/icon_align_start.PNG
>
> On Fri, Nov 16, 2018 at 11:13 AM Alex Harui 
> wrote:
>
> > Hi Piotr,
> >
> > If you build one of the Royale examples, like
> > examples/royale/DataBindingExample, the POM tries to use artifacts
> from
> > examples-tests.  If you are building your own app, your POM probably
> > doesn't care about examples-tests.
> >
> > Where did you download sources from?
> >
> > When the artifacts are only on the staging server, and not in your
> local
> > repo (by building the entire source package which by default does not
> > include examples), then I think you have to redirect your poms to the
> > staging server.  See:
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fguides%2Fdevelopment%2Fguide-testing-releases.htmldata=02%7C01%7Caharui%40adobe.com%7C8c3cb407a16444958a6608d64bf9caa6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779933553764185sdata=Xu12pHIo1Wk%2B5EolVMSK%2BOgTlkueYL68XbVqBKH0lx4%3Dreserved=0
> >
> > IMO, if you plan to be an RM, you should not be satisfied with a +0
> vote
> > because things are not working for you.  Otherwise, you are just
> set

Re: [DISCUSS] Discuss Release Apache Royale 0.9.4 RC2

2018-11-16 Thread OmPrakash Muppirala
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

RELEASE_NOTES is ok: y

NOTICE is ok: y

LICENSE is ok: y

No unapproved licenses or archives: y

No unapproved binaries: n


Package
https://dist.apache.org/repos/dist/dev/royale/0.9.4/rc2/binaries/apache-royale-0.9.4-bin-js-swf.tar.gz

Binary kit signatures match: y

NOTICE is ok: y

LICENSE is ok: y

No unapproved licenses or archives in binary package: y

No unapproved binaries in binary package: n




BUILD FAILED

/Users/om/p/os/royale/rc/ApproveRoyale.xml:1103: condition satisfied


Looking at the rat report, I do see these files marked as B which might be
causing this?

  B
/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/favicon.ico

  B
/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/mx/controls/assets/flexinstaller.mp4

  B
/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/mx/effects/assets/OpenSans-Regular.ttf

  B
/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/components/assets/FlexInstaller.mp4

  B
/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/controls/assets/FlexInstaller.mp4

  B
/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/tlf/textEditBar/assets/icon_align_end.PNG

  B
/Users/om/p/os/royale/rc/apache-royale-0.9.4-bin-js-swf/royale-asjs/examples/mxroyale/tourdeflexmodules/src/spark/tlf/textEditBar/assets/icon_align_start.PNG

On Fri, Nov 16, 2018 at 11:13 AM Alex Harui 
wrote:

> Hi Piotr,
>
> If you build one of the Royale examples, like
> examples/royale/DataBindingExample, the POM tries to use artifacts from
> examples-tests.  If you are building your own app, your POM probably
> doesn't care about examples-tests.
>
> Where did you download sources from?
>
> When the artifacts are only on the staging server, and not in your local
> repo (by building the entire source package which by default does not
> include examples), then I think you have to redirect your poms to the
> staging server.  See:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> IMO, if you plan to be an RM, you should not be satisfied with a +0 vote
> because things are not working for you.  Otherwise, you are just setting
> yourself up for others to be in the same situation and when you are the RM,
> you will get a bunch of +0 votes.
>
> Thanks,
> -Alex
>
> On 11/16/18, 10:53 AM, "Piotr Zarzycki" 
> wrote:
>
> Hi Alex,
>
> Once my build failed with that timeout I went to downloaded sources
> directly in order to run Maven build and see whether it's working. I
> was
> able to build it - with similar issue as other with airglobal. - I have
> manually add that part to my Maven cache.
>
> Part 2 of the test was simply build example using your staged
> artifacts -
> It doesn't connected whether I build examples/examples-tests or not -
> Am I
> wrong? Let's imagine that I have clean machine, created Royale project
> -
> I'm trying to build my project with Maven and your artifacts - Do I
> need
> that org.apache.royale.examples:examples-tests:jar ?
>
> If answer is NO - That's ok - it is an requirements for build our
> example
> and I can vote +0.
>
> *Please verify that FlexUnit is working in your repo and then compare
> the
> FlexUnit jars it is using against the ones that the RC downloaded.  Or
> investigate the difference between the SWFs generated by the repo
> build vs
> the RC build.  If we don't figure out why things fail, then we are
> doomed
> to keep hitting these failure points.  *
>
> Above part requires from me a lot of time probably - If I found it
> before
> to be next RM I will do this for sure.
>
> Piotr
>
> pt., 16 lis 2018 o 19:10 Alex Harui 
> napisał(a):
>
> > Piotr,
> >
> > Did you build the examples/examples-tests folder first?
> >
> > If you used the ApproveRoyale script then it would have done all of
> that
> > for you.  If you plan to be an RM, it is worth your time to find out
> why
> > the approval script is not working for you, as it is expected that
> the RM
> > has run the approval script before posting the vote threads in order
> to
> > save everyone time.
> >
> > Please verify that FlexUnit is working in your repo and then compare
> the
> > FlexUnit jars it is using against the ones that the RC downloaded.
> Or
> > investigate the difference between the SWFs generated by 

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

2018-11-15 Thread OmPrakash Muppirala
On Thu, Nov 15, 2018 at 2:02 AM Alex Harui  wrote:

> To be clear:  the process DOES NOT upload artifacts to Maven Central.  It
> uploads to the ASF staging repo.  Only after we approve the release do the
> artifacts get pushed to Maven Central.  One of the RMs got an error
> DOWNLOADING a Maven plugin from Maven Central.  There is nothing wrong with
> doing that.
>

Sorry, I misspoke.  But the question remains.  Why do we need to upload it
to the staging server during building or testing a release candidate?  Can
we not just use the local m2 repository for this?

In other words, what aspect of the release are we actually testing by
uploading stuff to the staging repo?



>
> Any volunteer is welcome to re-do the release scripts.  What we have now
> is what I think was the simplest sequence for creating both Maven and
> non-Maven artifacts.  Maven was the number 1 asked for feature in Adobe
> Flex.  IIRC, it had 100 votes and 2nd place was 12 votes.  So we support
> Maven in hopes that the customers we want to attract are using Maven, plus
> at least Carlos prefers to use Maven.
>
> Just like any other code or script in Royale, there can be bugs and room
> for improvement in the release process.  I found and fixed some issues, and
> hopefully the next RM will try the scripts after a month or so instead of 6
> months so fewer things will have become stale and broken.  In fact,  I
> think I will say that RC2 is my last RC for a while.  If we need an RC3,
> someone else should create it since the know the scripts recently worked
> for me.  And since it is fresh in my mind, I might be able to help the next
> RM better.  I think the problems Piotr and Yishay hit have been addressed.
> The only remaining 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
> 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 dont force maven on folks who dont need it.
>
> Thoughts?
>
> Thanks,
> Om
>
>
>
> On Wed, Nov 14, 2018 at 12:54 PM Carlos Rovira <
> carlosrov...@apache.org>
> wrote:
>
> > Hi Alex,
> >
> > first congrats to reach to this point. After many months is great to
> > finally can release :)
> >
> > I forked the thread to avoid mixing topics and let the discuss
> thread to
> > just discuss the RC2
> >
> > I'll try RC2 soon, but first I want to talk about the inherent
> problem. I
> > know we are all here making a huge effort to make Royale work and
> shine,
> > and be release manager is to spend many hours working in that task,
> so
> > first I want to express as well a huge recognition to all RMs that
> tried to
> > make this happen before you. I still didn't try to make myself a
> release,
> > so I'm talking without the knowledge you all guys have, so sorry if
> I say
> > something inconvenient now, but just want to talk about the elephant
> in the
> > room, so we can improve the process from now own.
> >
> > My perception, from a person that is still outside the release
> process,
> > still does not have all the knowledge and never was a RM is that the
> > process is not reliable. Again hope nobody feels that talk about
> this is
> > any kind of attack, just that if we agree on that, we could try to
> improve
> > for the better. Right now seems that only Alex can make a release
> happen
> > due to his machine configuration. I assume all RMs execute the RM
> > instructions, so the problem is not related to the instructions, but
> seems
> > more to the nature of how we build.
> >
> > So, my question is, what we could change to ensure scripts and
> process are
> > reliable in all machines and doable by any of us?
> > Is the process a mix of maven and ant what is making this so hard to
> do?
> > Just a comment, could be the nature of ant (more single separated
> scripting
> > based on computer environment config vs structured building based on
> > building framework and servers) a problem?
> >
> > I want to be a RM soon (hope to be available for this task around
> Feb-Mar
> > 2019), so its clear

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

2018-11-14 Thread OmPrakash Muppirala
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 dont force maven on folks who dont need it.

Thoughts?

Thanks,
Om



On Wed, Nov 14, 2018 at 12:54 PM Carlos Rovira 
wrote:

> Hi Alex,
>
> first congrats to reach to this point. After many months is great to
> finally can release :)
>
> I forked the thread to avoid mixing topics and let the discuss thread to
> just discuss the RC2
>
> I'll try RC2 soon, but first I want to talk about the inherent problem. I
> know we are all here making a huge effort to make Royale work and shine,
> and be release manager is to spend many hours working in that task, so
> first I want to express as well a huge recognition to all RMs that tried to
> make this happen before you. I still didn't try to make myself a release,
> so I'm talking without the knowledge you all guys have, so sorry if I say
> something inconvenient now, but just want to talk about the elephant in the
> room, so we can improve the process from now own.
>
> My perception, from a person that is still outside the release process,
> still does not have all the knowledge and never was a RM is that the
> process is not reliable. Again hope nobody feels that talk about this is
> any kind of attack, just that if we agree on that, we could try to improve
> for the better. Right now seems that only Alex can make a release happen
> due to his machine configuration. I assume all RMs execute the RM
> instructions, so the problem is not related to the instructions, but seems
> more to the nature of how we build.
>
> So, my question is, what we could change to ensure scripts and process are
> reliable in all machines and doable by any of us?
> Is the process a mix of maven and ant what is making this so hard to do?
> Just a comment, could be the nature of ant (more single separated scripting
> based on computer environment config vs structured building based on
> building framework and servers) a problem?
>
> I want to be a RM soon (hope to be available for this task around Feb-Mar
> 2019), so its clear I still can say a word about the process just start
> this thread and hoping no one feels this as an attack (since I recognize
> the huge effort done to reach this point), but just a way to start trying
> to think with open mind and see that we have at least a thing to solve so
> any of us can make the same as Alex do
>
> Thanks in advance for your thoughts :)
>
> Carlos
>
>
>
>
>
> El mié., 14 nov. 2018 a las 19:46, Alex Harui ()
> escribió:
>
> > This is the discussion thread.   RC1 was never put up for vote because
> > there
> > were issues with the notice files and build scripts when running from the
> > packages and not the repo.
> >
> > Interestingly, the scripts ran just fine for me on my home Windows
> > computer.
> > I did not have the problems Om, Piotr, and Yishay had when uploading or
> > downloading Maven artifacts.  Except when I tried watching videos while
> > waiting for the scripts to run (the "maven" target takes 2 hours in
> > Powershell, the "main" target took over an hour).   Then I would see
> > uploads
> > "hang".   So I would recommend to any future RMs to try to make sure the
> > network is not otherwise too busy when running these scripts.
> >
> > Changes in this RC include:
> >
> >
> >
> > Thanks,
> > Alex Harui
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


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

2018-10-04 Thread OmPrakash Muppirala
On Thu, Oct 4, 2018 at 1:48 AM Alex Harui  wrote:

> Om, it looks like you are still deleting and recreating the branches.
> Does this mean you have never completed the make_branches step?


Yes, I delete the tags, branches (remote) each time something fails.  Then
I do a global search for 0.9.5 and replace it with 0.9.4 (some 200+ files
across 3 repos), then push them into remote/develop.

Then I do the make_branches step first.  Then do a git push in roayale-asjs
as per the instructions in the commandline. I have never had issues with
this step.  It is always the maven step that fails for some reason or the
other.


> Is make_branches failing trying to run a build in the develop branch and
> uploading 0.9.5-SNAPSHOT artifacts?


No


> I supposed we could try to find a way to skip that, but you will need
> reliable uploading to repository.a.o to be an RM without going crazy.
>

Hmm, I use the same internet connection for personal and work related
activities.  I don't usually have issues with internet.  Either we are very
unlucky here or we need a more reselient way to pick up things if we lose
internet connectivity momentarily.

It takes upwards of 90 minutes 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 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 is attempted to
> > deploy?  I found this article that might help:
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.apigee.com%2Fquestions%2F50756%2Funable-to-deploy-using-maven-script-due-to-error-r.htmldata=02%7C01%7Caharui%40adobe.com%7Cf53d1f8543df4d1a82a808d62974c4fa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741978831424956sdata=rrkMaSLxamQGHfveBJZ6FMMAj9KQY3BxQlOUc4gd2io%3Dreserved=0
>
>
> It deployed a lot of artifacts before hitting this error.  I don't see
> anything special with this artifact.  So, I am guessing that it was a
> momentary bad connection that caused this.
>
>
> >
> >
> > I would be concerned about restarting from the middle of a Maven
> call.  I
> > suppose you could try it, but what if it skipped an artifact?
> >
>
> The maven error message explicitly says this:
>
>  [exec] [INFO] [ERROR] After correcting the problems, you can
> resume
> the build with the command
>
>  [exec] [INFO] [ERROR]   mvn  -rf
> :Jewel-Light-NoFlat-Primary-Sunflower-Theme
>
>
> >
> > 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 after
> > everything is done locally?  That way, if something goes wrong
> > halfway, we
>     > can just delete the royale-* dirs locally and rerun the
> > releasecandiate ant
> > script?
> >
> > Not sure if this is an easy change?
> >
> > Thanks,
> > Om
> >
> > On Wed, Oct 3, 2018 at 11:42 AM OmPrakash Muppirala <
> > bigosma...@gmail.com>
> > wrote:
> >
> > > Okay, I tried a couple of times and I have started getting
> `SSL peer
> > shut
> > > down incorrectly errors`
> > >
> > >  [exec] [INFO] [INFO]
> > >
> >
> 
> > >
> > >  [exec] [INFO] [INFO] BUILD FAILURE
> > >
> > >  [exec] [INFO] [INFO]
> > >
> >
> 
> > >
> > >  [exec] [INFO] [INFO] Total time: 16:04 min
> > >
> > >  [exec] [INFO] [INFO] Finished at:
> 2018-10-03T11:38:49-07:00
> > >
> > >  [exec] [INFO] [INFO]
> > >
> >
> 
> > >
> > >  [exec] [INFO] [ERROR] Failed to execute goal
> > > 

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

2018-10-04 Thread OmPrakash Muppirala
On Thu, Oct 4, 2018 at 9:33 AM Alex Harui  wrote:

> Om,
>
> What version of Java are you using?  Maven uses Java and maybe there is an
> incompatibility in the server communication layer of Java.
>

OmPrakashs-MacBook-Pro:release om$ java -version

java version "1.8.0_181"

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 (at work)
>
>
> On Thu, Oct 4, 2018 at 1:09 AM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> wrote:
>
> > Neverending story ;) What's your internet connection actually?
> >
> > On Thu, Oct 4, 2018, 10:04 AM OmPrakash Muppirala <
> bigosma...@gmail.com>
> > wrote:
> >
> > > Hmm, failed again at a different spot:
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > > Jewel-Dark-NoFlat-Emphasized-Sunflower-Theme SUCCESS [ 22.251 s]
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > > Jewel-Dark-NoFlat-Emphasized-Topaz-Theme SUCCESS [ 18.741 s]
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > > Jewel-Dark-NoFlat-Emphasized-Turquoise-Theme SUCCESS [ 18.421 s]
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > > Jewel-Dark-NoFlat-Emphasized-Violet-Theme FAILURE [ 31.354 s]
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > > Jewel-Dark-NoFlat-Emphasized-Yellow-Theme SKIPPED
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes
> > > ... SKIPPED
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes:
> Simple
> > > Royale Application SKIPPED
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes:
> Simple
> > > Royale Pure-JS Application SKIPPED
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes:
> Simple
> > > Royale Pure-SWF Application SKIPPED
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes:
> Simple
> > > Royale Library SKIPPED
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes:
> Simple
> > > Royale Typedef Library 0.9.4 SKIPPED
> > >
> > >  [exec] [INFO] [INFO]
> > >
> 
> > >
> > >  [exec] [INFO] [INFO] BUILD FAILURE
> > >
> > >  [exec] [INFO] [INFO]
> > >
> 
> > >
> > >  [exec] [INFO] [INFO] Total time: 38:52 min
> > >
> > >  [exec] [INFO] [INFO] Finished at: 2018-10-04T00:50:41-07:00
> > >
> > >  [exec] [INFO] [INFO]
> > >
> 
> > >
> > >  [exec] [INFO] [ERROR] Failed to execute goal
> > > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> > (default-deploy)
> > > on project Jewel-Dark-NoFlat-Emphasized-Violet-Theme: Failed to
> deploy
> > > artifacts: Could not transfer artifact
> > >
> > >
> >
> org.apache.royale.framework:Jewel-Dark-NoFlat-Emphasized-Violet-Theme:swc.asc:typedefs:0.9.4
> > > from/to apache.releases.https (
> > >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fservice%2Flocal%2Fstaging%2Fdeploy%2Fmaven2data=02%7C01%7Caharui%40adobe.com%7C4113dbce443a4bcbba0008d629d161c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636742376597410393sdata=%2FA5wGdk8cvC23pci3FUR9nEW%2FBsBGPMyyBa%2BlIxnr3s%3Dreserved=0
> ):
> > > Connect
> > > to repository.apache.org:443 [repository.apache.org/207.244.88.140
> ]
> > > failed:
> > > Operation timed out (Connection timed out) -> [Help 1]
> > >
> > >  [exec] [INFO] [ERROR]
> > >
> > >  [exec] [INFO] [ERROR] To see the full stack trace of the
> errors,
> > > re-run Maven with the -e switch.
&

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

2018-10-04 Thread OmPrakash Muppirala
I am curious about why we are uploading example swcs to maven central.
What is the usecase?

Thanks,
Om


On Thu, Oct 4, 2018, 2:26 AM Alex Harui  wrote:

> We are using both Maven and Ant to create releases.  Some of our users
> prefer Maven others prefer Ant.  Best way to make sure both work is to use
> Maven for Maven and Ant for Ant.
>
> I don't know if is really Maven that is failing or just something wrong
> with Om's internet connection.
>
> -Alex
>
> On 10/4/18, 2:10 AM, "Carlos Rovira"  wrote:
>
> Hi Harbs,
>
> for me Maven is not easier, seems as difficult as ANT. For me the
> points
> for maven is the reliability and robustness of the build process and
> the
> management of dependencies. ANT was the first step for me, and I always
> liked, but the problems was that it was more a way to script than
> something
> that follows a protocol and manage the download of packages (and ensure
> that package are the exact bits you need).
>
> We have a use case when build the SDK with ANT in Royale. You and Alex
> gets
> flexunit and uses the as3 swc. Erik and I do the same and we end using
> the
> flex swc. Why? This is cause is all hand made script and probably we
> have
> some configuration differences in our environments that make the script
> behave different. The fact is that I still could not find the black
> point
> after some hours of digging.
>
> This is something that should not happen in Maven (well, you always can
> make maven do things badly as with any technology). Maven as all
> tools, can
> make things more or less easy, but once you have the things correctly
> setup
> should manage all the needed dependencies and be more reliable in all
> environments. But don't expect to be more easy than working with ANT,
> since
> for a project with the size of Royale both build systems are complex.
>
> Just my 2
>
>
> El jue., 4 oct. 2018 a las 10:24, Harbs ()
> escribió:
>
> > Can I ask a dumb question?
> >
> > Why are we using Maven for release? The argument I’ve always heard
> is that
> > Maven is easier. This doesn’t seem easy… ;-)
> >
> > 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:04 AM OmPrakash Muppirala <
> bigosma...@gmail.com>
> > > wrote:
> > >
> > >> Hmm, failed again at a different spot:
> > >>
> > >> [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > >> Jewel-Dark-NoFlat-Emphasized-Sunflower-Theme SUCCESS [ 22.251 s]
> > >>
> > >> [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > >> Jewel-Dark-NoFlat-Emphasized-Topaz-Theme SUCCESS [ 18.741 s]
> > >>
> > >> [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > >> Jewel-Dark-NoFlat-Emphasized-Turquoise-Theme SUCCESS [ 18.421 s]
> > >>
> > >> [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > >> Jewel-Dark-NoFlat-Emphasized-Violet-Theme FAILURE [ 31.354 s]
> > >>
> > >> [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > >> Jewel-Dark-NoFlat-Emphasized-Yellow-Theme SKIPPED
> > >>
> > >> [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes
> > >> ... SKIPPED
> > >>
> > >> [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes:
> Simple
> > >> Royale Application SKIPPED
> > >>
> > >> [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes:
> Simple
> > >> Royale Pure-JS Application SKIPPED
> > >>
> > >> [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes:
> Simple
> > >> Royale Pure-SWF Application SKIPPED
> > >>
> > >> [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes:
> Simple
> > >> Royale Library SKIPPED
> > >>
> > >> [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes:
> Simple
> > >> Royale Typedef Library 0.9.4 SKIPPED
> > >>
> > >> [exec] [INFO] [INFO]
> > >>
> -

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

2018-10-04 Thread OmPrakash Muppirala
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 again at a different spot:
> >
> >  [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > Jewel-Dark-NoFlat-Emphasized-Sunflower-Theme SUCCESS [ 22.251 s]
> >
> >  [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > Jewel-Dark-NoFlat-Emphasized-Topaz-Theme SUCCESS [ 18.741 s]
> >
> >  [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > Jewel-Dark-NoFlat-Emphasized-Turquoise-Theme SUCCESS [ 18.421 s]
> >
> >  [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > Jewel-Dark-NoFlat-Emphasized-Violet-Theme FAILURE [ 31.354 s]
> >
> >  [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
> > Jewel-Dark-NoFlat-Emphasized-Yellow-Theme SKIPPED
> >
> >  [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes
> > ... SKIPPED
> >
> >  [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes: Simple
> > Royale Application SKIPPED
> >
> >  [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes: Simple
> > Royale Pure-JS Application SKIPPED
> >
> >  [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes: Simple
> > Royale Pure-SWF Application SKIPPED
> >
> >  [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes: Simple
> > Royale Library SKIPPED
> >
> >  [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes: Simple
> > Royale Typedef Library 0.9.4 SKIPPED
> >
> >  [exec] [INFO] [INFO]
> > 
> >
> >  [exec] [INFO] [INFO] BUILD FAILURE
> >
> >  [exec] [INFO] [INFO]
> > 
> >
> >  [exec] [INFO] [INFO] Total time: 38:52 min
> >
> >  [exec] [INFO] [INFO] Finished at: 2018-10-04T00:50:41-07:00
> >
> >  [exec] [INFO] [INFO]
> > 
> >
> >  [exec] [INFO] [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy)
> > on project Jewel-Dark-NoFlat-Emphasized-Violet-Theme: Failed to deploy
> > artifacts: Could not transfer artifact
> >
> >
> org.apache.royale.framework:Jewel-Dark-NoFlat-Emphasized-Violet-Theme:swc.asc:typedefs:0.9.4
> > from/to apache.releases.https (
> > https://repository.apache.org/service/local/staging/deploy/maven2):
> > Connect
> > to repository.apache.org:443 [repository.apache.org/207.244.88.140]
> > failed:
> > Operation timed out (Connection timed out) -> [Help 1]
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] To see the full stack trace of the errors,
> > re-run Maven with the -e switch.
> >
> >  [exec] [INFO] [ERROR] Re-run Maven using the -X switch to enable
> full
> > debug logging.
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] For more information about the errors and
> > possible solutions, please read the following articles:
> >
> >  [exec] [INFO] [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] After correcting the problems, you can resume
> > the build with the command
> >
> >  [exec] [INFO] [ERROR]   mvn  -rf
> > :Jewel-Dark-NoFlat-Emphasized-Violet-Theme
> >
> >  [exec] [INFO]
> > 
> >
> > 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 is attempted to
> > >> deploy?  I found this article that might help:
> > >>
> > >>
> >
> https://community.apigee.com/questions/50756/unable-to-deploy-using-maven-script-due-to-error-r.html
> > >
> > >
> > > It deployed a lot of artifacts before hitting this error.  I don't see
> > > anything special with this artifact.  So, I am guessing 

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

2018-10-04 Thread OmPrakash Muppirala
Hmm, failed again at a different spot:

 [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
Jewel-Dark-NoFlat-Emphasized-Sunflower-Theme SUCCESS [ 22.251 s]

 [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
Jewel-Dark-NoFlat-Emphasized-Topaz-Theme SUCCESS [ 18.741 s]

 [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
Jewel-Dark-NoFlat-Emphasized-Turquoise-Theme SUCCESS [ 18.421 s]

 [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
Jewel-Dark-NoFlat-Emphasized-Violet-Theme FAILURE [ 31.354 s]

 [exec] [INFO] [INFO] Apache Royale: Framework: Themes:
Jewel-Dark-NoFlat-Emphasized-Yellow-Theme SKIPPED

 [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes
... SKIPPED

 [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes: Simple
Royale Application SKIPPED

 [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes: Simple
Royale Pure-JS Application SKIPPED

 [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes: Simple
Royale Pure-SWF Application SKIPPED

 [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes: Simple
Royale Library SKIPPED

 [exec] [INFO] [INFO] Apache Royale: Framework: Archetypes: Simple
Royale Typedef Library 0.9.4 SKIPPED

 [exec] [INFO] [INFO]


 [exec] [INFO] [INFO] BUILD FAILURE

 [exec] [INFO] [INFO]


 [exec] [INFO] [INFO] Total time: 38:52 min

 [exec] [INFO] [INFO] Finished at: 2018-10-04T00:50:41-07:00

 [exec] [INFO] [INFO]


 [exec] [INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
on project Jewel-Dark-NoFlat-Emphasized-Violet-Theme: Failed to deploy
artifacts: Could not transfer artifact
org.apache.royale.framework:Jewel-Dark-NoFlat-Emphasized-Violet-Theme:swc.asc:typedefs:0.9.4
from/to apache.releases.https (
https://repository.apache.org/service/local/staging/deploy/maven2): Connect
to repository.apache.org:443 [repository.apache.org/207.244.88.140] failed:
Operation timed out (Connection timed out) -> [Help 1]

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] To see the full stack trace of the errors,
re-run Maven with the -e switch.

 [exec] [INFO] [ERROR] Re-run Maven using the -X switch to enable full
debug logging.

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] For more information about the errors and
possible solutions, please read the following articles:

 [exec] [INFO] [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] After correcting the problems, you can resume
the build with the command

 [exec] [INFO] [ERROR]   mvn  -rf
:Jewel-Dark-NoFlat-Emphasized-Violet-Theme

 [exec] [INFO]


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 is attempted to
>> deploy?  I found this article that might help:
>>
>> https://community.apigee.com/questions/50756/unable-to-deploy-using-maven-script-due-to-error-r.html
>
>
> It deployed a lot of artifacts before hitting this error.  I don't see
> anything special with this artifact.  So, I am guessing that it was a
> momentary bad connection that caused this.
>
>
>>
>>
>> I would be concerned about restarting from the middle of a Maven call.  I
>> suppose you could try it, but what if it skipped an artifact?
>>
>
> The maven error message explicitly says this:
>
>  [exec] [INFO] [ERROR] After correcting the problems, you can resume
> the build with the command
>
>  [exec] [INFO] [ERROR]   mvn  -rf
> :Jewel-Light-NoFlat-Primary-Sunflower-Theme
>
>
>>
>> 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
>> after
>> everything is done locally?  That way, if something goes wrong
>> halfway, we
>> can just delete the royale-* dirs locally and rerun the
>> releasecandiate ant
>> script?
>>
>> Not sure if this is an easy change?
>>
>> Thanks,
>> Om
>>
>> On Wed, Oct 3, 2018 at 11:42 AM OmPrakash Muppirala <
>> bigosma...@gmail.com>
>> wrote:
&g

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

2018-10-03 Thread OmPrakash Muppirala
On Wed, Oct 3, 2018 at 2:02 PM Alex Harui  wrote:

> Hi Om,
>
> Does anything deploy, or is that the first thing that is attempted to
> deploy?  I found this article that might help:
>
> https://community.apigee.com/questions/50756/unable-to-deploy-using-maven-script-due-to-error-r.html


It deployed a lot of artifacts before hitting this error.  I don't see
anything special with this artifact.  So, I am guessing that it was a
momentary bad connection that caused this.


>
>
> I would be concerned about restarting from the middle of a Maven call.  I
> suppose you could try it, but what if it skipped an artifact?
>

The maven error message explicitly says this:

 [exec] [INFO] [ERROR] After correcting the problems, you can resume
the build with the command

 [exec] [INFO] [ERROR]   mvn  -rf
:Jewel-Light-NoFlat-Primary-Sunflower-Theme


>
> 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 after
> everything is done locally?  That way, if something goes wrong
> halfway, we
> can just delete the royale-* dirs locally and rerun the
> releasecandiate ant
> script?
>
> Not sure if this is an easy change?
>
> Thanks,
> Om
>
> On Wed, Oct 3, 2018 at 11:42 AM OmPrakash Muppirala <
> bigosma...@gmail.com>
> wrote:
>
> > Okay, I tried a couple of times and I have started getting `SSL peer
> shut
> > down incorrectly errors`
> >
> >  [exec] [INFO] [INFO]
> >
> 
> >
> >  [exec] [INFO] [INFO] BUILD FAILURE
> >
> >  [exec] [INFO] [INFO]
> >
> 
> >
> >  [exec] [INFO] [INFO] Total time: 16:04 min
> >
> >  [exec] [INFO] [INFO] Finished at: 2018-10-03T11:38:49-07:00
> >
> >  [exec] [INFO] [INFO]
> >
> 
> >
> >  [exec] [INFO] [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy)
> > on project Jewel-Light-NoFlat-Primary-Sunflower-Theme: Failed to
> deploy
> > artifacts: Could not transfer artifact
> >
> org.apache.royale.framework:Jewel-Light-NoFlat-Primary-Sunflower-Theme:swc:0.9.4
> > from/to apache.releases.https (
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fservice%2Flocal%2Fstaging%2Fdeploy%2Fmaven2data=02%7C01%7Caharui%40adobe.com%7Cf27e84867a5440c6809008d62962338f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741899088254161sdata=vzyO7Stsj3pqyE9Sih32heK62GABKGZo0wlgWpxW0bE%3Dreserved=0
> ):
> > Remote host closed connection during handshake: SSL peer shut down
> > incorrectly -> [Help 1]
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] To see the full stack trace of the errors,
> > re-run Maven with the -e switch.
> >
> >  [exec] [INFO] [ERROR] Re-run Maven using the -X switch to enable
> > full debug logging.
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] For more information about the errors and
> > possible solutions, please read the following articles:
> >
> >  [exec] [INFO] [ERROR] [Help 1]
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionExceptiondata=02%7C01%7Caharui%40adobe.com%7Cf27e84867a5440c6809008d62962338f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741899088254161sdata=RU7b9uJt%2FtsXJiX376HgIqRTvKoiKZcs7Z%2Flr1b4wO8%3Dreserved=0
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] After correcting the problems, you can
> resume
> > the build with the command
> >
> >  [exec] [INFO] [ERROR]   mvn  -rf
> > :Jewel-Light-NoFlat-Primary-Sunflower-Theme
> >
> >  [exec] [INFO]
> >
> 
> >
> >
> > I am guessing it is a bad internet connection.  I am wondering if we
> can
> > pass a -rf (resume from) option to the maven call from ant?
> Otherwis

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

2018-10-03 Thread OmPrakash Muppirala
Another suggestion I have is - can we do all the pushes to remote after
everything is done locally?  That way, if something goes wrong halfway, we
can just delete the royale-* dirs locally and rerun the releasecandiate ant
script?

Not sure if this is an easy change?

Thanks,
Om

On Wed, Oct 3, 2018 at 11:42 AM OmPrakash Muppirala 
wrote:

> Okay, I tried a couple of times and I have started getting `SSL peer shut
> down incorrectly errors`
>
>  [exec] [INFO] [INFO]
> 
>
>  [exec] [INFO] [INFO] BUILD FAILURE
>
>  [exec] [INFO] [INFO]
> 
>
>  [exec] [INFO] [INFO] Total time: 16:04 min
>
>  [exec] [INFO] [INFO] Finished at: 2018-10-03T11:38:49-07:00
>
>  [exec] [INFO] [INFO]
> 
>
>  [exec] [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
> on project Jewel-Light-NoFlat-Primary-Sunflower-Theme: Failed to deploy
> artifacts: Could not transfer artifact
> org.apache.royale.framework:Jewel-Light-NoFlat-Primary-Sunflower-Theme:swc:0.9.4
> from/to apache.releases.https (
> https://repository.apache.org/service/local/staging/deploy/maven2):
> Remote host closed connection during handshake: SSL peer shut down
> incorrectly -> [Help 1]
>
>  [exec] [INFO] [ERROR]
>
>  [exec] [INFO] [ERROR] To see the full stack trace of the errors,
> re-run Maven with the -e switch.
>
>  [exec] [INFO] [ERROR] Re-run Maven using the -X switch to enable
> full debug logging.
>
>  [exec] [INFO] [ERROR]
>
>  [exec] [INFO] [ERROR] For more information about the errors and
> possible solutions, please read the following articles:
>
>  [exec] [INFO] [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>
>  [exec] [INFO] [ERROR]
>
>  [exec] [INFO] [ERROR] After correcting the problems, you can resume
> the build with the command
>
>  [exec] [INFO] [ERROR]   mvn  -rf
> :Jewel-Light-NoFlat-Primary-Sunflower-Theme
>
>  [exec] [INFO]
> 
>
>
> I am guessing it is a bad internet connection.  I am wondering if we can
> pass a -rf (resume from) option to the maven call from ant?  Otherwise
> doing all this from scratch everytime is a big pain.
>
> Thanks,
> Om
>
> On Wed, Oct 3, 2018 at 12:47 AM Alex Harui 
> wrote:
>
>> Looks like it was a missing [
>>
>> MXRoyale and SparkRoyale built for me.
>>
>> HTH,
>> -Alex
>>
>> On 10/3/18, 12:43 AM, "OmPrakash Muppirala" 
>> wrote:
>>
>> Thanks!
>>
>> I reverted everything back to previous state.  I can give it a shot
>> tomorrow evening.
>>
>> Regards,
>> Om
>>
>> On Wed, Oct 3, 2018 at 12:41 AM Alex Harui 
>> wrote:
>>
>> > It was in a releasable state.  TourDeFlex was running on it.
>> >
>> > I'm trying to track down the change that broke it.
>> >
>> > -Alex
>> >
>> > On 10/3/18, 12:32 AM, "OmPrakash Muppirala" 
>> wrote:
>> >
>> > A bit more progress. Now we are failing on the MXRoyale project:
>> >
>> >  [exec] [INFO] [INFO]
>> >
>> >
>> 
>> >
>> >  [exec] [INFO] [INFO] BUILD FAILURE
>> >
>> >  [exec] [INFO] [INFO]
>> >
>> >
>> 
>> >
>> >  [exec] [INFO] [INFO] Total time: 01:34 min
>> >
>> >  [exec] [INFO] [INFO] Finished at: 2018-10-03T00:28:14-07:00
>> >
>> >  [exec] [INFO] [INFO]
>> >
>> >
>> 
>> >
>> >  [exec] [INFO] [ERROR] Failed to execute goal
>> > org.apache.royale.compiler:royale-maven-plugin:0.9.4:compile-as
>> > (default-compile-as) on project MXRoyale: There were errors
>> during the
>> > build. Got return code 3 -> [Help 1]
>> >
>> >  [exec] [INFO] [ERROR]
>> >
>> >  [exec] 

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

2018-10-03 Thread OmPrakash Muppirala
Okay, I tried a couple of times and I have started getting `SSL peer shut
down incorrectly errors`

 [exec] [INFO] [INFO]


 [exec] [INFO] [INFO] BUILD FAILURE

 [exec] [INFO] [INFO]


 [exec] [INFO] [INFO] Total time: 16:04 min

 [exec] [INFO] [INFO] Finished at: 2018-10-03T11:38:49-07:00

 [exec] [INFO] [INFO]


 [exec] [INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
on project Jewel-Light-NoFlat-Primary-Sunflower-Theme: Failed to deploy
artifacts: Could not transfer artifact
org.apache.royale.framework:Jewel-Light-NoFlat-Primary-Sunflower-Theme:swc:0.9.4
from/to apache.releases.https (
https://repository.apache.org/service/local/staging/deploy/maven2): Remote
host closed connection during handshake: SSL peer shut down incorrectly ->
[Help 1]

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] To see the full stack trace of the errors,
re-run Maven with the -e switch.

 [exec] [INFO] [ERROR] Re-run Maven using the -X switch to enable full
debug logging.

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] For more information about the errors and
possible solutions, please read the following articles:

 [exec] [INFO] [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] After correcting the problems, you can resume
the build with the command

 [exec] [INFO] [ERROR]   mvn  -rf
:Jewel-Light-NoFlat-Primary-Sunflower-Theme

 [exec] [INFO]



I am guessing it is a bad internet connection.  I am wondering if we can
pass a -rf (resume from) option to the maven call from ant?  Otherwise
doing all this from scratch everytime is a big pain.

Thanks,
Om

On Wed, Oct 3, 2018 at 12:47 AM Alex Harui  wrote:

> Looks like it was a missing [
>
> MXRoyale and SparkRoyale built for me.
>
> HTH,
> -Alex
>
> On 10/3/18, 12:43 AM, "OmPrakash Muppirala"  wrote:
>
> Thanks!
>
> I reverted everything back to previous state.  I can give it a shot
> tomorrow evening.
>
> Regards,
> Om
>
> On Wed, Oct 3, 2018 at 12:41 AM Alex Harui 
> wrote:
>
> > It was in a releasable state.  TourDeFlex was running on it.
> >
> > I'm trying to track down the change that broke it.
> >
> > -Alex
> >
> > On 10/3/18, 12:32 AM, "OmPrakash Muppirala" 
> wrote:
> >
> > A bit more progress. Now we are failing on the MXRoyale project:
> >
> >  [exec] [INFO] [INFO]
> >
> >
> 
> >
> >  [exec] [INFO] [INFO] BUILD FAILURE
> >
> >  [exec] [INFO] [INFO]
> >
> >
> 
> >
> >  [exec] [INFO] [INFO] Total time: 01:34 min
> >
> >  [exec] [INFO] [INFO] Finished at: 2018-10-03T00:28:14-07:00
> >
> >  [exec] [INFO] [INFO]
> >
> >
> 
> >
> >  [exec] [INFO] [ERROR] Failed to execute goal
> > org.apache.royale.compiler:royale-maven-plugin:0.9.4:compile-as
> > (default-compile-as) on project MXRoyale: There were errors
> during the
> > build. Got return code 3 -> [Help 1]
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] To see the full stack trace of the
> errors,
> > re-run Maven with the -e switch.
> >
> >  [exec] [INFO] [ERROR] Re-run Maven using the -X switch to
> enable
> > full
> > debug logging.
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] For more information about the errors
> and
> > possible solutions, please read the following articles:
> >
> >  [exec] [INFO] [ERROR] [Help 1]
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionExceptiondata=02%7C01%7Caharui%40adobe.com%7C1286310eeccc4c57439108d62903e119%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741493968858792sdata=h0WDkLmfJD1GjTezuQ6GT1bqr

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

2018-10-03 Thread OmPrakash Muppirala
Thanks!

I reverted everything back to previous state.  I can give it a shot
tomorrow evening.

Regards,
Om

On Wed, Oct 3, 2018 at 12:41 AM Alex Harui  wrote:

> It was in a releasable state.  TourDeFlex was running on it.
>
> I'm trying to track down the change that broke it.
>
> -Alex
>
> On 10/3/18, 12:32 AM, "OmPrakash Muppirala"  wrote:
>
> A bit more progress. Now we are failing on the MXRoyale project:
>
>  [exec] [INFO] [INFO]
>
> 
>
>  [exec] [INFO] [INFO] BUILD FAILURE
>
>  [exec] [INFO] [INFO]
>
> 
>
>  [exec] [INFO] [INFO] Total time: 01:34 min
>
>  [exec] [INFO] [INFO] Finished at: 2018-10-03T00:28:14-07:00
>
>  [exec] [INFO] [INFO]
>
> 
>
>  [exec] [INFO] [ERROR] Failed to execute goal
> org.apache.royale.compiler:royale-maven-plugin:0.9.4:compile-as
> (default-compile-as) on project MXRoyale: There were errors during the
> build. Got return code 3 -> [Help 1]
>
>  [exec] [INFO] [ERROR]
>
>  [exec] [INFO] [ERROR] To see the full stack trace of the errors,
> re-run Maven with the -e switch.
>
>  [exec] [INFO] [ERROR] Re-run Maven using the -X switch to enable
> full
> debug logging.
>
>  [exec] [INFO] [ERROR]
>
>  [exec] [INFO] [ERROR] For more information about the errors and
> possible solutions, please read the following articles:
>
>  [exec] [INFO] [ERROR] [Help 1]
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionExceptiondata=02%7C01%7Caharui%40adobe.com%7C2b91c6a14e704d842f2e08d629025d96%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741487473245214sdata=l2L26ZMwSr5v20mncG4smoSrRuJeIDxdKMzQMq8dM7A%3Dreserved=0
>
>  [exec] [INFO] [ERROR]
>
>  [exec] [INFO] [ERROR] After correcting the problems, you can
> resume
> the build with the command
>
>  [exec] [INFO] [ERROR]   mvn  -rf :MXRoyale
>
>
> Can we perhaps turn this project off?  Is it in a releasable state?
>
> On Tue, Oct 2, 2018 at 7:30 PM OmPrakash Muppirala <
> bigosma...@gmail.com>
> wrote:
>
> > I'm going to give this another shot in a couple of hours, unless
> there are
> > any objections.
> >
> > Thanks,
> > Om
> >
> > On Mon, Oct 1, 2018, 2:04 PM Alex Harui 
> wrote:
> >
> >> Jewel is mentioned in there.  I added mention of the migration
> components
> >> and tour de flex.  Not sure if I got the formatting right.  I think
> it is
> >> good enough.
> >>
> >> -Alex
> >>
> >> On 10/1/18, 12:13 PM, "OmPrakash Muppirala" 
> >> wrote:
> >>
> >> I updated it, although it looks a bit sparse now.  Can we list
> a few
> >> major
> >> highlights here, that I can go add to the release notes?
> >> Jewel should at least have several updates.
> >>
> >> Thanks,
> >> Om
> >>
> >> On Mon, Oct 1, 2018 at 12:09 PM Alex Harui
> 
> >> wrote:
> >>
> >> > Hey, I just noticed that nobody put a 0.9.4 section in the
> >> RELEASE_NOTES.
> >> > Maybe just rename the 0.9.3 section?
> >> >
> >> > -Alex
> >> >
> >> > On 10/1/18, 12:07 PM, "OmPrakash Muppirala" <
> bigosma...@gmail.com>
> >> wrote:
> >> >
> >> > Good catch!  I just pushed a fix for that.
> >> >
> >> > Thanks,
> >> > Om
> >> >
> >> > On Mon, Oct 1, 2018 at 11:04 AM Alex Harui
> >> 
> >> > wrote:
> >> >
> >> > > Om,
> >> > >
> >> > > I think the release/0.9.4 in
> royale-asjs/pom.xml
> >> needs to
> >> > be
> >> > > reverted back to 0.9.3.
> >> > >
> >> > > Everything else looks ok from my quick examination.
> >>  

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

2018-10-03 Thread OmPrakash Muppirala
A bit more progress. Now we are failing on the MXRoyale project:

 [exec] [INFO] [INFO]


 [exec] [INFO] [INFO] BUILD FAILURE

 [exec] [INFO] [INFO]


 [exec] [INFO] [INFO] Total time: 01:34 min

 [exec] [INFO] [INFO] Finished at: 2018-10-03T00:28:14-07:00

 [exec] [INFO] [INFO]


 [exec] [INFO] [ERROR] Failed to execute goal
org.apache.royale.compiler:royale-maven-plugin:0.9.4:compile-as
(default-compile-as) on project MXRoyale: There were errors during the
build. Got return code 3 -> [Help 1]

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] To see the full stack trace of the errors,
re-run Maven with the -e switch.

 [exec] [INFO] [ERROR] Re-run Maven using the -X switch to enable full
debug logging.

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] For more information about the errors and
possible solutions, please read the following articles:

 [exec] [INFO] [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] After correcting the problems, you can resume
the build with the command

 [exec] [INFO] [ERROR]   mvn  -rf :MXRoyale


Can we perhaps turn this project off?  Is it in a releasable state?

On Tue, Oct 2, 2018 at 7:30 PM OmPrakash Muppirala 
wrote:

> I'm going to give this another shot in a couple of hours, unless there are
> any objections.
>
> Thanks,
> Om
>
> On Mon, Oct 1, 2018, 2:04 PM Alex Harui  wrote:
>
>> Jewel is mentioned in there.  I added mention of the migration components
>> and tour de flex.  Not sure if I got the formatting right.  I think it is
>> good enough.
>>
>> -Alex
>>
>> On 10/1/18, 12:13 PM, "OmPrakash Muppirala" 
>> wrote:
>>
>> I updated it, although it looks a bit sparse now.  Can we list a few
>> major
>> highlights here, that I can go add to the release notes?
>> Jewel should at least have several updates.
>>
>> Thanks,
>> Om
>>
>> On Mon, Oct 1, 2018 at 12:09 PM Alex Harui 
>> wrote:
>>
>> > Hey, I just noticed that nobody put a 0.9.4 section in the
>> RELEASE_NOTES.
>> > Maybe just rename the 0.9.3 section?
>> >
>> > -Alex
>> >
>> > On 10/1/18, 12:07 PM, "OmPrakash Muppirala" 
>> wrote:
>> >
>> > Good catch!  I just pushed a fix for that.
>> >
>> > Thanks,
>> > Om
>> >
>> > On Mon, Oct 1, 2018 at 11:04 AM Alex Harui
>> 
>> > wrote:
>> >
>> > > Om,
>> > >
>> > > I think the release/0.9.4 in royale-asjs/pom.xml
>> needs to
>> > be
>> > > reverted back to 0.9.3.
>> > >
>> > > Everything else looks ok from my quick examination.
>> > >
>> > > Thanks and good luck,
>> > > -Alex
>> > >
>> > > On 10/1/18, 10:29 AM, "Piotr Zarzycki" <
>> piotrzarzyck...@gmail.com>
>> > wrote:
>> > >
>> > > I saw your commit and I think you should be ok.
>> > >
>> > > pon., 1 paź 2018 o 19:21 OmPrakash Muppirala <
>> > bigosma...@gmail.com>
>> > > napisał(a):
>> > >
>> > > > Okay, I did the following to reset:
>> > > >
>> > > > For all three repos:
>> > > > * Reverted all references of 0.9.5 to 0.9.4
>> > > > * Deleted 0.9.4-rc1 tag
>> > > > * Deleted branch: release/0.9.4
>> > > >
>> > > > Can someone please make sure that we are good before
>> starting
>> > work?
>> > > >
>> > > > Thanks,
>> > > > Om
>> > > >
>> > > > On Mon, Oct 1, 2018 at 1:51 AM Carlos Rovira <
>> > > carlosrov...@apache.org>
>> > > > wrote:
>> > > >
>> > > > > Hi Om,
>> > > > > is related to flash player debugger not launched? are

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

2018-10-02 Thread OmPrakash Muppirala
I'm going to give this another shot in a couple of hours, unless there are
any objections.

Thanks,
Om

On Mon, Oct 1, 2018, 2:04 PM Alex Harui  wrote:

> Jewel is mentioned in there.  I added mention of the migration components
> and tour de flex.  Not sure if I got the formatting right.  I think it is
> good enough.
>
> -Alex
>
> On 10/1/18, 12:13 PM, "OmPrakash Muppirala"  wrote:
>
> I updated it, although it looks a bit sparse now.  Can we list a few
> major
> highlights here, that I can go add to the release notes?
> Jewel should at least have several updates.
>
> Thanks,
> Om
>
> On Mon, Oct 1, 2018 at 12:09 PM Alex Harui 
> wrote:
>
> > Hey, I just noticed that nobody put a 0.9.4 section in the
> RELEASE_NOTES.
> > Maybe just rename the 0.9.3 section?
> >
> > -Alex
> >
> > On 10/1/18, 12:07 PM, "OmPrakash Muppirala" 
> wrote:
> >
> > Good catch!  I just pushed a fix for that.
> >
> > Thanks,
> > Om
> >
> > On Mon, Oct 1, 2018 at 11:04 AM Alex Harui
> 
> > wrote:
> >
> > > Om,
> > >
> > > I think the release/0.9.4 in royale-asjs/pom.xml
> needs to
> > be
> > > reverted back to 0.9.3.
> > >
> > > Everything else looks ok from my quick examination.
> > >
> > > Thanks and good luck,
> > > -Alex
> > >
> > > On 10/1/18, 10:29 AM, "Piotr Zarzycki" <
> piotrzarzyck...@gmail.com>
> > wrote:
> > >
> > > I saw your commit and I think you should be ok.
> > >
> > > pon., 1 paź 2018 o 19:21 OmPrakash Muppirala <
> > bigosma...@gmail.com>
> > > napisał(a):
> > >
> > > > Okay, I did the following to reset:
> > > >
> > > > For all three repos:
> > > > * Reverted all references of 0.9.5 to 0.9.4
> > > > * Deleted 0.9.4-rc1 tag
> > > > * Deleted branch: release/0.9.4
> > > >
> > > > Can someone please make sure that we are good before
> starting
> > work?
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Mon, Oct 1, 2018 at 1:51 AM Carlos Rovira <
> > > carlosrov...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi Om,
> > > > > is related to flash player debugger not launched? are
> you on
> > Mac?
> > > > > I think on Mac I have to make *.swf files be always
> opened
> > by Flash
> > > > Player
> > > > > debugger.
> > > > >
> > > > > In the other hand, I need to commit during the day some
> > fixes, one
> > > on
> > > > > typedefs and expect more on compiler. So if you plan
> to try
> > again
> > > some
> > > > > hours ago, please, remove the commits to left the
> repos so
> > we can
> > > commit
> > > > > new work
> > > > >
> > > > > thanks!
> > > > >
> > > > > Carlos
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > El lun., 1 oct. 2018 a las 10:29, OmPrakash Muppirala
> (<
> > > > > bigosma...@gmail.com>)
>     >     > > > escribió:
> > > > >
> > > > > > I provided path to Chrome via -Dbrowser, but I got an
> > error that
> > > ant
> > > > was
> > > > > > not able to access the application.
> > > > > > So, I tried installing firefox and that seemed to
> work.
> > > > > >
> > > > > > On Mon, Oct 1, 2018 at 1:26 AM Piotr Zarzycki <
> > > > piotr

Re: NextGenAS tutorials on Royale website

2018-10-02 Thread OmPrakash Muppirala
I also see a typo in Josh's name :-)

Thanks,
Om

On Tue, Oct 2, 2018 at 4:24 PM Alex Harui  wrote:

> Personally, I don't have a problem, but I think Apache doesn't like
> anything that implies that Apache pays for code.
> IMO, the wording of that section does not say that Apache paid for
> anything, but it still talks about money and people can get the wrong
> impression.
>
> I would suggest removing that section.  Maybe in the top section where
> Josh's name is mentioned, make it a link to wherever Josh wants it to go
> that will tell people more about Josh and how he gets funding.
>
> Couple of small things I noticed:
>
> "donated to this website" --> "donated to Apache Royale"
> "Royale 0.8" --> "Royale 0.9.4".
>
> My 2 cents (dang, I'm mentioning money again!),
> -Alex
>
> On 10/2/18, 3:50 PM, "Carlos Rovira"  wrote:
>
> One latest thing. There’s a mention to yeti, moonshine and josh’s
> patreon
> account. It’s ok to left as is? Just to ensure all is correct
>
> Thanks!
>
> El El mié, 3 oct 2018 a las 0:41, Carlos Rovira <
> carlosrov...@apache.org>
> escribió:
>
> > Hi ,
> >
> > just introduced and edited NodeJS tutorial in pre site:
> >
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.codeoscopic.com%2Fhello-node-how-to-transpile-actionscript-for-node-js%2Fdata=02%7C01%7Caharui%40adobe.com%7C9dc0854917ab4b8d910908d628b97319%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741174301497910sdata=54snzCFJPohBfKCKj7egocm83yt88ifgEHvzanzWd4c%3Dreserved=0
> >
> > If someone could check if all is ok and even try the example, it
> would be
> > great I run out of time and could try my self.
> >
> > If all is ok, I can publish in r.a.o tomorrow morning
> >
> > thanks
> >
> > Carlos
> >
> >
> >
> > El mar., 2 oct. 2018 a las 19:17, Andrew Wetmore (<
> cottag...@gmail.com>)
> > escribió:
> >
> >> This will be a great addition. Thanks, Josh!
> >>
> >> On Tue, Oct 2, 2018 at 2:06 PM Carlos Rovira <
> carlosrov...@apache.org>
> >> wrote:
> >>
> >> > Hi,
> >> >
> >> > I contacted today Josh Tynjala, looking for the NodeJS tutorial
> he did
> >> that
> >> > I could not find.
> >> > It seems he refactored his site and change domain and the
> tutorials
> >> aren't
> >> > not available
> >> > I asked Josh to republish those tutorials on royale website with
> the
> >> > revision to update from FlexJS to Royale.
> >> >
> >> > He did the permission, and as well for anything he's part of this
> >> project
> >> > and PMC, so don't know if needs to expressly
> >> > notifiy here about the donation of this material
> >> >
> >> > In the other hand I want to expose here if we are all ok to
> republish
> >> this
> >> > tutorials in our website.
> >> >
> >> > I'll take the opportunity to say thanks to Josh for his generous
> >> donation!
> >> > Thanks Josh! :)
> >> >
> >> > --
> >> > Carlos Rovira
> >> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C9dc0854917ab4b8d910908d628b97319%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741174301654157sdata=vnLcJT%2F4C9zhFo%2BbZRwNmw3r94Y2uB1EjYP1Gf%2FGda0%3Dreserved=0
> >> >
> >>
> >>
> >> --
> >> Andrew Wetmore
> >>
> >>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C9dc0854917ab4b8d910908d628b97319%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741174301654157sdata=THdcEADC8cBa%2F8KkHNxPvZm0%2FVl3AhzoYDMFY2OSKdE%3Dreserved=0
> >>
> >
> >
> > --
> > Carlos Rovira
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C9dc0854917ab4b8d910908d628b97319%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741174301654157sdata=vnLcJT%2F4C9zhFo%2BbZRwNmw3r94Y2uB1EjYP1Gf%2FGda0%3Dreserved=0
> >
> > --
> Carlos Rovira
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C9dc0854917ab4b8d910908d628b97319%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741174301654157sdata=vnLcJT%2F4C9zhFo%2BbZRwNmw3r94Y2uB1EjYP1Gf%2FGda0%3Dreserved=0
>
>
>


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

2018-10-01 Thread OmPrakash Muppirala
I updated it, although it looks a bit sparse now.  Can we list a few major
highlights here, that I can go add to the release notes?
Jewel should at least have several updates.

Thanks,
Om

On Mon, Oct 1, 2018 at 12:09 PM Alex Harui  wrote:

> Hey, I just noticed that nobody put a 0.9.4 section in the RELEASE_NOTES.
> Maybe just rename the 0.9.3 section?
>
> -Alex
>
> On 10/1/18, 12:07 PM, "OmPrakash Muppirala"  wrote:
>
> Good catch!  I just pushed a fix for that.
>
> Thanks,
> Om
>
> On Mon, Oct 1, 2018 at 11:04 AM Alex Harui 
> wrote:
>
> > Om,
> >
> > I think the release/0.9.4 in royale-asjs/pom.xml needs to
> be
> > reverted back to 0.9.3.
> >
> > Everything else looks ok from my quick examination.
> >
> > Thanks and good luck,
> > -Alex
> >
> > On 10/1/18, 10:29 AM, "Piotr Zarzycki" 
> wrote:
> >
> > I saw your commit and I think you should be ok.
> >
> > pon., 1 paź 2018 o 19:21 OmPrakash Muppirala <
> bigosma...@gmail.com>
> > napisał(a):
> >
> > > Okay, I did the following to reset:
> > >
> > > For all three repos:
> > > * Reverted all references of 0.9.5 to 0.9.4
> > > * Deleted 0.9.4-rc1 tag
> > > * Deleted branch: release/0.9.4
> > >
> > > Can someone please make sure that we are good before starting
> work?
> > >
> > > Thanks,
> > > Om
> > >
> > > On Mon, Oct 1, 2018 at 1:51 AM Carlos Rovira <
> > carlosrov...@apache.org>
> > > wrote:
> > >
> > > > Hi Om,
> > > > is related to flash player debugger not launched? are you on
> Mac?
> > > > I think on Mac I have to make *.swf files be always opened
> by Flash
> > > Player
> > > > debugger.
> > > >
> > > > In the other hand, I need to commit during the day some
> fixes, one
> > on
> > > > typedefs and expect more on compiler. So if you plan to try
> again
> > some
> > > > hours ago, please, remove the commits to left the repos so
> we can
> > commit
> > > > new work
> > > >
> > > > thanks!
> > > >
> > > > Carlos
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > El lun., 1 oct. 2018 a las 10:29, OmPrakash Muppirala (<
> > > > bigosma...@gmail.com>)
> > > > escribió:
> > > >
> > > > > I provided path to Chrome via -Dbrowser, but I got an
> error that
> > ant
> >     > was
> > > > > not able to access the application.
> > > > > So, I tried installing firefox and that seemed to work.
> > > > >
> > > > > On Mon, Oct 1, 2018 at 1:26 AM Piotr Zarzycki <
> > > piotrzarzyck...@gmail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Hi Om,
> > > > > >
> > > > > > You did use Firefox for that purpose ? I had to specify
> > > -Dbrowser=path
> > > > to
> > > > > > firefox.exe
> > > > > >
> > > > > > Thanks,
> > > > > > Piotr
> > > > > >
> > > > > > pon., 1 paź 2018 o 10:22 OmPrakash Muppirala <
> > bigosma...@gmail.com>
> > > > > > napisał(a):
> > > > > >
> > > > > > > Okay, I made several attempts through the day, making
> > progress each
> > > > > time.
> > > > > > >  The last run failed because the browser could not be
>     > launched.
> > > > > > > I am going to pause on this and try again tomorrow (or
> > later) . If
> > > > > > someone
> > > > > > > else wants to give this a go in the meantimne, they are
> > welcome :-)
> > > >

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

2018-10-01 Thread OmPrakash Muppirala
Good catch!  I just pushed a fix for that.

Thanks,
Om

On Mon, Oct 1, 2018 at 11:04 AM Alex Harui  wrote:

> Om,
>
> I think the release/0.9.4 in royale-asjs/pom.xml needs to be
> reverted back to 0.9.3.
>
> Everything else looks ok from my quick examination.
>
> Thanks and good luck,
> -Alex
>
> On 10/1/18, 10:29 AM, "Piotr Zarzycki"  wrote:
>
> I saw your commit and I think you should be ok.
>
> pon., 1 paź 2018 o 19:21 OmPrakash Muppirala 
> napisał(a):
>
> > Okay, I did the following to reset:
> >
> > For all three repos:
> > * Reverted all references of 0.9.5 to 0.9.4
> > * Deleted 0.9.4-rc1 tag
> > * Deleted branch: release/0.9.4
> >
> > Can someone please make sure that we are good before starting work?
> >
> > Thanks,
> > Om
> >
> > On Mon, Oct 1, 2018 at 1:51 AM Carlos Rovira <
> carlosrov...@apache.org>
> > wrote:
> >
> > > Hi Om,
> > > is related to flash player debugger not launched? are you on Mac?
> > > I think on Mac I have to make *.swf files be always opened by Flash
> > Player
> > > debugger.
> > >
> > > In the other hand, I need to commit during the day some fixes, one
> on
> > > typedefs and expect more on compiler. So if you plan to try again
> some
> > > hours ago, please, remove the commits to left the repos so we can
> commit
> > > new work
> > >
> > > thanks!
> > >
> > > Carlos
> > >
> > >
> > >
> > >
> > >
> > > El lun., 1 oct. 2018 a las 10:29, OmPrakash Muppirala (<
> > > bigosma...@gmail.com>)
> > > escribió:
> > >
> > > > I provided path to Chrome via -Dbrowser, but I got an error that
> ant
> > was
> > > > not able to access the application.
> > > > So, I tried installing firefox and that seemed to work.
> > > >
> > > > On Mon, Oct 1, 2018 at 1:26 AM Piotr Zarzycki <
> > piotrzarzyck...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > Hi Om,
> > > > >
> > > > > You did use Firefox for that purpose ? I had to specify
> > -Dbrowser=path
> > > to
> > > > > firefox.exe
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > pon., 1 paź 2018 o 10:22 OmPrakash Muppirala <
> bigosma...@gmail.com>
> > > > > napisał(a):
> > > > >
> > > > > > Okay, I made several attempts through the day, making
> progress each
> > > > time.
> > > > > >  The last run failed because the browser could not be
> launched.
> > > > > > I am going to pause on this and try again tomorrow (or
> later) . If
> > > > > someone
> > > > > > else wants to give this a go in the meantimne, they are
> welcome :-)
> > > > > >
> > > > > > Thanks,
> > > > > > Om
> > > > > >
> > > > > > On Mon, Oct 1, 2018 at 12:22 AM Carlos Rovira <
> > > carlosrov...@apache.org
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Om,
> > > > > > > no,  I Thought this was due to different tries of the
> release
> > > process
> > > > > but
> > > > > > > most of the poms are in 0.9.6-SNAPSHOT.
> > > > > > > You can search the entire repo for "0.9.X-SNAPSHOT" string
> to see
> > > > that
> > > > > > now
> > > > > > > X is 6.
> > > > > > >
> > > > > > > thanks
> > > > > > >
> > > > > > > El lun., 1 oct. 2018 a las 2:07, OmPrakash Muppirala (<
> > > > > > > bigosma...@gmail.com>)
> > > > > > > escribió:
> > > > > > >
> > > > > > > > On Sun, Sep 30, 2018, 2:13 PM Carlos Rovira <
> > > > carlosrov...@apache.org
> > > &

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

2018-10-01 Thread OmPrakash Muppirala
Okay, I did the following to reset:

For all three repos:
* Reverted all references of 0.9.5 to 0.9.4
* Deleted 0.9.4-rc1 tag
* Deleted branch: release/0.9.4

Can someone please make sure that we are good before starting work?

Thanks,
Om

On Mon, Oct 1, 2018 at 1:51 AM Carlos Rovira 
wrote:

> Hi Om,
> is related to flash player debugger not launched? are you on Mac?
> I think on Mac I have to make *.swf files be always opened by Flash Player
> debugger.
>
> In the other hand, I need to commit during the day some fixes, one on
> typedefs and expect more on compiler. So if you plan to try again some
> hours ago, please, remove the commits to left the repos so we can commit
> new work
>
> thanks!
>
> Carlos
>
>
>
>
>
> El lun., 1 oct. 2018 a las 10:29, OmPrakash Muppirala (<
> bigosma...@gmail.com>)
> escribió:
>
> > I provided path to Chrome via -Dbrowser, but I got an error that ant was
> > not able to access the application.
> > So, I tried installing firefox and that seemed to work.
> >
> > On Mon, Oct 1, 2018 at 1:26 AM Piotr Zarzycki  >
> > wrote:
> >
> > > Hi Om,
> > >
> > > You did use Firefox for that purpose ? I had to specify -Dbrowser=path
> to
> > > firefox.exe
> > >
> > > Thanks,
> > > Piotr
> > >
> > > pon., 1 paź 2018 o 10:22 OmPrakash Muppirala 
> > > napisał(a):
> > >
> > > > Okay, I made several attempts through the day, making progress each
> > time.
> > > >  The last run failed because the browser could not be launched.
> > > > I am going to pause on this and try again tomorrow (or later) . If
> > > someone
> > > > else wants to give this a go in the meantimne, they are welcome :-)
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Mon, Oct 1, 2018 at 12:22 AM Carlos Rovira <
> carlosrov...@apache.org
> > >
> > > > wrote:
> > > >
> > > > > Hi Om,
> > > > > no,  I Thought this was due to different tries of the release
> process
> > > but
> > > > > most of the poms are in 0.9.6-SNAPSHOT.
> > > > > You can search the entire repo for "0.9.X-SNAPSHOT" string to see
> > that
> > > > now
> > > > > X is 6.
> > > > >
> > > > > thanks
> > > > >
> > > > > El lun., 1 oct. 2018 a las 2:07, OmPrakash Muppirala (<
> > > > > bigosma...@gmail.com>)
> > > > > escribió:
> > > > >
> > > > > > On Sun, Sep 30, 2018, 2:13 PM Carlos Rovira <
> > carlosrov...@apache.org
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Om,
> > > > > > > just saw that some poms was not changed to 0.9.6-SNAPSHOT.
> > > > > > >
> > > > > >
> > > > > > Do you mean 0.9.4-SNAPSHOT?
> > > > > >
> > > > > > Thanks,
> > > > > > Om
> > > > > >
> > > > > >
> > > > > >
> > > > > > I think that should be fixed and get a prepare maven release
> > process
> > > > that
> > > > > > > could finaly gets all poms updated to new version.
> > > > > > > Don't know if that could be the problem. Can you try again?
> > > > > > > thanks
> > > > > > >
> > > > > > > El dom., 30 sept. 2018 a las 21:32, OmPrakash Muppirala (<
> > > > > > > bigosma...@gmail.com>) escribió:
> > > > > > >
> > > > > > > > Made a bit more progress, but the build is failing here now:
> > > > > > > >
> > > > > > > >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > > > > > > > DataBindingExample_as SUCCESS [  2.469 s]
> > > > > > > >
> > > > > > > >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > > > > > > > DataBindingExample_Flat FAILURE [  1.756 s]
> > > > > > > >
> > > > > > > >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > > > > > > > DataBindingExampleWithLayout SKIPPED
> > > > > > > >
> > > > > > > >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > > >

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

2018-10-01 Thread OmPrakash Muppirala
I provided path to Chrome via -Dbrowser, but I got an error that ant was
not able to access the application.
So, I tried installing firefox and that seemed to work.

On Mon, Oct 1, 2018 at 1:26 AM Piotr Zarzycki 
wrote:

> Hi Om,
>
> You did use Firefox for that purpose ? I had to specify -Dbrowser=path to
> firefox.exe
>
> Thanks,
> Piotr
>
> pon., 1 paź 2018 o 10:22 OmPrakash Muppirala 
> napisał(a):
>
> > Okay, I made several attempts through the day, making progress each time.
> >  The last run failed because the browser could not be launched.
> > I am going to pause on this and try again tomorrow (or later) . If
> someone
> > else wants to give this a go in the meantimne, they are welcome :-)
> >
> > Thanks,
> > Om
> >
> > On Mon, Oct 1, 2018 at 12:22 AM Carlos Rovira 
> > wrote:
> >
> > > Hi Om,
> > > no,  I Thought this was due to different tries of the release process
> but
> > > most of the poms are in 0.9.6-SNAPSHOT.
> > > You can search the entire repo for "0.9.X-SNAPSHOT" string to see that
> > now
> > > X is 6.
> > >
> > > thanks
> > >
> > > El lun., 1 oct. 2018 a las 2:07, OmPrakash Muppirala (<
> > > bigosma...@gmail.com>)
> > > escribió:
> > >
> > > > On Sun, Sep 30, 2018, 2:13 PM Carlos Rovira  >
> > > > wrote:
> > > >
> > > > > Hi Om,
> > > > > just saw that some poms was not changed to 0.9.6-SNAPSHOT.
> > > > >
> > > >
> > > > Do you mean 0.9.4-SNAPSHOT?
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > >
> > > >
> > > > I think that should be fixed and get a prepare maven release process
> > that
> > > > > could finaly gets all poms updated to new version.
> > > > > Don't know if that could be the problem. Can you try again?
> > > > > thanks
> > > > >
> > > > > El dom., 30 sept. 2018 a las 21:32, OmPrakash Muppirala (<
> > > > > bigosma...@gmail.com>) escribió:
> > > > >
> > > > > > Made a bit more progress, but the build is failing here now:
> > > > > >
> > > > > >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > > > > > DataBindingExample_as SUCCESS [  2.469 s]
> > > > > >
> > > > > >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > > > > > DataBindingExample_Flat FAILURE [  1.756 s]
> > > > > >
> > > > > >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > > > > > DataBindingExampleWithLayout SKIPPED
> > > > > >
> > > > > >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > > > > DataGridExample
> > > > > > ... SKIPPED
> > > > > >
> > > > > >
> > > > > >
> > > > > > Detailed error:
> > > > > >
> > > > > >
> > > > > > [exec] [INFO] [INFO]
> > > > > >
> > > >
> > 
> > > > > >
> > > > > >  [exec] [INFO] [INFO] BUILD FAILURE
> > > > > >
> > > > > >  [exec] [INFO] [INFO]
> > > > > >
> > > >
> > 
> > > > > >
> > > > > >  [exec] [INFO] [INFO] Total time: 07:03 min
> > > > > >
> > > > > >  [exec] [INFO] [INFO] Finished at: 2018-09-30T12:17:45-07:00
> > > > > >
> > > > > >  [exec] [INFO] [INFO]
> > > > > >
> > > >
> > 
> > > > > >
> > > > > >  [exec] [INFO] [ERROR] Failed to execute goal
> > > > > > org.apache.maven.plugins:maven-dependency-plugin:2.10:unpack
> > > > > (unpack-fonts)
> > > > > > on project DataBindingExample_Flat: Unable to find artifact.
> Could
> > > not
> > > > > find
> > > > > > artifact org.apache.royale.framework:Fonts:war:0.9.4 in
> > > apache-release
> > > > (
> > > > > > https://repository.apache

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

2018-10-01 Thread OmPrakash Muppirala
Okay, I made several attempts through the day, making progress each time.
 The last run failed because the browser could not be launched.
I am going to pause on this and try again tomorrow (or later) . If someone
else wants to give this a go in the meantimne, they are welcome :-)

Thanks,
Om

On Mon, Oct 1, 2018 at 12:22 AM Carlos Rovira 
wrote:

> Hi Om,
> no,  I Thought this was due to different tries of the release process but
> most of the poms are in 0.9.6-SNAPSHOT.
> You can search the entire repo for "0.9.X-SNAPSHOT" string to see that now
> X is 6.
>
> thanks
>
> El lun., 1 oct. 2018 a las 2:07, OmPrakash Muppirala (<
> bigosma...@gmail.com>)
> escribió:
>
> > On Sun, Sep 30, 2018, 2:13 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Om,
> > > just saw that some poms was not changed to 0.9.6-SNAPSHOT.
> > >
> >
> > Do you mean 0.9.4-SNAPSHOT?
> >
> > Thanks,
> > Om
> >
> >
> >
> > I think that should be fixed and get a prepare maven release process that
> > > could finaly gets all poms updated to new version.
> > > Don't know if that could be the problem. Can you try again?
> > > thanks
> > >
> > > El dom., 30 sept. 2018 a las 21:32, OmPrakash Muppirala (<
> > > bigosma...@gmail.com>) escribió:
> > >
> > > > Made a bit more progress, but the build is failing here now:
> > > >
> > > >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > > > DataBindingExample_as SUCCESS [  2.469 s]
> > > >
> > > >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > > > DataBindingExample_Flat FAILURE [  1.756 s]
> > > >
> > > >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > > > DataBindingExampleWithLayout SKIPPED
> > > >
> > > >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > > DataGridExample
> > > > ... SKIPPED
> > > >
> > > >
> > > >
> > > > Detailed error:
> > > >
> > > >
> > > > [exec] [INFO] [INFO]
> > > >
> > 
> > > >
> > > >  [exec] [INFO] [INFO] BUILD FAILURE
> > > >
> > > >  [exec] [INFO] [INFO]
> > > >
> > 
> > > >
> > > >  [exec] [INFO] [INFO] Total time: 07:03 min
> > > >
> > > >  [exec] [INFO] [INFO] Finished at: 2018-09-30T12:17:45-07:00
> > > >
> > > >  [exec] [INFO] [INFO]
> > > >
> > 
> > > >
> > > >  [exec] [INFO] [ERROR] Failed to execute goal
> > > > org.apache.maven.plugins:maven-dependency-plugin:2.10:unpack
> > > (unpack-fonts)
> > > > on project DataBindingExample_Flat: Unable to find artifact. Could
> not
> > > find
> > > > artifact org.apache.royale.framework:Fonts:war:0.9.4 in
> apache-release
> > (
> > > > https://repository.apache.org/content/repositories/releases)
> > > >
> > > >  [exec] [INFO] [ERROR]
> > > >
> > > >  [exec] [INFO] [ERROR] Try downloading the file manually from the
> > > > project website.
> > > >
> > > >  [exec] [INFO] [ERROR]
> > > >
> > > >  [exec] [INFO] [ERROR] Then, install it using the command:
> > > >
> > > >  [exec] [INFO] [ERROR] mvn install:install-file
> > > > -DgroupId=org.apache.royale.framework -DartifactId=Fonts
> > -Dversion=0.9.4
> > > > -Dpackaging=war -Dfile=/path/to/file
> > > >
> > > >  [exec] [INFO] [ERROR]
> > > >
> > > >  [exec] [INFO] [ERROR] Alternatively, if you host your own
> > repository
> > > > you can deploy the file there:
> > > >
> > > >  [exec] [INFO] [ERROR] mvn deploy:deploy-file
> > > > -DgroupId=org.apache.royale.framework -DartifactId=Fonts
> > -Dversion=0.9.4
> > > > -Dpackaging=war -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> > > >
> > > >  [exec] [INFO] [ERROR]
> > > >
> > > >  [exec] [INFO] [ERROR]
> > > >
> > > >  [exec] [INFO] [ERROR]
> >  org.apache.royale.framework:Fonts:war:0.9

Re: [royale-asjs] branch develop updated: fix version in poms. some poms still was in 0.9.4-SNAPSHOT. We should take a look about why this ones was not changed to 0.9.6-SNAPSHOT

2018-09-30 Thread OmPrakash Muppirala
Okay, reverted everything back to 0.9.4 in all three repos and trying again
:-)

On Sun, Sep 30, 2018 at 9:10 PM Piotr Zarzycki 
wrote:

> Starting point in Dev is 0.9.4-SNAPSHOT. If you run script and it's failed
> you should immediately revert all the changes which Maven did.
>
> It looks like it wasn't correctly reverted before script was run. I think
> you may next time succeed if you revert it correctly.
>
> Thanks,
> Piotr
>
> On Mon, Oct 1, 2018, 6:06 AM Alex Harui  wrote:
>
> > Something is already wrong if the devl branch is at 0.9.6-SNAPSHOT
> instead
> > of 0.9.5-SNAPSHOT.
> >
> > My 2 cents,
> > -Alex
> >
> > On 9/30/18, 2:11 PM, "carlosrov...@apache.org"  >
> > wrote:
> >
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > carlosrovira pushed a commit to branch develop
> > in repository
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-asjs.gitdata=02%7C01%7Caharui%40adobe.com%7C05747880a32c4336979008d627194c57%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636739386974979241sdata=2iznID6m%2BYuMbMOYBudO7dnT61D%2B1EEIzeA7tp5z5t4%3Dreserved=0
> >
> >
> > The following commit(s) were added to refs/heads/develop by this
> push:
> >  new 390d8c9  fix version in poms. some poms still was in
> > 0.9.4-SNAPSHOT. We should take a look about why this ones was not changed
> > to 0.9.6-SNAPSHOT
> > 390d8c9 is described below
> >
> > commit 390d8c982fe57ddf18dd873d7b196b8bfa0a46c2
> > Author: Carlos Rovira 
> > AuthorDate: Sun Sep 30 23:11:23 2018 +0200
> >
> > fix version in poms. some poms still was in 0.9.4-SNAPSHOT. We
> > should take a look about why this ones was not changed to 0.9.6-SNAPSHOT
> > ---
> >  archetypes/pom.xml   | 2 +-
> >  examples/pom.xml | 2 +-
> >  examples/royale/JewelExample/pom.xml | 6 +++---
> >  manualtests/pom.xml  | 2 +-
> >  pom.xml  | 4 ++--
> >  5 files changed, 8 insertions(+), 8 deletions(-)
> >
> > diff --git a/archetypes/pom.xml b/archetypes/pom.xml
> > index 4879f23..073f72d 100644
> > --- a/archetypes/pom.xml
> > +++ b/archetypes/pom.xml
> > @@ -34,7 +34,7 @@
> >Maven archetypes for creating royale maven
> > projects
> >
> >
> > -
> > 0.9.4-SNAPSHOT
> > +
> > 0.9.6-SNAPSHOT
> >
> >
> >
> > diff --git a/examples/pom.xml b/examples/pom.xml
> > index e64505a..a5a0140 100644
> > --- a/examples/pom.xml
> > +++ b/examples/pom.xml
> > @@ -38,7 +38,7 @@
> >
> >
> ${basedir}/target/javascript/bin/js-debug
> >  
> >
> >
> ${basedir}/target/javascript/bin/js-release
> > -
> > 0.9.4-SNAPSHOT
> > +
> > 0.9.6-SNAPSHOT
> >
> >
> >
> > diff --git a/examples/royale/JewelExample/pom.xml
> > b/examples/royale/JewelExample/pom.xml
> > index 9d3cbdc..a8060d0 100644
> > --- a/examples/royale/JewelExample/pom.xml
> > +++ b/examples/royale/JewelExample/pom.xml
> > @@ -139,7 +139,7 @@
> >  
> > diff --git a/manualtests/pom.xml b/manualtests/pom.xml
> > index 08c9c8c..7d8f793 100644
> > --- a/manualtests/pom.xml
> > +++ b/manualtests/pom.xml
> > @@ -33,7 +33,7 @@
> >
> >
> >
> >
> ${basedir}/target/javascript/bin/js-debug
> > -
> > 0.9.4-SNAPSHOT
> > +
> > 0.9.6-SNAPSHOT
> >
> >Apache Royale: ManualTests
> >
> > diff --git a/pom.xml b/pom.xml
> > index 45d179c..9664d5c 100644
> > --- a/pom.xml
> > +++ b/pom.xml
> > @@ -55,8 +55,8 @@
> >
> >
> UTF-8
> >  3.5.4
> >
> > -
> 0.9.4-SNAPSHOT
> > -
> 0.9.4-SNAPSHOT
> > +
> 0.9.6-SNAPSHOT
> > +
> 0.9.6-SNAPSHOT
> >  1.0.0
> >
> >  true
> >
> >
> >
> >
>


Re: [royale-asjs] branch develop updated: fix version in poms. some poms still was in 0.9.4-SNAPSHOT. We should take a look about why this ones was not changed to 0.9.6-SNAPSHOT

2018-09-30 Thread OmPrakash Muppirala
Next version will be 0.9.5.  But I guess because I ran it twice, it has
been bumped up to 0.9.6.
I will revert all those to 0.9.5 and retry.

Thanks,
Om

On Sun, Sep 30, 2018 at 5:22 PM OmPrakash Muppirala 
wrote:

>
>
> On Sun, Sep 30, 2018 at 2:11 PM  wrote:
>
>> This is an automated email from the ASF dual-hosted git repository.
>>
>> carlosrovira pushed a commit to branch develop
>> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>>
>>
>> The following commit(s) were added to refs/heads/develop by this push:
>>  new 390d8c9  fix version in poms. some poms still was in
>> 0.9.4-SNAPSHOT. We should take a look about why this ones was not changed
>> to 0.9.6-SNAPSHOT
>> 390d8c9 is described below
>>
>> commit 390d8c982fe57ddf18dd873d7b196b8bfa0a46c2
>> Author: Carlos Rovira 
>> AuthorDate: Sun Sep 30 23:11:23 2018 +0200
>>
>> fix version in poms. some poms still was in 0.9.4-SNAPSHOT. We should
>> take a look about why this ones was not changed to 0.9.6-SNAPSHOT
>>
>
> Why should they be changed to 0.9.6?
>
>
>> ---
>>  archetypes/pom.xml   | 2 +-
>>  examples/pom.xml | 2 +-
>>  examples/royale/JewelExample/pom.xml | 6 +++---
>>  manualtests/pom.xml  | 2 +-
>>  pom.xml  | 4 ++--
>>  5 files changed, 8 insertions(+), 8 deletions(-)
>>
>> diff --git a/archetypes/pom.xml b/archetypes/pom.xml
>> index 4879f23..073f72d 100644
>> --- a/archetypes/pom.xml
>> +++ b/archetypes/pom.xml
>> @@ -34,7 +34,7 @@
>>Maven archetypes for creating royale maven
>> projects
>>
>>
>> -0.9.4-SNAPSHOT
>> +0.9.6-SNAPSHOT
>>
>>
>>
>> diff --git a/examples/pom.xml b/examples/pom.xml
>> index e64505a..a5a0140 100644
>> --- a/examples/pom.xml
>> +++ b/examples/pom.xml
>> @@ -38,7 +38,7 @@
>>
>>  
>> ${basedir}/target/javascript/bin/js-debug
>>  
>>
>>  
>> ${basedir}/target/javascript/bin/js-release
>> -0.9.4-SNAPSHOT
>> +0.9.6-SNAPSHOT
>>
>>
>>
>> diff --git a/examples/royale/JewelExample/pom.xml
>> b/examples/royale/JewelExample/pom.xml
>> index 9d3cbdc..a8060d0 100644
>> --- a/examples/royale/JewelExample/pom.xml
>> +++ b/examples/royale/JewelExample/pom.xml
>> @@ -139,7 +139,7 @@
>>  
>> diff --git a/manualtests/pom.xml b/manualtests/pom.xml
>> index 08c9c8c..7d8f793 100644
>> --- a/manualtests/pom.xml
>> +++ b/manualtests/pom.xml
>> @@ -33,7 +33,7 @@
>>
>>
>>
>>  
>> ${basedir}/target/javascript/bin/js-debug
>> -0.9.4-SNAPSHOT
>> +0.9.6-SNAPSHOT
>>
>>Apache Royale: ManualTests
>>
>> diff --git a/pom.xml b/pom.xml
>> index 45d179c..9664d5c 100644
>> --- a/pom.xml
>> +++ b/pom.xml
>> @@ -55,8 +55,8 @@
>>
>>  UTF-8
>>  3.5.4
>>
>> -0.9.4-SNAPSHOT
>> -0.9.4-SNAPSHOT
>> +0.9.6-SNAPSHOT
>> +0.9.6-SNAPSHOT
>>  1.0.0
>>
>>  true
>>
>>


Re: [royale-asjs] branch develop updated: fix version in poms. some poms still was in 0.9.4-SNAPSHOT. We should take a look about why this ones was not changed to 0.9.6-SNAPSHOT

2018-09-30 Thread OmPrakash Muppirala
On Sun, Sep 30, 2018 at 2:11 PM  wrote:

> This is an automated email from the ASF dual-hosted git repository.
>
> carlosrovira pushed a commit to branch develop
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>
>
> The following commit(s) were added to refs/heads/develop by this push:
>  new 390d8c9  fix version in poms. some poms still was in
> 0.9.4-SNAPSHOT. We should take a look about why this ones was not changed
> to 0.9.6-SNAPSHOT
> 390d8c9 is described below
>
> commit 390d8c982fe57ddf18dd873d7b196b8bfa0a46c2
> Author: Carlos Rovira 
> AuthorDate: Sun Sep 30 23:11:23 2018 +0200
>
> fix version in poms. some poms still was in 0.9.4-SNAPSHOT. We should
> take a look about why this ones was not changed to 0.9.6-SNAPSHOT
>

Why should they be changed to 0.9.6?


> ---
>  archetypes/pom.xml   | 2 +-
>  examples/pom.xml | 2 +-
>  examples/royale/JewelExample/pom.xml | 6 +++---
>  manualtests/pom.xml  | 2 +-
>  pom.xml  | 4 ++--
>  5 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/archetypes/pom.xml b/archetypes/pom.xml
> index 4879f23..073f72d 100644
> --- a/archetypes/pom.xml
> +++ b/archetypes/pom.xml
> @@ -34,7 +34,7 @@
>Maven archetypes for creating royale maven
> projects
>
>
> -0.9.4-SNAPSHOT
> +0.9.6-SNAPSHOT
>
>
>
> diff --git a/examples/pom.xml b/examples/pom.xml
> index e64505a..a5a0140 100644
> --- a/examples/pom.xml
> +++ b/examples/pom.xml
> @@ -38,7 +38,7 @@
>
>  
> ${basedir}/target/javascript/bin/js-debug
>  
>
>  
> ${basedir}/target/javascript/bin/js-release
> -0.9.4-SNAPSHOT
> +0.9.6-SNAPSHOT
>
>
>
> diff --git a/examples/royale/JewelExample/pom.xml
> b/examples/royale/JewelExample/pom.xml
> index 9d3cbdc..a8060d0 100644
> --- a/examples/royale/JewelExample/pom.xml
> +++ b/examples/royale/JewelExample/pom.xml
> @@ -139,7 +139,7 @@
>  
> diff --git a/manualtests/pom.xml b/manualtests/pom.xml
> index 08c9c8c..7d8f793 100644
> --- a/manualtests/pom.xml
> +++ b/manualtests/pom.xml
> @@ -33,7 +33,7 @@
>
>
>
>  
> ${basedir}/target/javascript/bin/js-debug
> -0.9.4-SNAPSHOT
> +0.9.6-SNAPSHOT
>
>Apache Royale: ManualTests
>
> diff --git a/pom.xml b/pom.xml
> index 45d179c..9664d5c 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -55,8 +55,8 @@
>
>  UTF-8
>  3.5.4
>
> -0.9.4-SNAPSHOT
> -0.9.4-SNAPSHOT
> +0.9.6-SNAPSHOT
> +0.9.6-SNAPSHOT
>  1.0.0
>
>  true
>
>


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

2018-09-30 Thread OmPrakash Muppirala
On Sun, Sep 30, 2018, 2:13 PM Carlos Rovira  wrote:

> Hi Om,
> just saw that some poms was not changed to 0.9.6-SNAPSHOT.
>

Do you mean 0.9.4-SNAPSHOT?

Thanks,
Om



I think that should be fixed and get a prepare maven release process that
> could finaly gets all poms updated to new version.
> Don't know if that could be the problem. Can you try again?
> thanks
>
> El dom., 30 sept. 2018 a las 21:32, OmPrakash Muppirala (<
> bigosma...@gmail.com>) escribió:
>
> > Made a bit more progress, but the build is failing here now:
> >
> >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > DataBindingExample_as SUCCESS [  2.469 s]
> >
> >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > DataBindingExample_Flat FAILURE [  1.756 s]
> >
> >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> > DataBindingExampleWithLayout SKIPPED
> >
> >  [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
> DataGridExample
> > ... SKIPPED
> >
> >
> >
> > Detailed error:
> >
> >
> > [exec] [INFO] [INFO]
> > 
> >
> >  [exec] [INFO] [INFO] BUILD FAILURE
> >
> >  [exec] [INFO] [INFO]
> > 
> >
> >  [exec] [INFO] [INFO] Total time: 07:03 min
> >
> >  [exec] [INFO] [INFO] Finished at: 2018-09-30T12:17:45-07:00
> >
> >  [exec] [INFO] [INFO]
> > 
> >
> >  [exec] [INFO] [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-dependency-plugin:2.10:unpack
> (unpack-fonts)
> > on project DataBindingExample_Flat: Unable to find artifact. Could not
> find
> > artifact org.apache.royale.framework:Fonts:war:0.9.4 in apache-release (
> > https://repository.apache.org/content/repositories/releases)
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] Try downloading the file manually from the
> > project website.
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] Then, install it using the command:
> >
> >  [exec] [INFO] [ERROR] mvn install:install-file
> > -DgroupId=org.apache.royale.framework -DartifactId=Fonts -Dversion=0.9.4
> > -Dpackaging=war -Dfile=/path/to/file
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] Alternatively, if you host your own repository
> > you can deploy the file there:
> >
> >  [exec] [INFO] [ERROR] mvn deploy:deploy-file
> > -DgroupId=org.apache.royale.framework -DartifactId=Fonts -Dversion=0.9.4
> > -Dpackaging=war -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR]   org.apache.royale.framework:Fonts:war:0.9.4
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] from the specified remote repositories:
> >
> >  [exec] [INFO] [ERROR]   apache-release (
> > https://repository.apache.org/content/repositories/releases,
> > releases=true,
> > snapshots=false),
> >
> >  [exec] [INFO] [ERROR]   apache-snapshots (
> > https://repository.apache.org/content/repositories/snapshots,
> > releases=false, snapshots=true),
> >
> >  [exec] [INFO] [ERROR]   apache.snapshots (
> > https://repository.apache.org/snapshots, releases=false,
> snapshots=true),
> >
> >  [exec] [INFO] [ERROR]   central (
> https://repo.maven.apache.org/maven2
> > ,
> > releases=true, snapshots=false)
> >
> >  [exec] [INFO] [ERROR] -> [Help 1]
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] To see the full stack trace of the errors,
> > re-run Maven with the -e switch.
> >
> >  [exec] [INFO] [ERROR] Re-run Maven using the -X switch to enable
> full
> > debug logging.
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] For more information about the errors and
> > possible solutions, please read the following articles:
> >
> >  [exec] [INFO] [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> >
> >  [exec] [INFO] [ERROR]
> >
> >  [exec] [INFO] [ERROR] After correcting the problems, you can resume
> > the build with the command
> >
> >

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

2018-09-30 Thread OmPrakash Muppirala
Made a bit more progress, but the build is failing here now:

 [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
DataBindingExample_as SUCCESS [  2.469 s]

 [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
DataBindingExample_Flat FAILURE [  1.756 s]

 [exec] [INFO] [INFO] Apache Royale: Examples: Royale:
DataBindingExampleWithLayout SKIPPED

 [exec] [INFO] [INFO] Apache Royale: Examples: Royale: DataGridExample
... SKIPPED



Detailed error:


[exec] [INFO] [INFO]


 [exec] [INFO] [INFO] BUILD FAILURE

 [exec] [INFO] [INFO]


 [exec] [INFO] [INFO] Total time: 07:03 min

 [exec] [INFO] [INFO] Finished at: 2018-09-30T12:17:45-07:00

 [exec] [INFO] [INFO]


 [exec] [INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:2.10:unpack (unpack-fonts)
on project DataBindingExample_Flat: Unable to find artifact. Could not find
artifact org.apache.royale.framework:Fonts:war:0.9.4 in apache-release (
https://repository.apache.org/content/repositories/releases)

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] Try downloading the file manually from the
project website.

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] Then, install it using the command:

 [exec] [INFO] [ERROR] mvn install:install-file
-DgroupId=org.apache.royale.framework -DartifactId=Fonts -Dversion=0.9.4
-Dpackaging=war -Dfile=/path/to/file

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] Alternatively, if you host your own repository
you can deploy the file there:

 [exec] [INFO] [ERROR] mvn deploy:deploy-file
-DgroupId=org.apache.royale.framework -DartifactId=Fonts -Dversion=0.9.4
-Dpackaging=war -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR]   org.apache.royale.framework:Fonts:war:0.9.4

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] from the specified remote repositories:

 [exec] [INFO] [ERROR]   apache-release (
https://repository.apache.org/content/repositories/releases, releases=true,
snapshots=false),

 [exec] [INFO] [ERROR]   apache-snapshots (
https://repository.apache.org/content/repositories/snapshots,
releases=false, snapshots=true),

 [exec] [INFO] [ERROR]   apache.snapshots (
https://repository.apache.org/snapshots, releases=false, snapshots=true),

 [exec] [INFO] [ERROR]   central (https://repo.maven.apache.org/maven2,
releases=true, snapshots=false)

 [exec] [INFO] [ERROR] -> [Help 1]

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] To see the full stack trace of the errors,
re-run Maven with the -e switch.

 [exec] [INFO] [ERROR] Re-run Maven using the -X switch to enable full
debug logging.

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] For more information about the errors and
possible solutions, please read the following articles:

 [exec] [INFO] [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] After correcting the problems, you can resume
the build with the command

 [exec] [INFO] [ERROR]   mvn  -rf :DataBindingExample_Flat

 [exec] [INFO]


 [exec] [INFO] Reactor Summary:

 [exec] [INFO] Apache Royale: Framework: Parent 0.9.5-SNAPSHOT 
FAILURE [07:08 min]

 [exec] [INFO] Apache Royale: Framework ...
SKIPPED

 [exec] [INFO] Apache Royale: Framework: Fonts 
SKIPPED



Can someone please take a look?

On Sun, Sep 30, 2018 at 9:13 AM OmPrakash Muppirala 
wrote:

> Thanks for the quick fix!  Will pull develop and try again.  Will report
> in a while.
>
> Regards,
> Om
>
>
> On Sun, Sep 30, 2018, 8:47 AM Carlos Rovira 
> wrote:
>
>> Hi Om,
>>
>> error is now fixed. Can you try to release again?
>> thanks
>>
>> Carlos
>>
>>
>>
>>
>>
>> El dom., 30 sept. 2018 a las 17:27, Carlos Rovira (<
>> carlosrov...@apache.org>)
>> escribió:
>>
>> > Hi,
>> >
>> > just reverted the two generated commits for release, I left to you
>> remove
>> > new branches generated.
>> > About the fail, I was wrong, since I saw this very quickly. It's not
>> about
>> > JDK, I'm using as well 1.8. I was confused for other thing I had some
>> weeks
>> > ago, and was trying to use another JDK, but I don't remember what was.
>> >
>> > Anyway, the problem is about java doc, in the new class
>> > AMFCompressionException.java I 

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

2018-09-30 Thread OmPrakash Muppirala
Thanks for the quick fix!  Will pull develop and try again.  Will report in
a while.

Regards,
Om


On Sun, Sep 30, 2018, 8:47 AM Carlos Rovira  wrote:

> Hi Om,
>
> error is now fixed. Can you try to release again?
> thanks
>
> Carlos
>
>
>
>
>
> El dom., 30 sept. 2018 a las 17:27, Carlos Rovira (<
> carlosrov...@apache.org>)
> escribió:
>
> > Hi,
> >
> > just reverted the two generated commits for release, I left to you remove
> > new branches generated.
> > About the fail, I was wrong, since I saw this very quickly. It's not
> about
> > JDK, I'm using as well 1.8. I was confused for other thing I had some
> weeks
> > ago, and was trying to use another JDK, but I don't remember what was.
> >
> > Anyway, the problem is about java doc, in the new class
> > AMFCompressionException.java I introduce some months ago.
> > since we never execute java doc generation we didn't see this.
> >
> > I'm going to try to fix this removing the problems I see, and I'll try to
> > see if I can try to use java doc to test if I pass the problem.
> >
> > I'll report soon.
> >
> > Carlos
> >
> >
> > El dom., 30 sept. 2018 a las 17:12, Carlos Rovira (<
> > carlosrov...@apache.org>) escribió:
> >
> >> Hi, since I'm going to work now on some compiler changes, I'll revert
> >> those 2 commits in each repo. I'll try to pass as well maven with java
> 1.8
> >> in amp and see if I get the same error
> >>
> >> El dom., 30 sept. 2018 a las 15:16, Piotr Zarzycki (<
> >> piotrzarzyck...@gmail.com>) escribió:
> >>
> >>> Om,
> >>>
> >>> I think if you got fail during the process you should right after that.
> >>> 1) Remove created release tags
> >>> 2) Revert all changes which Maven did in develop branches to the
> previous
> >>> state
> >>>
> >>> Thanks,
> >>> Piotr
> >>>
> >>> niedz., 30 wrz 2018 o 12:40 Carlos Rovira <
> carlos.rov...@codeoscopic.com
> >>> >
> >>> napisał(a):
> >>>
> >>> > Hi Om,
> >>> > don't have many time now, but seems you are using JDK 1.8 and that
> >>> project
> >>> > needs to be 1.7 or will fail
> >>> > I'll connect some hours later to see if you could use that sdk
> >>> > good luck! :)
> >>> >
> >>> > El dom., 30 sept. 2018 a las 11:34, Piotr Zarzycki (<
> >>> > piotrzarzyck...@gmail.com>) escribió:
> >>> >
> >>> > > Hi Om,
> >>> > >
> >>> > > Have you tried build that example on their own? Is it failing with
> >>> the
> >>> > same
> >>> > > stack trace?
> >>> > >
> >>> > > Thanks,
> >>> > > Piotr
> >>> > >
> >>> > > On Sun, Sep 30, 2018, 9:31 AM OmPrakash Muppirala <
> >>> bigosma...@gmail.com>
> >>> > > wrote:
> >>> > >
> >>> > > > So, I made a lot of progress (much more than last time), but
> >>> > > unfortunately
> >>> > > > the build failed at this stage.  Looks like an issue with the
> >>> > > > SampleAmfWebApp.  Anyone else seeing this error or am I doing
> >>> something
> >>> > > > wrong?
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] Apache Royale: Examples: Native:
> >>> USStatesMap
> >>> > > > ... SUCCESS [  1.001 s]
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] Apache Royale: Examples: NodeJS
> >>> > > >  SUCCESS [  0.210 s]
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] Apache Royale: Examples: NodeJS:
> >>> HelloWorld
> >>> > > >  SUCCESS [  0.945 s]
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] Apache Royale: Examples: AMF Web Apps
> >>> > > > .. SUCCESS [  0.202 s]
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] Apache Royale: Examples: AMF Web Apps:
> >>> > > > SampleAmfWebApp FAILURE [01:51 min]
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] Apache Royale: Examples:
> Integration

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

2018-09-30 Thread OmPrakash Muppirala
/release/royale-asjs/examples/amf/SampleAmfWebApp/target/apidocs'
dir.

 [exec] [INFO] [ERROR] -> [Help 1]

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] To see the full stack trace of the errors,
re-run Maven with the -e switch.

 [exec] [INFO] [ERROR] Re-run Maven using the -X switch to enable full
debug logging.

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] For more information about the errors and
possible solutions, please read the following articles:

 [exec] [INFO] [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] After correcting the problems, you can resume
the build with the command

 [exec] [INFO] [ERROR]   mvn  -rf :SampleAmfWebApp

On Sat, Sep 29, 2018 at 11:58 AM OmPrakash Muppirala 
wrote:

> Okay, trying now.
>
> On Tue, Sep 25, 2018 at 9:52 AM Piotr Zarzycki 
> wrote:
>
>> Om,
>>
>> I think if you first try to build Royale framework with Maven all the
>> dependencies will be downloaded. During framework build you should get
>> question about license related to player global etc. Once you do
>> successful
>> build  you could try to go and play with script for release. - That way to
>> go make you sure that script won't fail later during the process.
>>
>> Thanks,
>> Piotr
>>
>> pon., 24 wrz 2018 o 07:35 Alex Harui 
>> napisał(a):
>>
>> > According to the archives, try running:
>> >
>> > mvn -s settings-template.xml clean install
>> >
>> > Thanks,
>> > -Alex
>> >
>> > On 9/23/18, 3:48 PM, "OmPrakash Muppirala" 
>> wrote:
>> >
>> > On Sun, Sep 23, 2018 at 3:43 PM OmPrakash Muppirala <
>> > bigosma...@gmail.com>
>> > wrote:
>> >
>> > > Thanks.  I decided to stick with 1.8 :-)
>> > >
>> > >
>> > BTW, this is when I run: mvn clean install in the royale-asjs
>> > directory:
>> >
>> >
>> > > I am seeing this error:
>> > >
>> > > [ERROR] Failed to execute goal
>> > >
>> > org.apache.royale.compiler:royale-maven-plugin:0.9.4-SNAPSHOT:compile-as
>> > > (default-compile-as) on project Core: Could not resolve
>> dependencies
>> > for
>> > > project org.apache.royale.framework:Core:swc:0.9.4-SNAPSHOT:
>> Failure
>> > to
>> > > find com.adobe.air.framework:airglobal:swc:20.0 in
>> > >
>> >
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Freleasesdata=02%7C01%7Caharui%40adobe.com%7C2f3f5b1ac35b4355b12008d621a6b2e7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636733397180561746sdata=MWZN3TH8kh%2BKbX5CidHQhPOU6mKPIp2e7UP%2FwPXa2Mk%3Dreserved=0
>> > was cached in
>> > > the local repository, resolution will not be reattempted until the
>> > update
>> > > interval of apache-release has elapsed or updates are forced ->
>> > [Help 1]
>> > >
>> > > I don't see a `com` directory on
>> > >
>> >
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Freleasesdata=02%7C01%7Caharui%40adobe.com%7C2f3f5b1ac35b4355b12008d621a6b2e7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636733397180561746sdata=MWZN3TH8kh%2BKbX5CidHQhPOU6mKPIp2e7UP%2FwPXa2Mk%3Dreserved=0
>> > >
>> > > Is that expected?
>> > >
>> > > Thanks,
>> > > Om
>> > >
>> > >
>> > > On Sun, Sep 23, 2018 at 2:15 AM Carlos Rovira <
>> > carlosrov...@apache.org>
>> > > wrote:
>> > >
>> > >> Hi Om,
>> > >>
>> > >> I have Java 8 and 10 installed, and I think I was able to compile
>> > three
>> > >> repos, but I find AMF java example doesn't work, since BlazeDS
>> > needs a
>> > >> Lower version I need to go with 8 for this example. Maybe other
>> > part needs
>> > >> as well 7 or 8.
>> > >> I think trying another SDK should be left to some time between
>> > releases,
>> > >> since if not you can find spending more time that you thought.
>> > >>
>> > >> just my 2
>> > >>
>> > >> Thanks
>> > >>
>> >

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

2018-09-29 Thread OmPrakash Muppirala
Okay, trying now.

On Tue, Sep 25, 2018 at 9:52 AM Piotr Zarzycki 
wrote:

> Om,
>
> I think if you first try to build Royale framework with Maven all the
> dependencies will be downloaded. During framework build you should get
> question about license related to player global etc. Once you do successful
> build  you could try to go and play with script for release. - That way to
> go make you sure that script won't fail later during the process.
>
> Thanks,
> Piotr
>
> pon., 24 wrz 2018 o 07:35 Alex Harui 
> napisał(a):
>
> > According to the archives, try running:
> >
> > mvn -s settings-template.xml clean install
> >
> > Thanks,
> > -Alex
> >
> > On 9/23/18, 3:48 PM, "OmPrakash Muppirala" 
> wrote:
> >
> > On Sun, Sep 23, 2018 at 3:43 PM OmPrakash Muppirala <
> > bigosma...@gmail.com>
> > wrote:
> >
> > > Thanks.  I decided to stick with 1.8 :-)
> > >
> > >
> > BTW, this is when I run: mvn clean install in the royale-asjs
> > directory:
> >
> >
> > > I am seeing this error:
> > >
> > > [ERROR] Failed to execute goal
> > >
> > org.apache.royale.compiler:royale-maven-plugin:0.9.4-SNAPSHOT:compile-as
> > > (default-compile-as) on project Core: Could not resolve
> dependencies
> > for
> > > project org.apache.royale.framework:Core:swc:0.9.4-SNAPSHOT:
> Failure
> > to
> > > find com.adobe.air.framework:airglobal:swc:20.0 in
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Freleasesdata=02%7C01%7Caharui%40adobe.com%7C2f3f5b1ac35b4355b12008d621a6b2e7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636733397180561746sdata=MWZN3TH8kh%2BKbX5CidHQhPOU6mKPIp2e7UP%2FwPXa2Mk%3Dreserved=0
> > was cached in
> > > the local repository, resolution will not be reattempted until the
> > update
> > > interval of apache-release has elapsed or updates are forced ->
> > [Help 1]
> > >
> > > I don't see a `com` directory on
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Freleasesdata=02%7C01%7Caharui%40adobe.com%7C2f3f5b1ac35b4355b12008d621a6b2e7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636733397180561746sdata=MWZN3TH8kh%2BKbX5CidHQhPOU6mKPIp2e7UP%2FwPXa2Mk%3Dreserved=0
> > >
> > > Is that expected?
> > >
> > > Thanks,
> > > Om
> > >
> > >
> > > On Sun, Sep 23, 2018 at 2:15 AM Carlos Rovira <
> > carlosrov...@apache.org>
> > > wrote:
> > >
> > >> Hi Om,
> > >>
> > >> I have Java 8 and 10 installed, and I think I was able to compile
> > three
> > >> repos, but I find AMF java example doesn't work, since BlazeDS
> > needs a
> > >> Lower version I need to go with 8 for this example. Maybe other
> > part needs
> > >> as well 7 or 8.
> > >> I think trying another SDK should be left to some time between
> > releases,
> > >> since if not you can find spending more time that you thought.
> > >>
> > >> just my 2
> > >>
> > >> Thanks
> > >>
> > >> Carlos
> > >>
> > >> El dom., 23 sept. 2018 a las 8:14, OmPrakash Muppirala (<
> > >> bigosma...@gmail.com>) escribió:
> > >>
> > >> > Okay trying this out now.
> > >> >
> > >> > First question:  The release doc [1] says we need Java 1.7 or
> > higher.
> > >> Has
> > >> > anyone tried Java 10?   That is the default version available
> > through
> > >> all
> >     >> > installation channels.
> > >> > Any pitfalls I should consider?
> > >> >
> > >> > Thanks,
> > >> > Om
> > >> >
> > >> > On Fri, Sep 21, 2018 at 12:23 PM Carlos Rovira <
> > carlosrov...@apache.org
> > >> >
> > >> > wrote:
> > >> >
> > >> > > I think we are ready to go, so let's go! ;-)
> > >> > >
> > >> > > Good luck Om! :)
> > >> > >
> > >> > >

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

2018-09-23 Thread OmPrakash Muppirala
On Sun, Sep 23, 2018 at 3:43 PM OmPrakash Muppirala 
wrote:

> Thanks.  I decided to stick with 1.8 :-)
>
>
BTW, this is when I run: mvn clean install in the royale-asjs directory:


> I am seeing this error:
>
> [ERROR] Failed to execute goal
> org.apache.royale.compiler:royale-maven-plugin:0.9.4-SNAPSHOT:compile-as
> (default-compile-as) on project Core: Could not resolve dependencies for
> project org.apache.royale.framework:Core:swc:0.9.4-SNAPSHOT: Failure to
> find com.adobe.air.framework:airglobal:swc:20.0 in
> https://repository.apache.org/content/repositories/releases was cached in
> the local repository, resolution will not be reattempted until the update
> interval of apache-release has elapsed or updates are forced -> [Help 1]
>
> I don't see a `com` directory on
> https://repository.apache.org/content/repositories/releases
>
> Is that expected?
>
> Thanks,
> Om
>
>
> On Sun, Sep 23, 2018 at 2:15 AM Carlos Rovira 
> wrote:
>
>> Hi Om,
>>
>> I have Java 8 and 10 installed, and I think I was able to compile three
>> repos, but I find AMF java example doesn't work, since BlazeDS needs a
>> Lower version I need to go with 8 for this example. Maybe other part needs
>> as well 7 or 8.
>> I think trying another SDK should be left to some time between releases,
>> since if not you can find spending more time that you thought.
>>
>> just my 2
>>
>> Thanks
>>
>> Carlos
>>
>> El dom., 23 sept. 2018 a las 8:14, OmPrakash Muppirala (<
>> bigosma...@gmail.com>) escribió:
>>
>> > Okay trying this out now.
>> >
>> > First question:  The release doc [1] says we need Java 1.7 or higher.
>> Has
>> > anyone tried Java 10?   That is the default version available through
>> all
>> > installation channels.
>> > Any pitfalls I should consider?
>> >
>> > Thanks,
>> > Om
>> >
>> > On Fri, Sep 21, 2018 at 12:23 PM Carlos Rovira > >
>> > wrote:
>> >
>> > > I think we are ready to go, so let's go! ;-)
>> > >
>> > > Good luck Om! :)
>> > >
>> > > El vie., 21 sept. 2018 a las 18:19, Alex Harui
>> (> > > >)
>> > > escribió:
>> > >
>> > > > Yes, I think they are ready.  I removed the release/0.9.4 branches
>> so
>> > the
>> > > > scripts should be able to make a new one.
>> > > >
>> > > > -Alex
>> > > >
>> > > > On 9/21/18, 8:58 AM, "OmPrakash Muppirala" 
>> > > wrote:
>> > > >
>> > > > Alex said in his last email that the repos are ready.  Will try
>> in
>> > a
>> > > > few
>> > > > minutes.
>> > > >
>> > > > Thanks,
>> > > > Om
>> > > >
>> > > > On Fri, Sep 21, 2018, 7:24 AM Piotr Zarzycki <
>> > > > piotrzarzyck...@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > Om,
>> > > > >
>> > > > > In my opinion you have everything ready to go! Since develop
>> is
>> > > ready
>> > > > > probably you will start doing steps from the beginning, so in
>> the
>> > > > results
>> > > > > we will get branches release/0.9.4. However they already
>> exists,
>> > > > because
>> > > > > of
>> > > > > my previous attempt.
>> > > > >
>> > > > > Maybe before you even start they need to be removed.
>> > > > >
>> > > > > Thanks,
>> > > > > Piotr
>> > > > >
>> > > > >
>> > > > >
>> > > > > pt., 21 wrz 2018 o 16:16 OmPrakash Muppirala <
>> > bigosma...@gmail.com
>> > > >
>> > > > > napisał(a):
>> > > > >
>> > > > > > So am I clear to try and release?  Or should I wait for any
>> > other
>> > > > feature
>> > > > > > or bug?
>> > > > > >
>> > > > > > Thanks,
>> > > > > > Om
>> > > > > >
>> > > > > > On Fri, Sep 21, 2018, 6:20 AM Carlos Rovira <
>> > > > carlosrov...@apache.org>
>> > &g

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

2018-09-23 Thread OmPrakash Muppirala
Thanks.  I decided to stick with 1.8 :-)

I am seeing this error:

[ERROR] Failed to execute goal
org.apache.royale.compiler:royale-maven-plugin:0.9.4-SNAPSHOT:compile-as
(default-compile-as) on project Core: Could not resolve dependencies for
project org.apache.royale.framework:Core:swc:0.9.4-SNAPSHOT: Failure to
find com.adobe.air.framework:airglobal:swc:20.0 in
https://repository.apache.org/content/repositories/releases was cached in
the local repository, resolution will not be reattempted until the update
interval of apache-release has elapsed or updates are forced -> [Help 1]

I don't see a `com` directory on
https://repository.apache.org/content/repositories/releases

Is that expected?

Thanks,
Om


On Sun, Sep 23, 2018 at 2:15 AM Carlos Rovira 
wrote:

> Hi Om,
>
> I have Java 8 and 10 installed, and I think I was able to compile three
> repos, but I find AMF java example doesn't work, since BlazeDS needs a
> Lower version I need to go with 8 for this example. Maybe other part needs
> as well 7 or 8.
> I think trying another SDK should be left to some time between releases,
> since if not you can find spending more time that you thought.
>
> just my 2
>
> Thanks
>
> Carlos
>
> El dom., 23 sept. 2018 a las 8:14, OmPrakash Muppirala (<
> bigosma...@gmail.com>) escribió:
>
> > Okay trying this out now.
> >
> > First question:  The release doc [1] says we need Java 1.7 or higher.
> Has
> > anyone tried Java 10?   That is the default version available through all
> > installation channels.
> > Any pitfalls I should consider?
> >
> > Thanks,
> > Om
> >
> > On Fri, Sep 21, 2018 at 12:23 PM Carlos Rovira 
> > wrote:
> >
> > > I think we are ready to go, so let's go! ;-)
> > >
> > > Good luck Om! :)
> > >
> > > El vie., 21 sept. 2018 a las 18:19, Alex Harui
> ( > > >)
> > > escribió:
> > >
> > > > Yes, I think they are ready.  I removed the release/0.9.4 branches so
> > the
> > > > scripts should be able to make a new one.
> > > >
> > > > -Alex
> > > >
> > > > On 9/21/18, 8:58 AM, "OmPrakash Muppirala" 
> > > wrote:
> > > >
> > > > Alex said in his last email that the repos are ready.  Will try
> in
> > a
> > > > few
> > > > minutes.
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Fri, Sep 21, 2018, 7:24 AM Piotr Zarzycki <
> > > > piotrzarzyck...@gmail.com>
> > > > wrote:
> > > >
> > > > > Om,
> > > > >
> > > > > In my opinion you have everything ready to go! Since develop is
> > > ready
> > > > > probably you will start doing steps from the beginning, so in
> the
> > > > results
> > > > > we will get branches release/0.9.4. However they already
> exists,
> > > > because
> > > > > of
> > > > > my previous attempt.
> > > > >
> > > > > Maybe before you even start they need to be removed.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > >
> > > > >
> > > > > pt., 21 wrz 2018 o 16:16 OmPrakash Muppirala <
> > bigosma...@gmail.com
> > > >
> > > > > napisał(a):
> > > > >
> > > > > > So am I clear to try and release?  Or should I wait for any
> > other
> > > > feature
> > > > > > or bug?
> > > > > >
> > > > > > Thanks,
> > > > > > Om
> > > > > >
> > > > > > On Fri, Sep 21, 2018, 6:20 AM Carlos Rovira <
> > > > carlosrov...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Alex
> > > > > > >
> > > > > > > El vie., 21 sept. 2018 a las 3:06, Alex Harui
> > > > > ( > > > > > >)
> > > > > > > escribió:
> > > > > > >
> > > > > > > > I made some adjustments to the repos so that they
> "should"
> > be
> > > > ready
> > > > > to
> > > > > > > run
> > > > > > > > the scripts and 

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

2018-09-23 Thread OmPrakash Muppirala
Okay trying this out now.

First question:  The release doc [1] says we need Java 1.7 or higher.  Has
anyone tried Java 10?   That is the default version available through all
installation channels.
Any pitfalls I should consider?

Thanks,
Om

On Fri, Sep 21, 2018 at 12:23 PM Carlos Rovira 
wrote:

> I think we are ready to go, so let's go! ;-)
>
> Good luck Om! :)
>
> El vie., 21 sept. 2018 a las 18:19, Alex Harui ( >)
> escribió:
>
> > Yes, I think they are ready.  I removed the release/0.9.4 branches so the
> > scripts should be able to make a new one.
> >
> > -Alex
> >
> > On 9/21/18, 8:58 AM, "OmPrakash Muppirala" 
> wrote:
> >
> > Alex said in his last email that the repos are ready.  Will try in a
> > few
> > minutes.
> >
> > Thanks,
> > Om
> >
> > On Fri, Sep 21, 2018, 7:24 AM Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > wrote:
> >
> > > Om,
> > >
> > > In my opinion you have everything ready to go! Since develop is
> ready
> > > probably you will start doing steps from the beginning, so in the
> > results
> > > we will get branches release/0.9.4. However they already exists,
> > because
> > > of
> >     > my previous attempt.
> > >
> > > Maybe before you even start they need to be removed.
> > >
> > > Thanks,
> > > Piotr
> > >
> > >
> > >
> > > pt., 21 wrz 2018 o 16:16 OmPrakash Muppirala  >
> > > napisał(a):
> > >
> > > > So am I clear to try and release?  Or should I wait for any other
> > feature
> > > > or bug?
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Fri, Sep 21, 2018, 6:20 AM Carlos Rovira <
> > carlosrov...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi Alex
> > > > >
> > > > > El vie., 21 sept. 2018 a las 3:06, Alex Harui
> > > ( > > > >)
> > > > > escribió:
> > > > >
> > > > > > I made some adjustments to the repos so that they "should" be
> > ready
> > > to
> > > > > run
> > > > > > the scripts and produce the 0.9.4 release.  Of course, I
> could
> > be
> > > > wrong.
> > > > > > We'll see how Om fares.
> > > > > >
> > > > > >
> > > > > so cool :)
> > > > >
> > > > >
> > > > > > I also put in a change that should fix the dependencies
> > issue.  So
> > > the
> > > > > > remaining questions are around the AMF problem.  I'm thinking
> > of
> > > > looking
> > > > > > into what it takes to support Small Messages.  However, I
> > don't know
> > > > > > anything about them.  How often will migrating people be
> using
> > Small
> > > > > > Messages?  Is it fair to tell them to turn off Small
> Messages?
> > > > > >
> > > > >
> > > > > I think for now, that small messages is a BlazeDS feature. I
> > search for
> > > > > ZendAMF small messages and didn't fin d anything. So my bet is
> > that
> > > small
> > > > > messages is something only present in BlazeDS and Data Services
> > Adobe
> > > > > software.
> > > > >
> > > > > In the other hand, I'll be check new info from Darrell in 1-2
> > hours
> > > from
> > > > > now, but I think the problem with ZendAMF could be something
> > like the
> > > one
> > > > > happened with coldfusion where ArrayCollection needs some
> special
> > > > > treatment. I asked Darryl to start with simple connections like
> > we have
> > > > in
> > > > > our example (send and receive a String, then a simple object,
> > and so
> > > > > on...). I think is not good to start trying from a real app
> > scenario
> > > > where
> > > > > many other things could be working against you. For example, in
> > our
> > > > > a

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

2018-09-21 Thread OmPrakash Muppirala
Alex said in his last email that the repos are ready.  Will try in a few
minutes.

Thanks,
Om

On Fri, Sep 21, 2018, 7:24 AM Piotr Zarzycki 
wrote:

> Om,
>
> In my opinion you have everything ready to go! Since develop is ready
> probably you will start doing steps from the beginning, so in the results
> we will get branches release/0.9.4. However they already exists, because
> of
> my previous attempt.
>
> Maybe before you even start they need to be removed.
>
> Thanks,
> Piotr
>
>
>
> pt., 21 wrz 2018 o 16:16 OmPrakash Muppirala 
> napisał(a):
>
> > So am I clear to try and release?  Or should I wait for any other feature
> > or bug?
> >
> > Thanks,
> > Om
> >
> > On Fri, Sep 21, 2018, 6:20 AM Carlos Rovira 
> > wrote:
> >
> > > Hi Alex
> > >
> > > El vie., 21 sept. 2018 a las 3:06, Alex Harui
> ( > >)
> > > escribió:
> > >
> > > > I made some adjustments to the repos so that they "should" be ready
> to
> > > run
> > > > the scripts and produce the 0.9.4 release.  Of course, I could be
> > wrong.
> > > > We'll see how Om fares.
> > > >
> > > >
> > > so cool :)
> > >
> > >
> > > > I also put in a change that should fix the dependencies issue.  So
> the
> > > > remaining questions are around the AMF problem.  I'm thinking of
> > looking
> > > > into what it takes to support Small Messages.  However, I don't know
> > > > anything about them.  How often will migrating people be using Small
> > > > Messages?  Is it fair to tell them to turn off Small Messages?
> > > >
> > >
> > > I think for now, that small messages is a BlazeDS feature. I search for
> > > ZendAMF small messages and didn't fin d anything. So my bet is that
> small
> > > messages is something only present in BlazeDS and Data Services Adobe
> > > software.
> > >
> > > In the other hand, I'll be check new info from Darrell in 1-2 hours
> from
> > > now, but I think the problem with ZendAMF could be something like the
> one
> > > happened with coldfusion where ArrayCollection needs some special
> > > treatment. I asked Darryl to start with simple connections like we have
> > in
> > > our example (send and receive a String, then a simple object, and so
> > > on...). I think is not good to start trying from a real app scenario
> > where
> > > many other things could be working against you. For example, in our
> > > application, we have set up an additional encoding to byte array.
> > Something
> > > that even I was completely forget, and when I started to try AMF, I was
> > > always getting nothing until I reach to that point.
> > >
> > > So, as I said before, nothing should stop us to release now. If things
> go
> > > ok, Harbs will be next release manager, and I hope to be the next one
> :)
> > >
> > > Thanks
> > >
> > >
> > >
> > > >
> > > > Thanks,
> > > > -Alex
> > > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


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

2018-09-21 Thread OmPrakash Muppirala
So am I clear to try and release?  Or should I wait for any other feature
or bug?

Thanks,
Om

On Fri, Sep 21, 2018, 6:20 AM Carlos Rovira  wrote:

> Hi Alex
>
> El vie., 21 sept. 2018 a las 3:06, Alex Harui ()
> escribió:
>
> > I made some adjustments to the repos so that they "should" be ready to
> run
> > the scripts and produce the 0.9.4 release.  Of course, I could be wrong.
> > We'll see how Om fares.
> >
> >
> so cool :)
>
>
> > I also put in a change that should fix the dependencies issue.  So the
> > remaining questions are around the AMF problem.  I'm thinking of looking
> > into what it takes to support Small Messages.  However, I don't know
> > anything about them.  How often will migrating people be using Small
> > Messages?  Is it fair to tell them to turn off Small Messages?
> >
>
> I think for now, that small messages is a BlazeDS feature. I search for
> ZendAMF small messages and didn't fin d anything. So my bet is that small
> messages is something only present in BlazeDS and Data Services Adobe
> software.
>
> In the other hand, I'll be check new info from Darrell in 1-2 hours from
> now, but I think the problem with ZendAMF could be something like the one
> happened with coldfusion where ArrayCollection needs some special
> treatment. I asked Darryl to start with simple connections like we have in
> our example (send and receive a String, then a simple object, and so
> on...). I think is not good to start trying from a real app scenario where
> many other things could be working against you. For example, in our
> application, we have set up an additional encoding to byte array. Something
> that even I was completely forget, and when I started to try AMF, I was
> always getting nothing until I reach to that point.
>
> So, as I said before, nothing should stop us to release now. If things go
> ok, Harbs will be next release manager, and I hope to be the next one :)
>
> Thanks
>
>
>
> >
> > Thanks,
> > -Alex
> >
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


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

2018-09-20 Thread OmPrakash Muppirala
The last time I tried to release, it was on  Windows PC.  Some tweaks were
required.  Also, I would say that the release process was too automated 
As a result I was not able to figure out what exaxtly broke, etc.

FWIW, I have a Mac now.  I can try again if Piotr wants to take a break.

Getting an automated release script working flawlessly takes multiple
releases.  Remember, as with any software, such scripts will have bugs and
we need to catch them and fix them.

Unfortunately, one such bug was that for the 0.9.2 release, what got
published to npm was versioned at 0.9.3.  We have since fixed that issue in
our script.  But npm does not allow do overs for released artifacts.

We have learnt our lesson, lets move on please ☺

Thanks,
Om

On Thu, Sep 20, 2018, 12:53 AM Carlos Rovira 
wrote:

> Hi Alex,
> thanks you see it in the list of unread messages and will go to say that I
> found it.
> I'll take a look  now
>
>
> El jue., 20 sept. 2018 a las 9:44, Alex Harui ()
> escribió:
>
> >
> >
> > On 9/19/18, 11:49 PM, "Carlos Rovira"  wrote:
> >
> > Hi Alex,
> >
> > what Zend-AMF issue you refer? can you post the link to that issue?
> > thanks
> >
> > https://lists.apache.org/list.html?us...@royale.apache.org
> >
> > PD: about your preoccupation, we'll have issues for many months to
> > come. I
> > see each day in Jewel as I go here and there fixing or completing
> > issues I
> > find, so I think is ok release with that issues so people can "play
> > with
> > the toy".
> >
> >
> >
> > So, my opinion is that, if someone what to release, we should not
> wait
> > for
> > anything...we have many things to add, solve, fix, that one or two
> > will not
> > make a difference for me. As I said, maybe wait for release, could be
> > worse
> > in terms of potential users we can loose in that time.
> >
> > Of course there will be lots of issues to fix.  But some seem bigger than
> > others, and IMO, make the difference between whether Royale leaves the
> > impression of being a product or a toy.  If your app won't run because
> the
> > dependencies aren't right, or AMF doesn't work, will they help fix it, or
> > wait, or go somewhere else?
> >
> > If you want to release now, then you have to promise to delay what you
> > were planning to work on to handle new customer issues.  Because that's
> > what always happens to me.   By waiting until Alina hits an important
> > milestone helps keep a user we know and want to make successful.
> >
> > -Alex
> >
> >
> >
> >
> > El jue., 20 sept. 2018 a las 2:47, Alex Harui
> > ()
> > escribió:
> >
> > > The key question for me is what Carlos wrote:  " I'm trying to fix
> > and get
> > > things as most usable as possible in
> > > Jewel to avoid many changes post release"
> > >
> > > I always wonder if it helps or hurts to draw attention to the
> > release when
> > > we know there's good chance someone is going to hit a known bug.
> > I'd like
> > > to see if we can fix the issues brought up by some new users.  Such
> > as:
> > >
> > > 1)
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F297%23issuecomment-422870607data=02%7C01%7Caharui%40adobe.com%7C7b170880a70a4b8d340c08d61ec539b7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636730229757292613sdata=54aFEiUJ%2FRTCiBooZaJADt9CvYamAcvzNyWY1wP0%2Fjg%3Dreserved=0
> > >
> > > 2) the Zend-AMF issue.  A more robust AMF might be worth the wait.
> > >
> > > Those of you who want to release soon should promise to investigate
> > any
> > > dependency or AMF issues brought up by new users.  When we release
> > with
> > > issues like these, not only does it cost me the time to be the RM,
> > but also
> > > seems to cost me the time to investigate and respond to the issues
> > brought
> > > up afterwards.
> > >
> > > My 2 cents,
> > > -Alex
> > >
> > > On 9/19/18, 2:59 PM, "Carlos Rovira" 
> > wrote:
> > >
> > > Hi,
> > >
> > > I certainly can position clearly: Community is waiting and we
> are
> > > getting
> > > momentum, each day we get 1-2 new people in twitter following,
> > so it
> > > seems
> > > we are getting some traction. If we release now, those
> > interested in
> > > Royale
> > > would finally start to get its hands dirty and try things,
> > releasing
> > > later
> > > could make we loose that people interested and potential
> > community. In
> > > the
> > > other hand, I'm trying to fix and get things as most usable as
> > > possible in
> > > Jewel to avoid many changes post release. For example today
> make
> > some
> > > needed changes to jewel layouts that make more robust now, and
> > > although we
> > > make changes later, many of them will be more internally (or at
> > least I
> > > want to get 

Re: [Discuss] Start release process 0.9.3

2018-09-11 Thread OmPrakash Muppirala
+1 for releasing sooner than later :-)
I plan to make some time to test things out.

Thanks,
Om

On Tue, Sep 11, 2018 at 10:55 AM Piotr Zarzycki 
wrote:

> No problem. Thank you! If I start anything with release that would be
> tomorrow morning or evening my time.
>
> Piotr
>
> wt., 11 wrz 2018 o 19:54 Harbs  napisał(a):
>
> > I’m going to spend a few minutes now to see if I can resolve this simply.
> > If not, I’ll revert.
> >
> > Harbs
> >
> > > On Sep 11, 2018, at 8:50 PM, Piotr Zarzycki  >
> > wrote:
> > >
> > > Hi Harbs,
> > >
> > > It would be great if you could do that. You could bring back changes
> > again
> > > after release and discuss whatever needed.
> > > I think we are using following version from 20170626.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > wt., 11 wrz 2018 o 19:39 Harbs  napisał(a):
> > >
> > >> I can revert the changes if that’s what folks want. We’re going to
> have
> > >> trace calls output if I do that, but we can resolve that for the next
> > >> release.
> > >>
> > >> I’m going to see if a different version of the closure compiler plays
> > >> better. The latest version throws a NoSuchMethod error on
> > >> com.google.javascript.jscomp.CompilerOptions.setInlineLocalFunctions.
> > >>
> > >> Anyone know which version we’re using now?
> > >>
> > >>> On Sep 11, 2018, at 9:09 AM, Carlos Rovira 
> > >> wrote:
> > >>>
> > >>> I think is better move that changes to a branch and release.
> > >>> thanks
> > >>>
> > >>> El lun., 10 sept. 2018 a las 20:59, Piotr Zarzycki (<
> > >>> piotrzarzyck...@gmail.com>) escribió:
> > >>>
> >  Harbs,
> > 
> >  Can you comment on that ? Any chance to move that changes to branch
> ?
> > 
> >  Thanks,
> >  Piotr
> > 
> >  pon., 10 wrz 2018 o 20:54 Alex Harui 
> >  napisał(a):
> > 
> > > Yes.  I think we are using the wrong annotation for variable number
> > of
> > > parameters.
> > >
> > > -Alex
> > >
> > > On 9/10/18, 11:49 AM, "Piotr Zarzycki"  >
> >  wrote:
> > >
> > >   Alex,
> > >
> > >   What trace hack are you referring to ? This is related what Harbs
> > > commits ?
> > >
> > >   Thanks,
> > >   Piotr
> > >
> > >   pon., 10 wrz 2018 o 20:47 Alex Harui 
> > > napisał(a):
> > >
> > >> FWIW, I am not in favor of releasing with the current trace hack
> in
> > > the
> > >> compiler.  But if other's are ok with it, I'm not going to make a
> > > big deal
> > >> out of it, I'll just abstain from voting.
> > >>
> > >> -Alex
> > >>
> > >> On 9/10/18, 1:15 AM, "Piotr Zarzycki" 
> > > wrote:
> > >>
> > >>   Hi,
> > >>
> > >>   I have prepared today all stuff which is needed for making RC
> > > branch. I
> > >>   will check whether everything is working tomorrow. In the other
> > > words
> > >>   probably tomorrow I will push RC1 branch.
> > >>
> > >>   Thanks,
> > >>   Piotr
> > >>
> > >>   sob., 8 wrz 2018 o 18:55 Piotr Zarzycki <
> > > piotrzarzyck...@gmail.com>
> > >>   napisał(a):
> > >>
> > >>> Hi Guys,
> > >>>
> > >>> I see that typedefs build is up and running. Is there
> >  anything
> > >> important
> > >>> which you would like to add?
> > >>>
> > >>> I wanted to start on Monday playing with release.
> > >>>
> > >>> Thanks,
> > >>> Piotr
> > >>>
> > >>> On Thu, Sep 6, 2018, 6:05 PM Piotr Zarzycki <
> > >> piotrzarzyck...@gmail.com>
> > >>> wrote:
> > >>>
> >  Hi Alex,
> > 
> >  Is there anything I need to know before I jump into your
> > > notes [1]
> > >> and
> >  start play with develop for release ?
> > 
> >  [1]
> > >>
> > >
> > 
> > >>
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notesdata=02%7C01%7Caharui%40adobe.com%7Cf8dac71af4ff417b97c008d6174e1dd4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636722021606204100sdata=njV1vRpOrRyftdwcr17NLQpu3jYwS%2FQ7evR90iqEFBo%3Dreserved=0
> > 
> >  Thanks,
> >  Piotr
> > 
> >  czw., 6 wrz 2018 o 09:08 Piotr Zarzycki <
> > > piotrzarzyck...@gmail.com>
> >  napisał(a):
> > 
> > > Hi Guys,
> > >
> > > I was trying to check Tour De Flex if it has the same issue
> > > as the
> > >> rest
> > > of MX examples. In order to do that I would like to build
> > >> Framework using
> > > ANT. I got it working couple of days ago, but now it's
> > > constantly
> > >> failing.
> > > Pixel blender is downloaded corrupted. [1] Do you have any
> > > idea
> > >> why it is
> > > happen ?
> > >
> > > When I reach url directly through the browser I'm able to
> > > download
> > >> good
> > > file.
> > >
> > > 

Re: [Discuss] Start release process 0.9.3

2018-08-23 Thread OmPrakash Muppirala
Yes, since 0.9.3 was already pushed out via npm [1], it would be best if we
skip to 0.9.4

Thanks,
Om

[1] https://www.npmjs.com/package/@apache-royale/royale-js

On Thu, Aug 23, 2018 at 1:53 PM Piotr Zarzycki 
wrote:

> Hi Guys,
>
> It's been a while since last version of Royale was released. I would like
> to start process of releasing current version no matter in what state it is
> right now. I know that we have probably unfinished discussion about some
> core changes. I'm suggesting leave it for the next release. I'm volunteer
> to be release manager. I will study carefully what we have here [1] and I
> hope to get help with all of the issues.
>
> I see that we have failing typedefs - I cleaned up workspace and run build
> again. If #576 fail I will ask infra for advice. [2]
>
> Om,
>
> Do I need to know anything in case of release Royale to npm ? Your last
> suggestion here [3] is still up ?
>
> Alex,
>
> What about emulation branch - Can I merge it into develop ?
>
> Is there anything what can hold that release ?
>
> [1] https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
> [2] https://builds.apache.org/job/royale-typedefs/
> [3]
>
> http://apache-royale-development.20373.n8.nabble.com/0-9-3-Release-tp3872p4520.html
>
> Thanks,
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


Re: New blog example post "Using View States to show or hide content"

2018-06-07 Thread OmPrakash Muppirala
Hey, I am seeing a 404 error now.  Did the url change?

Thanks,
Om

On Thu, Jun 7, 2018, 2:31 AM Carlos Rovira  wrote:

> Great Harbs! As many of us making changes on website, we can move Royale
> out there better! :)
>
> Thanks!
>
>
> 2018-06-07 11:21 GMT+02:00 Harbs :
>
> > I made the changes and they are live.
> >
> > Thanks for the directions. :-)
> >
> > Harbs
> >
> > > On Jun 7, 2018, at 12:14 PM, Carlos Rovira 
> > wrote:
> > >
> > > Hi Harbs
> > >
> > > just let you know that maybe you are having a hard time seeing the
> > changes
> > > reflected in public site. I found this issue in my last change, and
> seems
> > > to be something related to apache infrastructure working slow. Until
> now
> > > changes use to be ready in seconds, this days seems to behave somewhat
> > > strange and can be ready in minutes, but finally use to work. If this
> > > strange behavior continues, we can open some jira issue.
> > >
> > > Only let you know so you can get mad and be patience while all gets
> > > published
> > >
> > > thanks
> > >
> > >
> > >
> > > 2018-06-07 10:04 GMT+02:00 Carlos Rovira :
> > >
> > >> Hi Harbs,
> > >>
> > >> steps to make this:
> > >>
> > >> 1.- log into royale.codeoscopic.com (since is a WP site go to
> /wp-admin
> > >> and insert your credentials)
> > >> 2.- go to *settings -> Codecolorer *(is the plugin that create the
> > syntax
> > >> coloring for MXML and AS3 code)
> > >> 3.- change the setting for height to what you prefer, right now is
> 300px
> > >> 4.- check some post and see has the height ok
> > >> 5.- go to "*Simply Static*" and click big blue button to generate the
> > >> entire static site
> > >> 6.- download the zip
> > >> 7.- overlay all the zip over your local royale website folder
> > >> 8.- commit the diff changes, this will make that in few seconds the
> site
> > >> will be published automatically
> > >> 9.- see your changes published ;)
> > >>
> > >> Let me know, if you have any problem
> > >>
> > >>
> > >>
> > >> 2018-06-07 9:53 GMT+02:00 Harbs :
> > >>
> > >>> FWIW, I tried  to remove that from the page, but it had no effect. I
> > >>> don’t know why.
> > >>>
> > >>> I also tried to see how it was constructed in WordPress and I
> couldn’t
> > >>> see the code block at all. What was I missing there?
> > >>>
> > >>> Harbs
> > >>>
> > >>>> On Jun 7, 2018, at 10:50 AM, Carlos Rovira  >
> > >>> wrote:
> > >>>>
> > >>>> Hi Om,
> > >>>>
> > >>>> thanks!, ok, I'll try to change height of code view for the current
> > >>>> examples in the next update :)
> > >>>>
> > >>>> 2018-06-06 20:52 GMT+02:00 OmPrakash Muppirala :
> > >>>>
> > >>>>> Thanks for this, Carlos!
> > >>>>>
> > >>>>> The snippet only shows 15 lines and then we need to scroll to see
> the
> > >>>>> rest.  Can we make it show all the code by default?
> > >>>>>
> > >>>>> Regards,
> > >>>>> Om
> > >>>>>
> > >>>>> On Wed, Jun 6, 2018 at 9:48 AM, Carlos Rovira <
> > carlosrov...@apache.org
> > >>>>
> > >>>>> wrote:
> > >>>>>
> > >>>>>> Hi,
> > >>>>>>
> > >>>>>> new blog post online:
> > >>>>>>
> > >>>>>> https://royale.apache.org/using-view-states-to-show-or-
> > hide-content/
> > >>>>>>
> > >>>>>> Enjoy! :)
> > >>>>>>
> > >>>>>> --
> > >>>>>> Carlos Rovira
> > >>>>>> http://about.me/carlosrovira
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> --
> > >>>> Carlos Rovira
> > >>>> http://about.me/carlosrovira
> > >>>
> > >>>
> > >>
> > >>
> > >> --
> > >> Carlos Rovira
> > >> http://about.me/carlosrovira
> > >>
> > >>
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


Re: New blog example post "Using View States to show or hide content"

2018-06-06 Thread OmPrakash Muppirala
Thanks for this, Carlos!

The snippet only shows 15 lines and then we need to scroll to see the
rest.  Can we make it show all the code by default?

Regards,
Om

On Wed, Jun 6, 2018 at 9:48 AM, Carlos Rovira 
wrote:

> Hi,
>
> new blog post online:
>
> https://royale.apache.org/using-view-states-to-show-or-hide-content/
>
> Enjoy! :)
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>


Re: Problem with Debugger in VSCode

2018-06-06 Thread OmPrakash Muppirala
Curious if simply calling debugger; will help here?

Will that statement crosscompile in Royale?

Thanks,
Om


On Wed, Jun 6, 2018, 10:18 AM Josh Tynjala  wrote:

> You might be running into this issue (Debugger will not stop at
> breakpoints on startup with Apache Royale):
>
>
> https://github.com/BowlerHatLLC/vscode-nextgenas/wiki/Common-issues#debugger-will-not-stop-at-breakpoints-on-startup-with-apache-royale
>
> It seems like VSCode can't connect with the browser's debugger protocol
> fast enough to register the breakpoint before the startup code has already
> finished running.
>
> A good way to check if you're running into this issue is to add some kind
> of click listener with a breakpoint. By the time you can interact with the
> app, the debugger should be fully connected.
>
> - Josh
>
> On 2018/06/05 19:50:40, Piotr Zarzycki  wrote:
> > Hi Guys,
> >
> > Does anyone who is using VSCode has problem with debugging app? I've
> > created Hello World app and tried to debug it but debugger cannot connect
> > with app at all. When I hit Menu "Debug" -> "Start Debugging" -
> Application
> > has been launched, but debugger seems to be dead, no stop on breakpoints.
> >
> > My asconfig [1], launch.json [2]. I'm using JS only Nighly build of
> Royale
> > - I have just tested with build number #926.
> >
> > VSCode version: Version 1.23.1
> > AS3 & MXML Engine: 0.12.0
> >
> > Anyone experience the same ? Or can check whether have the same problem?
> >
> > [1] https://paste.apache.org/ulBB
> > [2] https://paste.apache.org/g8I5
> >
> > Thanks,
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
> >
>


Re: Problem with Debugger in VSCode

2018-06-05 Thread OmPrakash Muppirala
I've seen some flakiness with this in the past.  Some things that could
help is: after starting the app in the browser, open the developer console,
then go back to VS and hit the reload button.  That should activate the
debugger.

Another thing, is try using Chrome as your browser?

Hope that helps.

Thanks,
Om

On Tue, Jun 5, 2018 at 12:50 PM, Piotr Zarzycki 
wrote:

> Hi Guys,
>
> Does anyone who is using VSCode has problem with debugging app? I've
> created Hello World app and tried to debug it but debugger cannot connect
> with app at all. When I hit Menu "Debug" -> "Start Debugging" - Application
> has been launched, but debugger seems to be dead, no stop on breakpoints.
>
> My asconfig [1], launch.json [2]. I'm using JS only Nighly build of Royale
> - I have just tested with build number #926.
>
> VSCode version: Version 1.23.1
> AS3 & MXML Engine: 0.12.0
>
> Anyone experience the same ? Or can check whether have the same problem?
>
> [1] https://paste.apache.org/ulBB
> [2] https://paste.apache.org/g8I5
>
> Thanks,
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


Re: 0.9.3 Release

2018-05-16 Thread OmPrakash Muppirala
On Wed, May 16, 2018, 9:42 AM Harbs <harbs.li...@gmail.com> wrote:

> Can we make sure the release does not have any breaking changes currently
> in develop?


The fixes need to go into develop so that we can simply cut a release
branch of off develop.  If not we will have to cherry pick.

What is the status of develop?  Are there any tickets we can keep track of?

Thanks,
Om



> > On May 16, 2018, at 2:58 AM, OmPrakash Muppirala <bigosma...@gmail.com>
> wrote:
> >
> > On Mon, May 14, 2018 at 12:56 PM, Alex Harui <aha...@adobe.com  aha...@adobe.com>> wrote:
> >
> >> Update:  I’ve been trying to get the release script to work on Windows
> >> with Powershell.  I didn’t have to go through the links Om used.  It
> just
> >> worked for me, but I’ve been getting other failures that I’ve been
> cleaning
> >> up.  Annoyingly, I have to reboot my computer before each attempt
> because
> >> something makes the repo folder appear locked until I reboot.
> >>
> >>
> >>
> >> So finally, today, I was able to reproduce Om’s issue about Git Add, but
> >> it is really about the command-line for Git Add being too long, not
> about
> >> filenames being too long.  I found this PR in the Maven project
> >> https://github.com/apache/maven-scm/pull/30.  I’m tempted to wait until
> >> the next Maven release so we don’t have to spend time refactoring our
> build
> >> scripts to try to work around it.
> >>
> >
> > Alex, I think that should 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 node.js and npm?  It appears that the
> > version mismatches are causing the `npm WARN tar invalid entry ` logs
> > during installation.  That should hopefully fix:
> > https://github.com/apache/royale-asjs/issues/231 <
> https://github.com/apache/royale-asjs/issues/231>
> >
> > Thanks,
> > Om
> >
> >
> >>
> >>
> >> Thanks,
> >>
> >> -Alex
> >>
> >>
> >>
> >> *From: *"omup...@gmail.com" <omup...@gmail.com> on behalf 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 command:
> >>
> >>> ant -f releasecandidate.xml "-Drelease.version=0.9.3" -Drc=1 maven
> >> -Dbrowser="/mnt/c/Program Files/Mozilla Firefox/firefox.exe"
> >>
> >>
> >>
> >> I could not fix Git Bash to use gpg-agent.  The gpg and gpg-agent were
> >> indeed running two different versions.  I dint want to take the risk to
> >> upgrade either.
> >>
> >>
> >>
> >> So, I figured out how to get PowerShell working by following the steps
> >> here:
> >>
> >> https://haacked.com/archive/2011/12/13/better-git-with-powershell.aspx/
> >> <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhaacked.com%2Farchive%2F2011%2F12%2F13%2Fbetter-git-with-powershell.aspx%2F=02%7C01%7Caharui%40adobe.com%7C06a1254b3e6a444c187208d5b4479214%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636613141894587256=06zTLxxoXtuu2H9Wb75itVLiV7yuamBvi6t5l6NOr8E%3D=0
> >
> >>
> >> https://haacked.com/archive/2011/12/19/get-git-for-windows.aspx/
> >> <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhaacked.com%2Farchive%2F2011%2F12%2F19%2Fget-git-for-windows.aspx%2F=02%7C01%7Caharui%40adobe.com%7C06a1254b3e6a444c187208d5b4479214%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636613141894587256=gIqBNB5HORzxt%2BDlcENBWpYYlNe2w8YgUWLSL16KZ4s%3D=0
> >
> >>
> >>
> >>
> >> The last issue I faced was:
> >>
> >> There were too many files in the git add command which caused the
> filename
> >> too long issue.  I tried to fix it by following directions here:
> >>
> >> https://ourcodeworld.com/articles/read/109/how-to-
> >> solve-filename-too-long-error-in-git-powershell-and-github-
> >> application-for-windows
> >> <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fourcodeworld.com%2Farticles%2Fread%2F109%2Fhow-to-solve-filename-too-long-error-in-git-p

Re: 0.9.3 Release

2018-05-15 Thread OmPrakash Muppirala
On Mon, May 14, 2018 at 12:56 PM, Alex Harui <aha...@adobe.com> wrote:

> Update:  I’ve been trying to get the release script to work on Windows
> with Powershell.  I didn’t have to go through the links Om used.  It just
> worked for me, but I’ve been getting other failures that I’ve been cleaning
> up.  Annoyingly, I have to reboot my computer before each attempt because
> something makes the repo folder appear locked until I reboot.
>
>
>
> So finally, today, I was able to reproduce Om’s issue about Git Add, but
> it is really about the command-line for Git Add being too long, not about
> filenames being too long.  I found this PR in the Maven project
> https://github.com/apache/maven-scm/pull/30.  I’m tempted to wait until
> the next Maven release so we don’t have to spend time refactoring our build
> scripts to try to work around it.
>

Alex, I think that should 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 node.js and npm?  It appears that the
version mismatches are causing the `npm WARN tar invalid entry ` logs
during installation.  That should hopefully fix:
https://github.com/apache/royale-asjs/issues/231

Thanks,
Om


>
>
> Thanks,
>
> -Alex
>
>
>
> *From: *"omup...@gmail.com" <omup...@gmail.com> on behalf 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 command:
>
> > ant -f releasecandidate.xml "-Drelease.version=0.9.3" -Drc=1 maven
> -Dbrowser="/mnt/c/Program Files/Mozilla Firefox/firefox.exe"
>
>
>
> I could not fix Git Bash to use gpg-agent.  The gpg and gpg-agent were
> indeed running two different versions.  I dint want to take the risk to
> upgrade either.
>
>
>
> So, I figured out how to get PowerShell working by following the steps
> here:
>
> https://haacked.com/archive/2011/12/13/better-git-with-powershell.aspx/
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhaacked.com%2Farchive%2F2011%2F12%2F13%2Fbetter-git-with-powershell.aspx%2F=02%7C01%7Caharui%40adobe.com%7C06a1254b3e6a444c187208d5b4479214%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636613141894587256=06zTLxxoXtuu2H9Wb75itVLiV7yuamBvi6t5l6NOr8E%3D=0>
>
> https://haacked.com/archive/2011/12/19/get-git-for-windows.aspx/
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhaacked.com%2Farchive%2F2011%2F12%2F19%2Fget-git-for-windows.aspx%2F=02%7C01%7Caharui%40adobe.com%7C06a1254b3e6a444c187208d5b4479214%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636613141894587256=gIqBNB5HORzxt%2BDlcENBWpYYlNe2w8YgUWLSL16KZ4s%3D=0>
>
>
>
> The last issue I faced was:
>
> There were too many files in the git add command which caused the filename
> too long issue.  I tried to fix it by following directions here:
>
> https://ourcodeworld.com/articles/read/109/how-to-
> solve-filename-too-long-error-in-git-powershell-and-github-
> application-for-windows
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fourcodeworld.com%2Farticles%2Fread%2F109%2Fhow-to-solve-filename-too-long-error-in-git-powershell-and-github-application-for-windows=02%7C01%7Caharui%40adobe.com%7C06a1254b3e6a444c187208d5b4479214%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636613141894587256=iRsnBnWzlJPLDwogRtIY%2Fl6D2%2FlENkuHAA8iPuPHvIA%3D=0>
>
> But that did not work.
>
>
>
> Thanks,
>
> Om
>
>
>
>
>
>
>
>
>
> On Sun, May 6, 2018 at 11:56 PM, Alex Harui <aha...@adobe.com> wrote:
>
> Om, what Ant target were you running that was referencing 0.9.5?
>
> I'm done for tonight, will check in the morning...
>
> Thanks,
> -Alex
>
> On 5/4/18, 10:55 PM, "Alex Harui" <aha...@adobe.com.INVALID> wrote:
>
> Hi Om,
>
> I will look into it Sunday evening.  The 0.9.2 release was created on
> my Windows machine.  0.9.1 was done on the Mac.
>
> Do you have a list of issues you ran into and solutions?  Like for the
> gpg-agent problem 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>
> Subject: Re: 0.9.3 Release
>
>
> On Fri, May 4, 2018, 1:55 PM Alex Harui <aha...@adobe.com<mailto:aha

Re: [DISCUSS] Explanation of the changes

2018-05-13 Thread OmPrakash Muppirala
It took a while for me to catch up on the series of threads on this topic.
>From what I see, on a high level, https://snag.gy/KW36yn.jpg seems to be a
better setup than https://snag.gy/JqO2ZI.jpg.  That is , Jewel must extend
from Core and not extend Basic.

Ideally we would follow these sets of principles:

1.  Backwards compatibility is important.
Even though Royale is very early in its development cycle, there are apps
using Royale in the wild.  If Basic component set is refactored, the
expectation should be that current apps should not break.  There is a
reason we use Semver.  An upgrade from 0.9.2 to 0.9.3 should NOT break
existing contracts and APIs.

2.  Royale should be more flexible.
I understand the strong viewpoints some folks have about Royale.  But what
good is an SDK with which we cannot easily build component sets.  Carlos
has been involved in building two completely different component sets (MDL,
Jewel) along with other things.  If he is raising concerns about the
framework, we all need to listen to him.  It doesn't matter if no one else
agrees with him.  I think he has earned enough credit here to voice his
opinion however unpopular it may be.

3.  DRY is not that important.
Again, given where we are with Royale's maturity, we must expect more of
such complex changes.  Insisting that we always need to be DRY leads to
more rigidity while building up the SDK.  Let folks like Carlos who are
trying out new things some leeway.  Once the main goal is achieved we can
go back and figure out the best way to keep things DRY.

Thanks,
Om



On Sat, May 12, 2018 at 1:09 AM, Carlos Rovira 
wrote:

> Hi,
>
> I'm trying here to explain with more tools the problems we had until now
> and the solution I did he past Friday.
>
> Disclaimer: This solution doesn't intend to end in the current state, and
> we can evolve to get other shape more convenient for others in this
> project. I'm sure Alex or Harbs can add up to enhance what I did greatly as
> always do.
>
> So let's go:
>
> Until now we had this kind of relation between libraries :
>
> https://snag.gy/JqO2ZI.jpg
>
> In this schema. Basic is needed always to construct an Application. That
> causes that all applications will end aggregating the used styles of the
> CSS in basic and all the classes that are linked in that way plus the tree
> of dependent classes.
>
> Until now that wasn't a problem, since we didn't care of it. That extra
> size all applications incorporated was not in out target since we only had
> Basic to construct applications. A side case was MDL but as is a "wrapper"
> around an external library, again we didn't care too much about this.
>
> Now with the new Jewel UI set, we have another UI set that although is
> based in the work in Basic is a first citizen, so for example, a Button in
> Jewel extends UIBase and not basic Button like before. So changes in Button
> or in other Basic infrastructure classes not affect Jewel at all. So
> final/leaf components are dependent of UIBase (in Core) and not anything we
> have in Basic. The same happens with Jewel TextInput, Jewel Slider, and
> more.
> For example Jewel Slider is based on input range, while Basic Slider is
> build with two buttons. So even ISlider interfaces are different in Basic
> than in Jewel.
> So key point here: final implementations should not depend one from another
> since any changes in the code of the parent will affect the children.
>
> As you can see in the schema, we have various libraries that are top level,
> some of them are optional, and for this reason are separated in library
> units (Network, Binding, Collections, and more), but Core is not optional,
> must be in all Royale Applications.
>
> Basic until now although it was a concrete final implementation of an UI
> set, was in fact needed in all Royale Applications, and that cause that
> always its CSS and its classes was baked into the final App. Only if you
> don't use visual elements you'll get rid of basic need, but that in a front
> end app is very strange right?
>
> This design caused from the begging lots of problems that started to rise
> when I first started MDL library. We have styles and behaviours that was
> not required due to the presence of unwanted CSS and classes from Basic.
>
> So for this reason a key point is that we need to bake into final app the
> resources we really need to avoid unwanted content that is not required and
> only increases size and the presence of potential bugs and not wanted
> behaviors.
>
> With the refactor we get to the following graph
>
> https://snag.gy/KW36yn.jpg
>
> Now in the final picture, we don't have the presence of all the things that
> comes with Basic when we create a Jewel application, the final developer
> don't need to be worried of any unwanted behavior that comes from Basic
> since Jewel no more requies it.
>
> But this is completely compatible with the older scenarios. People using
> Basic, 

Re: Royale CLI issues

2018-05-08 Thread OmPrakash Muppirala
Dany,

I updated my pushed a new version of cli a couple days ago.  This was
published using the latest versions of npm and node.js

Can you please try these commands and let me know how it goes?

npm install -g @apache-royale/royale-js
npm install -g @apache-royale/cli

royale new new-test
cd new-test
royale serve:debug



Thanks,
Om

On Wed, May 2, 2018 at 1:05 AM, Dany Dhondt <archeme...@mac.com> wrote:

> :) nice to know that messing things up makes your day
>
> My aim is to expand the Hello world app to a real boilerplate app in which
> a basic layout is used and where most common components are shown.
> I would also like to implement one server call (which might return some
> json) to get people started.
>
> -Dany
>
> Op 2 mei 2018 om 09:59 uur uur schreef OmPrakash Muppirala <
> bigosma...@gmail.com>:
>
> Okay, I bumped my versions and the good news is that everything is messed
> up on my computer as well :-)
>
> Thanks for your patience Dany. I will try to debug this issue soon and
> make a new release.
>
> Regards,
> Om
>
> On Wed, May 2, 2018 at 12:23 AM, Dany Dhondt <archeme...@mac.com> wrote:
>
> my-royale-app dany$ > node -v
>
>
> v8.11.1
>
>
> my-royale-app dany$ > npm -v
>
>
> 6.0.0
>
>
>
> -Dany
>
>
>
> Op 2 mei 2018 om 09:19 uur uur schreef OmPrakash Muppirala <
>
> bigosma...@gmail.com>:
>
>
> Ah that makes more sense. It looks like mxmlc (the compiler) is not able
>
> to access the Main.mxml file. So, it fails at the compilation step.
>
> Instead of erroring out right away, the server tries to load a non existent
>
> index.html.
>
>
> As someone mentioned earlier, this might be because of the npm version
>
> mismatch.
>
> Can you please let me know what your npm and node.js versions are?
>
>
> Mine are:
>
> C:\temp\royale-test\my-app>npm -v
>
> 4.3.0
>
>
> C:\temp\royale-test\my-app>node -v
>
> v7.7.1
>
>
> Thanks,
>
> Om
>
>
> On Wed, May 2, 2018 at 12:09 AM, Dany Dhondt <archeme...@mac.com> wrote:
>
>
> this is the complete error listing:
>
>
>
> my-royale-app dany$ > royale serve:debug
>
>
>
> Compiling...
>
>
>
> WARNING: An illegal reflective access operation has occurred
>
>
>
> WARNING: Illegal reflective access by com.google.common.base.
>
> internal.Finalizer
>
>
> (file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/
>
> royale-asjs/js/lib/guava.jar)
>
>
> to field java.lang.Thread.inheritableThreadLocals
>
>
>
> WARNING: Please consider reporting this to the maintainers of
>
>
> com.google.common.base.internal.Finalizer
>
>
>
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>
>
> reflective access operations
>
>
>
> WARNING: All illegal access operations will be denied in a future release
>
>
>
> Error: unable to open 'HD/Documents/ARCHEMEDIA/
>
>
> ROYALE/my-royale-app/src/Main.mxml'.
>
>
>
>
>
>
> Command failed: mxmlc /Volumes/Macintosh HD/Documents/ARCHEMEDIA/
>
>
> ROYALE/my-royale-app/src/Main.mxml -debug=true
>
>
>
> WARNING: An illegal reflective access operation has occurred
>
>
>
> WARNING: Illegal reflective access by com.google.common.base.
>
> internal.Finalizer
>
>
> (file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/
>
> royale-asjs/js/lib/guava.jar)
>
>
> to field java.lang.Thread.inheritableThreadLocals
>
>
>
> WARNING: Please consider reporting this to the maintainers of
>
>
> com.google.common.base.internal.Finalizer
>
>
>
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>
>
> reflective access operations
>
>
>
> WARNING: All illegal access operations will be denied in a future release
>
>
>
> Error: unable to open 'HD/Documents/ARCHEMEDIA/
>
>
> ROYALE/my-royale-app/src/Main.mxml'.
>
>
>
>
>
>
>
> fs.js:646
>
>
>
> return binding.open(pathModule._makeLong(path), stringToFlags(flags),
>
>
> mode);
>
>
>
> ^
>
>
>
>
> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
>
>
> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'
>
>
>
> at Object.fs.openSync (fs.js:646:18)
>
>
>
> at Object.fs.readFileSync (fs.js:551:33)
>
>
>
> at updateIndex (/usr/local/lib/node_modules/@
>
>
> apache-royale/cli/index.js:125:24)
>
>
>
> at compileDebug (/usr/local/lib/node_modules/@
>
>
> apache-royale/cli/index.js:106:9)
>
>
>
> at serveDebug (/usr/local/lib/node_modules/@
>
>
> apache-royale/cli/index.js:88:5)
>
>
>
> at Object. (/usr/local/lib/node_modules/@
>
>
> apache-royale/cli/index.js:59:13)
>
>
>
> at Module._compile (module.js:652:30)
>
>
>
> at Object.Module._extensions..js (module.js:663:10)
>
>
>
> at Module.load (module.js:565:32)
>
>
>
> at tryModuleLoad (module.js:505:12)
>
>
>
>
>
>
>
>
>
>


Re: 0.9.3 Release

2018-05-07 Thread OmPrakash Muppirala
I was running this command:
> ant -f releasecandidate.xml "-Drelease.version=0.9.3" -Drc=1 maven
-Dbrowser="/mnt/c/Program Files/Mozilla Firefox/firefox.exe"

I could not fix Git Bash to use gpg-agent.  The gpg and gpg-agent were
indeed running two different versions.  I dint want to take the risk to
upgrade either.

So, I figured out how to get PowerShell working by following the steps here:
https://haacked.com/archive/2011/12/13/better-git-with-powershell.aspx/
https://haacked.com/archive/2011/12/19/get-git-for-windows.aspx/

The last issue I faced was:
There were too many files in the git add command which caused the filename
too long issue.  I tried to fix it by following directions here:
https://ourcodeworld.com/articles/read/109/how-to-solve-filename-too-long-error-in-git-powershell-and-github-application-for-windows
But that did not work.

Thanks,
Om




On Sun, May 6, 2018 at 11:56 PM, Alex Harui <aha...@adobe.com> wrote:

> Om, what Ant target were you running that was referencing 0.9.5?
>
> I'm done for tonight, will check in the morning...
>
> Thanks,
> -Alex
>
> On 5/4/18, 10:55 PM, "Alex Harui" <aha...@adobe.com.INVALID> wrote:
>
> Hi Om,
>
> I will look into it Sunday evening.  The 0.9.2 release was created on
> my Windows machine.  0.9.1 was done on the Mac.
>
> Do you have a list of issues you ran into and solutions?  Like for the
> gpg-agent problem 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>
> Subject: Re: 0.9.3 Release
>
>
> On Fri, May 4, 2018, 1:55 PM Alex Harui <aha...@adobe.com<mailto:aharu
> i...@adobe.com>> wrote:
> Hi Om,
>
> I won’t have much time until Sunday late.  IMO, it is more important
> to get the scripts to work so people besides me can make a release.  I will
> try to take a look on Sunday and try to restore the repos back to where
> they should be.  Or are there other problems you have not solved?
>
>
>
> I reverted my changes and deleted the staging maven artifact.
>
> I have not been able to figure out where the 0.9.5 is coming from.
>
> And this might be a Mac vs Windows thing.  If you can revert things
> back to a good state, I can try with my Mac.
>
> Thanks,
> Om
> -Alex
>
> From: "omup...@gmail.com<mailto:omup...@gmail.com>" <omup...@gmail.com
> <mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala <
> bigosma...@gmail.com<mailto:bigosma...@gmail.com>>
> Date: Friday, May 4, 2018 at 12:04 PM
> To: Alex Harui <aha...@adobe.com<mailto:aha...@adobe.com>>
> Cc: "dev@royale.apache.org<mailto:dev@royale.apache.org>" <
> dev@royale.apache.org<mailto: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 any more than
> I already have.
> I tried to clean up things, but for some reason the release candidate
> script tries to build 0.9.5 now :-o  I am not sure how to fix that at this
> point.
>
> Alex, you may have to do the 0.9.3 release.  Sorry for the trouble.
>
> Thanks,
> Om
>
> On Mon, Apr 30, 2018 at 1:20 AM, Alex Harui <aha...@adobe.com aha...@adobe.com>> wrote:
> Did you try the instructions about gpg and ssh-agent in the wiki?
> https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%
> 2FRelease-Manager-Notes=02%7C01%7Caharui%40adobe.com%
> 7C5015911c5a8244a05fa408d5b24cc1cb%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636610965190205448=eTDZ73oTkid7eiaEv%
> 2BwfL4HXN0Dcu3XUB%2FPCW%2FLp3a8%3D=0<https://
> na01.safelinks.protection.outlook.com/?url=https%3A%2F%
> 2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes=
> 02%7C01%7Caharui%40adobe.com%7Ce3e881894d9f4d85a11308d5b1f1e0b9%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636610574790159284=
> pbpunrcMYrHJaOdF75nJ7SqMb%2B10Tr%2BRwLaNQiwTF3I%3D=0>
>
> Unfortunately, I have to shut down for tonight.  Will check tomorrow.
>
> -Alex
>
> From: "omup...@gmail.com<mailto:omup...@gmail.com>" <omup...@gmail.com
> <mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala <
> bigosma...@gmail.com<mailto:bigosma...@gmail.com>>
> Date: Monday, April 30, 2018 at 1:15 AM
> To: "dev@royale.apa

Re: 0.9.3 Release

2018-05-04 Thread OmPrakash Muppirala
On Fri, May 4, 2018, 1:55 PM Alex Harui <aha...@adobe.com> wrote:

> Hi Om,
>
>
>
> I won’t have much time until Sunday late.  IMO, it is more important to
> get the scripts to work so people besides me can make a release.  I will
> try to take a look on Sunday and try to restore the repos back to where
> they should be.  Or are there other problems you have not solved?
>
>
>


I reverted my changes and deleted the staging maven artifact.

I have not been able to figure out where the 0.9.5 is coming from.

And this might be a Mac vs Windows thing.  If you can revert things back to
a good state, I can try with my Mac.

Thanks,
Om

> -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.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 any more than I
> already have.
>
> I tried to clean up things, but for some reason the release candidate
> script tries to build 0.9.5 now :-o  I am not sure how to fix that at this
> point.
>
>
>
> Alex, you may have to do the 0.9.3 release.  Sorry for the trouble.
>
>
>
> Thanks,
>
> Om
>
>
>
> On Mon, Apr 30, 2018 at 1:20 AM, Alex Harui <aha...@adobe.com> wrote:
>
> Did you try the instructions about gpg and ssh-agent in the wiki?
> https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes=02%7C01%7Caharui%40adobe.com%7Ce3e881894d9f4d85a11308d5b1f1e0b9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636610574790159284=pbpunrcMYrHJaOdF75nJ7SqMb%2B10Tr%2BRwLaNQiwTF3I%3D=0>
>
>
>
> Unfortunately, I have to shut down for tonight.  Will check tomorrow.
>
>
>
> -Alex
>
>
>
> *From: *"omup...@gmail.com" <omup...@gmail.com> on behalf of OmPrakash
> 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 am getting the same error on cmd prompt, git bash and ubuntu bash
> on my windows machine.  I am pretty sure I am missing something.
>
>
>
> 
>
> [exec] [INFO] [INFO]
>
>  [exec] [INFO] [INFO] --- maven-gpg-plugin:1.6:sign
> (sign-release-artifacts) @ royale-compiler-parent ---
>
>  [exec] [INFO] gpg: gpg-agent is not available in this session
>
>  [exec] [INFO] gpg: Sorry, no terminal at all requested - can't get
> input
>
>  [exec] [INFO] [INFO]
> 
>
>  [exec] [INFO] [INFO] BUILD FAILURE
>
>  [exec] [INFO] [INFO]
> 
>
>  [exec] [INFO] [INFO] Total time: 20.027 s
>
>  [exec] [INFO] [INFO] Finished at: 2018-04-30T01:05:47-07:00
>
>  [exec] [INFO] [INFO] Final Memory: 35M/666M
>
>  [exec] [INFO] [INFO]
> 
>
>  [exec] [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-gpg-plugin:1.6:sign (sign-release-artifacts)
> on project royale-compiler-parent: Exit code: 2 -> [Help 1]
>
>  [exec] [INFO] [ERROR]
>
>  [exec] [INFO] [ERROR] To see the full stack trace of the errors,
> re-run Maven with the -e switch.
>
>  [exec] [INFO] [ERROR] Re-run Maven using the -X switch to enable full
> debug logging.
>
>  [exec] [INFO] [ERROR]
>
>  [exec] [INFO] [ERROR] For more information about the errors and
> possible solutions, please read the following articles:
>
>  [exec] [INFO] [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionException=02%7C01%7Caharui%40adobe.com%7C91ad0a4299e5458fa6cc08d5ae7280bc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636606729202066029=cbx9iZB4DhceXjAMqUl0%2BHS54IYjYMfUOFsjyS8yEC0%3D=0>
>
>  [exec] [INFO] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
>
>  [exec] [INFO]
> 

Re: 0.9.3 Release

2018-05-04 Thread OmPrakash Muppirala
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 any more than I
already have.
I tried to clean up things, but for some reason the release candidate
script tries to build 0.9.5 now :-o  I am not sure how to fix that at this
point.

Alex, you may have to do the 0.9.3 release.  Sorry for the trouble.

Thanks,
Om

On Mon, Apr 30, 2018 at 1:20 AM, Alex Harui <aha...@adobe.com> wrote:

> Did you try the instructions about gpg and ssh-agent in the wiki?
> https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes
>
>
>
> Unfortunately, I have to shut down for tonight.  Will check tomorrow.
>
>
>
> -Alex
>
>
>
> *From: *"omup...@gmail.com" <omup...@gmail.com> on behalf of OmPrakash
> 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 am getting the same error on cmd prompt, git bash and ubuntu bash
> on my windows machine.  I am pretty sure I am missing something.
>
>
>
> 
>
> [exec] [INFO] [INFO]
>
>  [exec] [INFO] [INFO] --- maven-gpg-plugin:1.6:sign
> (sign-release-artifacts) @ royale-compiler-parent ---
>
>  [exec] [INFO] gpg: gpg-agent is not available in this session
>
>  [exec] [INFO] gpg: Sorry, no terminal at all requested - can't get
> input
>
>  [exec] [INFO] [INFO] --
> --
>
>  [exec] [INFO] [INFO] BUILD FAILURE
>
>  [exec] [INFO] [INFO] --
> --
>
>  [exec] [INFO] [INFO] Total time: 20.027 s
>
>  [exec] [INFO] [INFO] Finished at: 2018-04-30T01:05:47-07:00
>
>  [exec] [INFO] [INFO] Final Memory: 35M/666M
>
>  [exec] [INFO] [INFO] --
> --
>
>  [exec] [INFO] [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-gpg-plugin:1.6:sign
> (sign-release-artifacts) on project royale-compiler-parent: Exit code: 2 ->
> [Help 1]
>
>  [exec] [INFO] [ERROR]
>
>  [exec] [INFO] [ERROR] To see the full stack trace of the errors,
> re-run Maven with the -e switch.
>
>  [exec] [INFO] [ERROR] Re-run Maven using the -X switch to enable full
> debug logging.
>
>  [exec] [INFO] [ERROR]
>
>  [exec] [INFO] [ERROR] For more information about the errors and
> possible solutions, please read the following articles:
>
>  [exec] [INFO] [ERROR] [Help 1] http://cwiki.apache.org/
> confluence/display/MAVEN/MojoExecutionException
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FMAVEN%2FMojoExecutionException=02%7C01%7Caharui%40adobe.com%7C91ad0a4299e5458fa6cc08d5ae7280bc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636606729202066029=cbx9iZB4DhceXjAMqUl0%2BHS54IYjYMfUOFsjyS8yEC0%3D=0>
>
>  [exec] [INFO] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
>
>  [exec] [INFO] --
> --
>
>  [exec] [INFO] Reactor Summary:
>
>  [exec] [INFO]
>
>  [exec] [INFO] Apache Royale: Compiler: Parent 
> FAILURE [ 25.700 s]
>
>  [exec] [INFO] Apache Royale: Compiler: Compiler-Common ...
> SKIPPED
>
>  [exec] [INFO] Apache Royale: Compiler: Test Utils 
> SKIPPED
>
>  [exec] [INFO] Apache Royale: Compiler: Externc ...
> SKIPPED
>
>  [exec] [INFO] Apache Royale: Compiler: Compiler ..
> SKIPPED
>
>  [exec] [INFO] Apache Royale: Compiler: Compiler-JX ...
> SKIPPED
>
>  [exec] [INFO] Apache Royale: Compiler: SWFUtils ..
> SKIPPED
>
>  [exec] [INFO] Apache Royale: Compiler: Debugger ..
> SKIPPED
>
>  [exec] [INFO] Apache Royale: Compiler: OEM Layer .
> SKIPPED
>
>  [exec] [INFO] Apache Royale: Royale Ant Tasks 
> SKIPPED
>
>  [exec] [INFO] Apache Royale: Royale Maven Plugin .
> SKIPPED
>
>  [exec] [INFO] --
> --
>
>  [exec] [INFO] BUILD FAILURE
>
>  [exec] [INFO] --
> --
>
>  [exec] [INFO] Total time: 2

Re: Newest little Harbs (was Re: Null pointer errors)

2018-05-02 Thread OmPrakash Muppirala
Fantastic news, Harbs.  Welcome to the little one :-)

Thanks,
Om

On Wed, May 2, 2018 at 9:10 AM, Dave Fisher  wrote:

> Harbs!
>
> Little Flexy! Mazel Tov!
>
> Regards,
> Dave
>
> > On May 2, 2018, at 9:03 AM, Alex Harui  wrote:
> >
> > That can be her middle name.
> >
> > -Alex
> >
> > PS: Really not liking Outlook 2016 on the Mac.  Can't figure out how to
> enter emojis.
> >
> > On 5/2/18, 9:01 AM, "Harbs"  wrote:
> >
> >What about Flex? FlexJS? ;-p
> >
> >> On May 2, 2018, at 6:50 PM, Alex Harui 
> wrote:
> >>
> >> Whatever you do, do not name her "Royale" __
> >
> >
> >
>
>


Re: Royale CLI issues

2018-05-02 Thread OmPrakash Muppirala
Okay, I bumped my versions and the good news is that everything is messed
up on my computer as well :-)

Thanks for your patience Dany.  I will try to debug this issue soon and
make a new release.

Regards,
Om

On Wed, May 2, 2018 at 12:23 AM, Dany Dhondt <archeme...@mac.com> wrote:

> my-royale-app dany$  > node -v
>
> v8.11.1
>
> my-royale-app dany$  > npm -v
>
> 6.0.0
>
>
> -Dany
>
>
> Op 2 mei 2018 om 09:19 uur uur schreef OmPrakash Muppirala <
> bigosma...@gmail.com>:
>
> Ah that makes more sense. It looks like mxmlc (the compiler) is not able
> to access the Main.mxml file. So, it fails at the compilation step.
> Instead of erroring out right away, the server tries to load a non existent
> index.html.
>
> As someone mentioned earlier, this might be because of the npm version
> mismatch.
> Can you please let me know what your npm and node.js versions are?
>
> Mine are:
> C:\temp\royale-test\my-app>npm -v
> 4.3.0
>
> C:\temp\royale-test\my-app>node -v
> v7.7.1
>
> Thanks,
> Om
>
> On Wed, May 2, 2018 at 12:09 AM, Dany Dhondt <archeme...@mac.com> wrote:
>
> this is the complete error listing:
>
>
> my-royale-app dany$ > royale serve:debug
>
>
> Compiling...
>
>
> WARNING: An illegal reflective access operation has occurred
>
>
> WARNING: Illegal reflective access by com.google.common.base.
> internal.Finalizer
>
> (file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/
> royale-asjs/js/lib/guava.jar)
>
> to field java.lang.Thread.inheritableThreadLocals
>
>
> WARNING: Please consider reporting this to the maintainers of
>
> com.google.common.base.internal.Finalizer
>
>
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>
> reflective access operations
>
>
> WARNING: All illegal access operations will be denied in a future release
>
>
> Error: unable to open 'HD/Documents/ARCHEMEDIA/
>
> ROYALE/my-royale-app/src/Main.mxml'.
>
>
>
>
>
> Command failed: mxmlc /Volumes/Macintosh HD/Documents/ARCHEMEDIA/
>
> ROYALE/my-royale-app/src/Main.mxml -debug=true
>
>
> WARNING: An illegal reflective access operation has occurred
>
>
> WARNING: Illegal reflective access by com.google.common.base.
> internal.Finalizer
>
> (file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/
> royale-asjs/js/lib/guava.jar)
>
> to field java.lang.Thread.inheritableThreadLocals
>
>
> WARNING: Please consider reporting this to the maintainers of
>
> com.google.common.base.internal.Finalizer
>
>
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>
> reflective access operations
>
>
> WARNING: All illegal access operations will be denied in a future release
>
>
> Error: unable to open 'HD/Documents/ARCHEMEDIA/
>
> ROYALE/my-royale-app/src/Main.mxml'.
>
>
>
>
>
>
> fs.js:646
>
>
> return binding.open(pathModule._makeLong(path), stringToFlags(flags),
>
> mode);
>
>
> ^
>
>
>
> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
>
> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'
>
>
> at Object.fs.openSync (fs.js:646:18)
>
>
> at Object.fs.readFileSync (fs.js:551:33)
>
>
> at updateIndex (/usr/local/lib/node_modules/@
>
> apache-royale/cli/index.js:125:24)
>
>
> at compileDebug (/usr/local/lib/node_modules/@
>
> apache-royale/cli/index.js:106:9)
>
>
> at serveDebug (/usr/local/lib/node_modules/@
>
> apache-royale/cli/index.js:88:5)
>
>
> at Object. (/usr/local/lib/node_modules/@
>
> apache-royale/cli/index.js:59:13)
>
>
> at Module._compile (module.js:652:30)
>
>
> at Object.Module._extensions..js (module.js:663:10)
>
>
> at Module.load (module.js:565:32)
>
>
> at tryModuleLoad (module.js:505:12)
>
>
>
>
>
>
>
>


Re: Royale CLI issues

2018-05-02 Thread OmPrakash Muppirala
Ah that makes more sense.  It looks like mxmlc (the compiler) is not able
to access the Main.mxml file.  So, it fails at the compilation step.
Instead of erroring out right away, the server tries to load a non existent
index.html.

As someone mentioned earlier, this might be because of the npm version
mismatch.
Can you please let me know what your npm and node.js versions are?

Mine are:
C:\temp\royale-test\my-app>npm -v
4.3.0

C:\temp\royale-test\my-app>node -v
v7.7.1

Thanks,
Om

On Wed, May 2, 2018 at 12:09 AM, Dany Dhondt  wrote:

> this is the complete error listing:
>
> my-royale-app dany$  > royale serve:debug
>
> Compiling...
>
> WARNING: An illegal reflective access operation has occurred
>
> WARNING: Illegal reflective access by 
> com.google.common.base.internal.Finalizer
> (file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/royale-asjs/js/lib/guava.jar)
> to field java.lang.Thread.inheritableThreadLocals
>
> WARNING: Please consider reporting this to the maintainers of
> com.google.common.base.internal.Finalizer
>
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
>
> WARNING: All illegal access operations will be denied in a future release
>
> Error: unable to open 'HD/Documents/ARCHEMEDIA/
> ROYALE/my-royale-app/src/Main.mxml'.
>
>
>
>
> Command failed: mxmlc /Volumes/Macintosh HD/Documents/ARCHEMEDIA/
> ROYALE/my-royale-app/src/Main.mxml -debug=true
>
> WARNING: An illegal reflective access operation has occurred
>
> WARNING: Illegal reflective access by 
> com.google.common.base.internal.Finalizer
> (file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/royale-asjs/js/lib/guava.jar)
> to field java.lang.Thread.inheritableThreadLocals
>
> WARNING: Please consider reporting this to the maintainers of
> com.google.common.base.internal.Finalizer
>
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
>
> WARNING: All illegal access operations will be denied in a future release
>
> Error: unable to open 'HD/Documents/ARCHEMEDIA/
> ROYALE/my-royale-app/src/Main.mxml'.
>
>
>
>
>
> fs.js:646
>
>   return binding.open(pathModule._makeLong(path), stringToFlags(flags),
> mode);
>
>  ^
>
>
> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'
>
> at Object.fs.openSync (fs.js:646:18)
>
> at Object.fs.readFileSync (fs.js:551:33)
>
> at updateIndex (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:125:24)
>
> at compileDebug (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:106:9)
>
> at serveDebug (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:88:5)
>
> at Object. (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:59:13)
>
> at Module._compile (module.js:652:30)
>
> at Object.Module._extensions..js (module.js:663:10)
>
> at Module.load (module.js:565:32)
>
> at tryModuleLoad (module.js:505:12)
>
>
>
>
>
>


Re: Royale CLI issues

2018-05-02 Thread OmPrakash Muppirala
On Tue, May 1, 2018 at 11:59 PM, Harbs <harbs.li...@gmail.com> wrote:

> The bin folder is created by the compiler while compiling the app. I have
> not been following this discussion very closely. What are you using to
> compile?
>

Please follow the steps here:
https://github.com/apache/royale-asjs/tree/develop/npm/cli to reproduce the
issue.

Thanks,
Om


>
> > On May 2, 2018, at 9:48 AM, Dany Dhondt <archeme...@mac.com> wrote:
> >
> > Hi Om,
> >
> > I tried both ways, none of them works.
> > Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'
> >
> >
> >
> > My question is: shouldn't the 'new' command create more than just one
> mxml file?
> > What script is responsible for creating the bin folder? Should it be the
> 'new' script or the 'serve' script?
> >
> > -Dany
> >
> >
> > Op 2 mei 2018 om 08:36 uur uur schreef OmPrakash Muppirala <
> bigosma...@gmail.com>:
> >
> >> On Tue, May 1, 2018 at 11:15 PM, Dany Dhondt <archeme...@mac.com>
> wrote:
> >>
> >>> Alex,
> >>>
> >>> The version number here came from package.json so it should have been
> >>> updated by someone.
> >>>
> >>> I reinstalled from the link you provided with no problem.
> >>> But running the royale server:debug [1] command gives me the same
> errors
> >>> as before.
> >>>
> >>> I noticed that when running: royale new my-royale-app, only an app
> folder
> >>> is created with a src folder in it.In this src folder, there is a
> main.mxml
> >>> file. So no other files or folders whatsoever are created by the 'new'
> >>> command.
> >>>
> >>
> >> Yes, that is the expected behavior. Currently, we ship a very simple
> >> `Hello World` app with the royale-cli tool. We can make it fancier app
> >> once we iron out all the issues.
> >>
> >>
> >>>
> >>> This explains the error:
> >>>
> >>> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
> >>> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/bin/
> js-debug/index.html'
> >>>
> >>>
> >> Hmm, the path does not seem correct. it should be
> >> .../my-royale-app/bin/js-debug/index.html instead of what is shown
> here.
> >>
> >> It appears that you are running the royale serve:debug command from the
> >> .../my-royale-app/src directory instead of from the .../my-royale-app
> >> directory.
> >>
> >> Thanks,
> >> Om
> >>
> >>
> >>> -Dany
> >>>
> >>> [1] https://github.com/apache/royale-asjs/tree/develop/npm/cli <
> https://github.com/apache/royale-asjs/tree/develop/npm/cli>
> >>> Op 2 mei 2018 om 05:13 uur uur schreef Alex Harui
> <aha...@adobe.com.INVALID
> >>> >:
> >>>
> >>> That's my windows machine that I used for 0.9.2.
> >>>
> >>> Where did it say 0.9.3? I'm trying to remember if I published the
> package
> >>> to NPM or if you did. Maybe the scripts are running or were run after
> some
> >>> versions got updated in the repos. I have not run a build on my windows
> >>> machine since the release.
> >>>
> >>> -Alex
> >>>
> >>> On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash
> Muppirala" <
> >>> omup...@gmail.com <mailto:omup...@gmail.com> on behalf of
> bigosma...@gmail.com <mailto:bigosma...@gmail.com>> wrote:
> >>>
> >>> On Tue, May 1, 2018 at 1:36 PM, Alex Harui <aha...@adobe.com.invalid>
> >>> wrote:
> >>>
> >>> > Om,
> >>> >
> >>> > I got the warnings when we released 0.9.2 but it appeared to leave a
> >>> > functional SDK. Now it is hanging for me and Dany.
> >>> >
> >>> > I don't think I've run a publish and I don't think the CI server is
> >>> > either, but you never know. Try grabbing one of the SWCs. Unzip it
> and
> >>> > swfdump the library.swf. There should be debugfile bytecodes with
> paths
> >>> to
> >>> > the source that give us a clue.
> >>> >
> >>> >
> >>> Good idea. Here is what I see in swfdump:
> >>>
> >>> 2) + 0:1 debugfile
> >>> &quo

Re: Royale CLI issues

2018-05-02 Thread OmPrakash Muppirala
On Tue, May 1, 2018 at 11:48 PM, Dany Dhondt <archeme...@mac.com> wrote:

> Hi Om,
>
> I tried both ways, none of them works.
>
> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'
>
>
>
>
>
>
Can I see the entire content of your terminal when you run these commands?


> My question is: shouldn't the 'new' command create more than just one mxml
> file?
> What script is responsible for creating the bin folder? Should it be the
> 'new' script or the 'serve' script?
>

The `royale new` command just copies a template directory (which contains
only one mxml file) into the my-royale-app/src directory.
The `royale serve:debug` command does the following:


   - Compiles the project in debug mode
   - Compiles with source map option
   - Starts a http server and serves the files from the bin/js-debug
   directory
   - Opens the default browser and navigates to http://localhost:3000
   - Listens to src folder
   - When any file changes, it will recompile the app
   - Automatically reloads the browser to show the updated application


All the logic is in here:
https://github.com/apache/royale-asjs/blob/develop/npm/cli/index.js

Thanks,
Om


> -Dany
>
>
> Op 2 mei 2018 om 08:36 uur uur schreef OmPrakash Muppirala <
> bigosma...@gmail.com>:
>
> On Tue, May 1, 2018 at 11:15 PM, Dany Dhondt <archeme...@mac.com> wrote:
>
> Alex,
>
>
> The version number here came from package.json so it should have been
>
> updated by someone.
>
>
> I reinstalled from the link you provided with no problem.
>
> But running the royale server:debug [1] command gives me the same errors
>
> as before.
>
>
> I noticed that when running: royale new my-royale-app, only an app folder
>
> is created with a src folder in it.In this src folder, there is a main.mxml
>
> file. So no other files or folders whatsoever are created by the 'new'
>
> command.
>
>
>
> Yes, that is the expected behavior. Currently, we ship a very simple
> `Hello World` app with the royale-cli tool. We can make it fancier app
> once we iron out all the issues.
>
>
>
> This explains the error:
>
>
> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
>
> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/bin/js-debug/index.html'
>
>
>
> Hmm, the path does not seem correct. it should be
> .../my-royale-app/bin/js-debug/index.html instead of what is shown here.
>
> It appears that you are running the royale serve:debug command from the
> .../my-royale-app/src directory instead of from the .../my-royale-app
> directory.
>
> Thanks,
> Om
>
>
> -Dany
>
>
> [1] https://github.com/apache/royale-asjs/tree/develop/npm/cli
>
>
> Op 2 mei 2018 om 05:13 uur uur schreef Alex Harui <aha...@adobe.com.INVALID
>
> >:
>
>
> That's my windows machine that I used for 0.9.2.
>
>
> Where did it say 0.9.3? I'm trying to remember if I published the package
>
> to NPM or if you did. Maybe the scripts are running or were run after some
>
> versions got updated in the repos. I have not run a build on my windows
>
> machine since the release.
>
>
> -Alex
>
>
> On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" <
>
> omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
>
>
> On Tue, May 1, 2018 at 1:36 PM, Alex Harui <aha...@adobe.com.invalid>
>
> wrote:
>
>
> > Om,
>
> >
>
> > I got the warnings when we released 0.9.2 but it appeared to leave a
>
> > functional SDK. Now it is hanging for me and Dany.
>
> >
>
> > I don't think I've run a publish and I don't think the CI server is
>
> > either, but you never know. Try grabbing one of the SWCs. Unzip it and
>
> > swfdump the library.swf. There should be debugfile bytecodes with paths
>
> to
>
> > the source that give us a clue.
>
> >
>
> >
>
> Good idea. Here is what I see in swfdump:
>
>
> 2) + 0:1 debugfile
>
> "C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;
>
> org\apache\royale\collections;FlattenedList.as"
>
>
> Any idea whose machine this could have been?
>
>
> Thanks,
>
> Om
>
>
>
> > -Alex
>
> >
>
> > On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
>
> > Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
>
> >
>
> > On Tue, May 1, 2018 at 8:57 AM, Alex Harui <aha...@adobe.com.invalid>
>
> > wrote:
>
> >
>
> > >

Royale CLI issues

2018-05-02 Thread OmPrakash Muppirala
On Tue, May 1, 2018 at 11:15 PM, Dany Dhondt <archeme...@mac.com> wrote:

> Alex,
>
> The version number here came from package.json so it should have been
> updated by someone.
>
> I reinstalled from the link you provided with no problem.
> But running the royale server:debug [1] command gives me the same errors
> as before.
>
> I noticed that when running: royale new  my-royale-app, only an app folder
> is created with a src folder in it.In this src folder, there is a main.mxml
> file. So no other files or folders whatsoever are created by the 'new'
> command.
>

Yes, that is the expected behavior.  Currently, we ship a very simple
`Hello World` app with the royale-cli tool.  We can make it fancier app
once we iron out all the issues.


>
> This explains the error:
>
> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
> HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/bin/js-debug/index.html'
>
>
Hmm, the path does not seem correct.  it should be
.../my-royale-app/bin/js-debug/index.html  instead of what is shown here.

It appears that you are running the royale serve:debug command from the
.../my-royale-app/src directory instead of from the .../my-royale-app
directory.

Thanks,
Om


> -Dany
>
> [1] https://github.com/apache/royale-asjs/tree/develop/npm/cli
>
> Op 2 mei 2018 om 05:13 uur uur schreef Alex Harui <aha...@adobe.com.INVALID
> >:
>
> That's my windows machine that I used for 0.9.2.
>
> Where did it say 0.9.3? I'm trying to remember if I published the package
> to NPM or if you did. Maybe the scripts are running or were run after some
> versions got updated in the repos. I have not run a build on my windows
> machine since the release.
>
> -Alex
>
> On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" <
> omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
>
> On Tue, May 1, 2018 at 1:36 PM, Alex Harui <aha...@adobe.com.invalid>
> wrote:
>
> > Om,
> >
> > I got the warnings when we released 0.9.2 but it appeared to leave a
> > functional SDK. Now it is hanging for me and Dany.
> >
> > I don't think I've run a publish and I don't think the CI server is
> > either, but you never know. Try grabbing one of the SWCs. Unzip it and
> > swfdump the library.swf. There should be debugfile bytecodes with paths
> to
> > the source that give us a clue.
> >
> >
> Good idea. Here is what I see in swfdump:
>
> 2) + 0:1 debugfile
> "C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;
> org\apache\royale\collections;FlattenedList.as"
>
> Any idea whose machine this could have been?
>
> Thanks,
> Om
>
>
> > -Alex
> >
> > On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
> > Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
> >
> > On Tue, May 1, 2018 at 8:57 AM, Alex Harui <aha...@adobe.com.invalid>
> > wrote:
> >
> > > Hi Dany,
> > >
> > > The link is directly to a tar.gz built by our CI server. No humans
> > > involved, and no special packaging for NPM. NPM says it can install
> > any
> > > tar.gz file. Try downloading the file at that link and using Mac
> > Finder to
> > > expand it into a folder. For me it expands without errors. This is
> > why I
> > > believe it is some incompatibility with NPM.
> > >
> > > If the tar.gz expands for you on Mac, you can try to "npm install"
> > the
> > > folder. Running:
> > >
> > > sudo npm install -g 
> > >
> > > seemed to work for me.
> > >
> > > -Alex
> > >
> >
> > I just tried
> > npm install @apache-royale/royale-js -g
> > on windwos and it installed just fine.
> >
> > Although, I notice that @apache-royale/royale-js@0.9.3 was
> > installed. It
> > should have installed 0.9.2. Did we publish 0.9.3 to npm by mistake?
> > Could that be related?
> >
> > Thanks,
> > Om
> >
> >
> > >
> > > On 5/1/18, 1:51 AM, "Dany Dhondt" <archeme...@mac.com> wrote:
> > >
> > > Hi Alex,
> > >
> > > I tried the direct link you provided: same result (hundreds of
> > > ‘invalid entry’ messages)
> > >
> > > My version of npm is 6.0.0
> > >
> > > downgrading to a lower npm version is not an option at this
> > moment
> > > because I’m on a production mac with crucial projects on it.
> > >
> > > Amids all the invalid entry messages, now a

Re: NPM Issues (was Re: [Discussion] "Life after FlashPlayer" post @flex lists)

2018-05-02 Thread OmPrakash Muppirala
On Tue, May 1, 2018 at 11:16 PM, Alex Harui <aha...@adobe.com.invalid>
wrote:

> I think that's a bug in releasecandidate.xml.  When you run the release
> target, it calls the update.versions target before reminding you to run the
> release.npm target.  It did not occur to me that the publishing grabbed
> files other than the tar.gz (which should have the right version in its
> files).


It appears that the npm library needs this package.json file to be passed
during an installation.  I will try to remove it and try to publish.


>   So I suppose you could try running release.npm before update.versions.
>

If my above fix does not work, I will switch the order and see if that
fixes it.

Thanks,
Om


>
> HTH,
> -Alex
>
> On 5/1/18, 11:10 PM, "omup...@gmail.com on behalf of OmPrakash
> Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
>
>  As per git history, this file was updated from 0.9.2 to 0.9.3 on
> 3/16/2018
> at around 10:40AM :
> https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fcommit%
> 2F2e6923440655c2c2314a9f3e2e1d91fa745cd6e2%23diff-
> 6515d4243f4018bb4527c9184823da7f=02%7C01%7Caharui%40adobe.com%
> 7Ca1f8ef5c36e84b2ce18508d5aff364ab%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636608382274076486=xcQE%
> 2BsDRTUvsyE8t3eUTPHRg9ojfQleqCVx7aP9vFCs%3D=0
>
> According to https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.npmjs.com%2Forg%2Fapache-royale=02%
> 7C01%7Caharui%40adobe.com%7Ca1f8ef5c36e84b2ce18508d5aff364ab%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636608382274076486=%
> 2FCSPJkc%2B6CctGw4btT%2BoX5rUSS2CAq7aE36SNop0e0g%3D=0, the 0.9.3
> release was
> made on at around 11:00 AM on the same day.
>
> I am guessing that the npm publish script was run accidentally that
> caused
> a 0.9.3 release to be pushed.
>
> Is it possible that this can happen again? i.e. are some scripts
> getting
> called when they should not be?
>
> Thanks,
> Om
>
> On Tue, May 1, 2018 at 9:44 PM, Alex Harui <aha...@adobe.com.invalid>
> wrote:
>
>     > OK, but what file would contain that string such that it shows up
> then?
> >
> > Thanks,
> > -Alex
> >
> > On 5/1/18, 9:32 PM, "OmPrakash Muppirala" <bigosma...@gmail.com>
> wrote:
> >
> > On Tue, May 1, 2018, 8:13 PM Alex Harui <aha...@adobe.com.invalid
> >
> > wrote:
> >
> > > That's my windows machine that I used for 0.9.2.
> > >
> > > Where did it say 0.9.3?
> >
> >
> > It shows up after the npm install completes.
> >
> >
> > I'm trying to remember if I published the package to NPM or if
> you did.
> > > Maybe the scripts are running or were run after some versions
> got
> > updated
> > > in the repos.  I have not run a build on my windows machine
> since the
> > > release.
> >
> >
> > >
> > >
> > >
> > >
> > > -Alex
> > >
> > > On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash
> > Muppirala"
> > > <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
> > >
> > > On Tue, May 1, 2018 at 1:36 PM, Alex Harui
> > <aha...@adobe.com.invalid>
> > > wrote:
> > >
> > > > Om,
> > > >
> > > > I got the warnings when we released 0.9.2 but it
> appeared to
> > leave a
> > > > functional SDK.  Now it is hanging for me and Dany.
> > > >
> > > > I don't think I've run a publish and I don't think the CI
> > server is
> > > > either, but you never know.  Try grabbing one of the
> SWCs.
> > Unzip it
> > > and
> > > > swfdump the library.swf.  There should be debugfile
> bytecodes
> > with
> > > paths to
> > > > the source that give us a clue.
> > > >
> > > >
> > > Good idea.  Here is what I see in swfdump:
> > >
> > > 2) + 0:1 debugfile
> > >
> > > "C:\temp\rc\royale-asjs\frameworks\projects\
> > Collecti

Re: NPM Issues (was Re: [Discussion] "Life after FlashPlayer" post @flex lists)

2018-05-02 Thread OmPrakash Muppirala
 As per git history, this file was updated from 0.9.2 to 0.9.3 on 3/16/2018
at around 10:40AM :
https://github.com/apache/royale-asjs/commit/2e6923440655c2c2314a9f3e2e1d91fa745cd6e2#diff-6515d4243f4018bb4527c9184823da7f

According to https://www.npmjs.com/org/apache-royale, the 0.9.3 release was
made on at around 11:00 AM on the same day.

I am guessing that the npm publish script was run accidentally that caused
a 0.9.3 release to be pushed.

Is it possible that this can happen again? i.e. are some scripts getting
called when they should not be?

Thanks,
Om

On Tue, May 1, 2018 at 9:44 PM, Alex Harui <aha...@adobe.com.invalid> wrote:

> OK, but what file would contain that string such that it shows up then?
>
> Thanks,
> -Alex
>
> On 5/1/18, 9:32 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote:
>
> On Tue, May 1, 2018, 8:13 PM Alex Harui <aha...@adobe.com.invalid>
> wrote:
>
> > That's my windows machine that I used for 0.9.2.
> >
> > Where did it say 0.9.3?
>
>
> It shows up after the npm install completes.
>
>
> I'm trying to remember if I published the package to NPM or if you did.
> > Maybe the scripts are running or were run after some versions got
> updated
> > in the repos.  I have not run a build on my windows machine since the
> > release.
>
>
> >
> >
> >
> >
> > -Alex
> >
> > On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash
> Muppirala"
> > <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
> >
> > On Tue, May 1, 2018 at 1:36 PM, Alex Harui
> <aha...@adobe.com.invalid>
> > wrote:
> >
> > > Om,
> > >
> > > I got the warnings when we released 0.9.2 but it appeared to
> leave a
> > > functional SDK.  Now it is hanging for me and Dany.
> > >
> > > I don't think I've run a publish and I don't think the CI
> server is
> > > either, but you never know.  Try grabbing one of the SWCs.
> Unzip it
> > and
> > > swfdump the library.swf.  There should be debugfile bytecodes
> with
> > paths to
> > > the source that give us a clue.
> > >
> > >
> > Good idea.  Here is what I see in swfdump:
> >
> > 2) + 0:1 debugfile
> >
> > "C:\temp\rc\royale-asjs\frameworks\projects\
> Collections\src\main\royale;org\apache\royale\collections;
> FlattenedList.as"
> >
> > Any idea whose machine this could have been?
> >
> > Thanks,
> > Om
> >
> >
> > > -Alex
> > >
> > > On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
> > > Muppirala" <omup...@gmail.com on behalf of
> bigosma...@gmail.com>
> > wrote:
> > >
> > > On Tue, May 1, 2018 at 8:57 AM, Alex Harui
> > <aha...@adobe.com.invalid>
> > > wrote:
> > >
> > > > Hi Dany,
> > > >
> > > > The link is directly to a tar.gz built by our CI
> server.  No
> > humans
> > > > involved, and no special packaging for NPM.  NPM says it
> can
> > install
> > > any
> > > > tar.gz file.  Try downloading the file at that link and
> using
> > Mac
> > > Finder to
> > > > expand it into a folder.  For me it expands without
> errors.
> > This is
> > > why I
> > > > believe it is some incompatibility with NPM.
> > > >
> > > > If the tar.gz expands for you on Mac, you can try to "npm
> > install"
> > > the
> > > > folder.  Running:
> > > >
> > > > sudo npm install -g 
> > > >
> > > > seemed to work for me.
> > > >
> > > > -Alex
> > > >
> > >
> > > I just tried
> > > npm install @apache-royale/royale-js -g
> > > on windwos and it installed just fine.
> > >
> > > Although, I notice th

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

2018-05-01 Thread OmPrakash Muppirala
On Tue, May 1, 2018, 8:13 PM Alex Harui <aha...@adobe.com.invalid> wrote:

> That's my windows machine that I used for 0.9.2.
>
> Where did it say 0.9.3?


It shows up after the npm install completes.


I'm trying to remember if I published the package to NPM or if you did.
> Maybe the scripts are running or were run after some versions got updated
> in the repos.  I have not run a build on my windows machine since the
> release.


>
>
>
>
> -Alex
>
> On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
> <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
>
> On Tue, May 1, 2018 at 1:36 PM, Alex Harui <aha...@adobe.com.invalid>
> wrote:
>
> > Om,
> >
> > I got the warnings when we released 0.9.2 but it appeared to leave a
> > functional SDK.  Now it is hanging for me and Dany.
> >
> > I don't think I've run a publish and I don't think the CI server is
> > either, but you never know.  Try grabbing one of the SWCs.  Unzip it
> and
> > swfdump the library.swf.  There should be debugfile bytecodes with
> paths to
> > the source that give us a clue.
> >
> >
> Good idea.  Here is what I see in swfdump:
>
> 2) + 0:1 debugfile
>
> "C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;org\apache\royale\collections;FlattenedList.as"
>
> Any idea whose machine this could have been?
>
> Thanks,
> Om
>
>
> > -Alex
> >
> > On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
> > Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com>
> wrote:
> >
> > On Tue, May 1, 2018 at 8:57 AM, Alex Harui
> <aha...@adobe.com.invalid>
> > wrote:
> >
> > > Hi Dany,
> > >
> > > The link is directly to a tar.gz built by our CI server.  No
> humans
> > > involved, and no special packaging for NPM.  NPM says it can
> install
> > any
> > > tar.gz file.  Try downloading the file at that link and using
> Mac
> > Finder to
> > > expand it into a folder.  For me it expands without errors.
> This is
> > why I
> > > believe it is some incompatibility with NPM.
> > >
> > > If the tar.gz expands for you on Mac, you can try to "npm
> install"
> > the
> > > folder.  Running:
> > >
> > > sudo npm install -g 
> > >
> > > seemed to work for me.
> > >
> > > -Alex
> > >
> >
> > I just tried
> > npm install @apache-royale/royale-js -g
> > on windwos and it installed just fine.
> >
> > Although, I notice that  @apache-royale/royale-js@0.9.3 was
> > installed.  It
> > should have installed 0.9.2.  Did we publish 0.9.3 to npm by
> mistake?
> > Could that be related?
> >
> > Thanks,
> > Om
> >
> >
> > >
> > > On 5/1/18, 1:51 AM, "Dany Dhondt" <archeme...@mac.com> wrote:
> > >
> > > Hi Alex,
> > >
> > > I tried the direct link you provided: same result
> (hundreds of
> > > ‘invalid entry’ messages)
> > >
> > > My version of npm is 6.0.0
> > >
> > > downgrading to a lower npm version is not an option at this
> > moment
> > > because I’m on a production mac with crucial projects on it.
> > >
> > > Amids all the invalid entry messages, now and then is a
> somewhat
> > > longer message like
> > >
> > > WARN⸨   ░░░⸩ ⠸ extract:@apache-royale
> /royale-js:
> > verb
> > > lock using /Users/ tar invalid entry
> > >
> > >
> > >
> > >
> > > Is it Om that created this package? This might give him an
> idea
> > of
> > > what’s going on?
> > >
> > > -Dany
> > >
> > >
> > >
> > > > Op 30 apr. 2018, om 18:39 heeft Alex Harui
> > <aha...@adobe.com.INVALID
> > > &l

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

2018-05-01 Thread OmPrakash Muppirala
On Tue, May 1, 2018 at 1:36 PM, Alex Harui <aha...@adobe.com.invalid> wrote:

> Om,
>
> I got the warnings when we released 0.9.2 but it appeared to leave a
> functional SDK.  Now it is hanging for me and Dany.
>
> I don't think I've run a publish and I don't think the CI server is
> either, but you never know.  Try grabbing one of the SWCs.  Unzip it and
> swfdump the library.swf.  There should be debugfile bytecodes with paths to
> the source that give us a clue.
>
>
Good idea.  Here is what I see in swfdump:

2) + 0:1 debugfile
"C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;org\apache\royale\collections;FlattenedList.as"

Any idea whose machine this could have been?

Thanks,
Om


> -Alex
>
> On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
> Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
>
> On Tue, May 1, 2018 at 8:57 AM, Alex Harui <aha...@adobe.com.invalid>
> wrote:
>
> > Hi Dany,
> >
> > The link is directly to a tar.gz built by our CI server.  No humans
> > involved, and no special packaging for NPM.  NPM says it can install
> any
> > tar.gz file.  Try downloading the file at that link and using Mac
> Finder to
> > expand it into a folder.  For me it expands without errors.  This is
> why I
> > believe it is some incompatibility with NPM.
> >
> > If the tar.gz expands for you on Mac, you can try to "npm install"
> the
> > folder.  Running:
> >
> > sudo npm install -g 
> >
> > seemed to work for me.
> >
> > -Alex
> >
>
> I just tried
> npm install @apache-royale/royale-js -g
> on windwos and it installed just fine.
>
> Although, I notice that  @apache-royale/royale-js@0.9.3 was
> installed.  It
> should have installed 0.9.2.  Did we publish 0.9.3 to npm by mistake?
> Could that be related?
>
> Thanks,
> Om
>
>
> >
> > On 5/1/18, 1:51 AM, "Dany Dhondt" <archeme...@mac.com> wrote:
> >
> > Hi Alex,
> >
> > I tried the direct link you provided: same result (hundreds of
> > ‘invalid entry’ messages)
> >
> > My version of npm is 6.0.0
> >
> > downgrading to a lower npm version is not an option at this
> moment
> > because I’m on a production mac with crucial projects on it.
> >
> > Amids all the invalid entry messages, now and then is a somewhat
> > longer message like
> >
> > WARN⸨   ░░░⸩ ⠸ extract:@apache-royale/royale-js:
> verb
> > lock using /Users/ tar invalid entry
> >
> >
> >
> >
> > Is it Om that created this package? This might give him an idea
> of
> > what’s going on?
> >
> > -Dany
> >
> >
> >
> > > Op 30 apr. 2018, om 18:39 heeft Alex Harui
> <aha...@adobe.com.INVALID
> > <mailto:aha...@adobe.com.INVALID>> het volgende geschreven:
> > >
> > > Hmm.  I'm getting that too on my Mac.  It used to complete
> anyway
> > and work, but now it appears to be hanging.
> > >
> > > The internet hints that it might have to do with the version
> of NPM
> > used to create the package vs the  NPM we are using to install.  Om,
> did
> > you create the packages for publishing to NPM?  If so, what version
> did you
> > use?
> > >
> > > On the other hand, just installing the nightly build also
> gives a
> > ton of those warnings but seems to complete and produce a runnable
> compiler.
> > >
> > > sudo npm install -g https://na01.safelinks.
> protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks&
> data=02%7C01%7Caharui%40adobe.com%7C00079fd32a194a4caf1b08d5af8bd09e%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636607937396983186=D%
> 2BedD6Pv8Eh7GSR8q1dLpGxi6RL5R43uCdchzXoECD0%3D=0.
> > protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
> > westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
> > jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
> > royale-0.9.3-bin-js.tar.gz=02%7C01%7Caharui%40adobe.com%
> > 7C0c405d2ff9134638451608d5af40c2f1%7Cfa7b1b5a7b34438794aed2c178de
> > cee1%7C0%7C0%7C636607615050264364=zKrYmme3fourKgDPSyULPEiiR5%
> > 2FfXBUXmGQ49qdY0aM%3D=0 <https

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

2018-05-01 Thread OmPrakash Muppirala
On Tue, May 1, 2018 at 8:57 AM, Alex Harui <aha...@adobe.com.invalid> wrote:

> Hi Dany,
>
> The link is directly to a tar.gz built by our CI server.  No humans
> involved, and no special packaging for NPM.  NPM says it can install any
> tar.gz file.  Try downloading the file at that link and using Mac Finder to
> expand it into a folder.  For me it expands without errors.  This is why I
> believe it is some incompatibility with NPM.
>
> If the tar.gz expands for you on Mac, you can try to "npm install" the
> folder.  Running:
>
> sudo npm install -g 
>
> seemed to work for me.
>
> -Alex
>

I just tried
npm install @apache-royale/royale-js -g
on windwos and it installed just fine.

Although, I notice that  @apache-royale/royale-js@0.9.3 was installed.  It
should have installed 0.9.2.  Did we publish 0.9.3 to npm by mistake?
Could that be related?

Thanks,
Om


>
> On 5/1/18, 1:51 AM, "Dany Dhondt" <archeme...@mac.com> wrote:
>
> Hi Alex,
>
> I tried the direct link you provided: same result (hundreds of
> ‘invalid entry’ messages)
>
> My version of npm is 6.0.0
>
> downgrading to a lower npm version is not an option at this moment
> because I’m on a production mac with crucial projects on it.
>
> Amids all the invalid entry messages, now and then is a somewhat
> longer message like
>
> WARN⸨   ░░░⸩ ⠸ extract:@apache-royale/royale-js: verb
> lock using /Users/ tar invalid entry
>
>
>
>
> Is it Om that created this package? This might give him an idea of
> what’s going on?
>
> -Dany
>
>
>
> > Op 30 apr. 2018, om 18:39 heeft Alex Harui <aha...@adobe.com.INVALID
> <mailto:aha...@adobe.com.INVALID>> het volgende geschreven:
> >
> > Hmm.  I'm getting that too on my Mac.  It used to complete anyway
> and work, but now it appears to be hanging.
> >
> > The internet hints that it might have to do with the version of NPM
> used to create the package vs the  NPM we are using to install.  Om, did
> you create the packages for publishing to NPM?  If so, what version did you
> use?
> >
> > On the other hand, just installing the nightly build also gives a
> ton of those warnings but seems to complete and produce a runnable compiler.
> >
> > sudo npm install -g https://na01.safelinks.
> protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
> westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
> jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
> royale-0.9.3-bin-js.tar.gz=02%7C01%7Caharui%40adobe.com%
> 7C0c405d2ff9134638451608d5af40c2f1%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636607615050264364=zKrYmme3fourKgDPSyULPEiiR5%
> 2FfXBUXmGQ49qdY0aM%3D=0 <https://na01.safelinks.
> protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
> westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
> jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
> royale-0.9.3-bin-js.tar.gz=02%7C01%7Caharui%40adobe.com%
> 7C0c405d2ff9134638451608d5af40c2f1%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636607615050264364=zKrYmme3fourKgDPSyULPEiiR5%
> 2FfXBUXmGQ49qdY0aM%3D=0>
> >
> > I haven't tried downgrading or upgrading my version of NPM (5.6).
> Dany which version are you running?  Can you try different versions of NPM?
> >
> > HTH,
> > -Alex
> >
> > On 4/30/18, 1:11 AM, "Dany Dhondt" <archeme...@mac.com  archeme...@mac.com>> wrote:
> >
> >Hi Om,
> >
> >I did that!
> >
> >In the mean time I tried all sorts of things:
> >install 0.9.1 instead of 0.9.3
> >reinstalled npm
> >
> >nothing works
> >
> >-Dany
> >
> >
> >> Op 30 apr. 2018, om 09:59 heeft OmPrakash Muppirala <
> bigosma...@gmail.com <mailto:bigosma...@gmail.com>> het volgende
> geschreven:
> >>
> >> Dany,
> >>
> >> I haven't tested this on a Mac.  I am told that Mac users need to
> use "sudo
> >> install npm  " depending on how they installed npm.
> Perhaps
> >> you can try that out?
> >>
> >> Thanks,
> >> Om
> >>
> >> On Mon, Apr 30, 2018 at 12:54 AM, Dany Dhondt <archeme...@mac.com
> <mailto:archeme...@mac.com>> wrote:
> >>
> >>> Hi Om,
> >>>
> >>> Thanks for pointing that out.
> >>>
> >>> I’ll have a go with that scenario.
>

Re: 0.9.3 Release

2018-04-30 Thread OmPrakash Muppirala
on’t go right, I’ve had to delete tags
> and revert commits before restarting Ant at certain targets.  I still have
> hope we can make the Ant script tolerant of differences between machines so
> any PMC member can use it to cut a release.  There are a lot of steps to
> handle both Maven and Ant and NPM.
>
>
>
> Good luck,
>
> -Alex
>
>
>
> *From: *OmPrakash Muppirala <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>
> Date: Sat, Apr 28, 2018, 11:14 PM
> Subject: Re: 0.9.3 Release
> To: <dev@royale.apache.org>
>
>
>
> Ah I just realized that the releasecandidate ant script made a few commits
> on my behalf.  I had a few errors that I had to fix.  Could those failed
> runs have caused this inconsistent state?
>
>
>
> Thanks,
>
> Om
>
>
>
> On Sat, Apr 28, 2018 at 10:44 PM, OmPrakash Muppirala <
> bigosma...@gmail.com> wrote:
>
> I am getting this error:
>
>
>
>  [exec] [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-release-plugin:2.5.3:branch (default-cli) on project
> royale-framework-parent: Cannot prepare the release because you have local
> modifications :
>
>  [exec] [ERROR] [pom.xml:modified]
>
>
>
> The pom.xml has only one change:
>
>
>
>   
>
> scm:git:g...@github.com:apache/royale-asjs.git
>
> scm:git:g...@github.com:apache/royale-
> asjs.git
>
> scm:git:g...@github.com:apache/royale-asjs.git
>
> *HEAD*
>
>   
>
>
>
> changed to:
>
>
>
>   
>
> scm:git:g...@github.com:apache/royale-asjs.git
>
> scm:git:g...@github.com:apache/royale-
> asjs.git
>
> scm:git:g...@github.com:apache/royale-asjs.git
>
> *release/0.9.3*
>
>   
>
>
>
> Should I first change HEAD to release/0.9.3 before starting the release
> process?
>
> It does indeed have HEAD currently: https://github.com/
> apache/royale-asjs/blob/develop/pom.xml#L49
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fblob%2Fdevelop%2Fpom.xml%23L49=02%7C01%7Caharui%40adobe.com%7C83d9deb2f89248a812db08d5ae32f0f7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636606456217160033=cBMQ2644E%2BtmH6vBfiJzZ2DxZ7R%2FwWjs3Dd%2FjwEujjE%3D=0>
>
>
>
> Thanks,
>
> Om
>
>
>
> On Fri, Apr 27, 2018 at 10:55 PM, Alex Harui <aha...@adobe.com.invalid>
> wrote:
>
> 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, "omup...@gmail.com on behalf of OmPrakash
> Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
>
> 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 <aha...@adobe.com.invalid
> >
> wrote:
>
> > Yep, that's what we have for you to work with.  I expect there will
> be
> > things missing or needing improvement, but it will be awesome if we
> can
> > make this process work for you.  Then we can hope that anyone can
> follow
> > these instructions and use the scripts to generate a release.
> >
> > Thanks,
> > -Alex
> >
> > On 4/25/18, 12:19 AM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com>
> wrote:
> >
> > Om,
> >
> > I believe this is some starting point [1]
> >
> > [1] https://na01.safelinks.protection.outlook.com/?url=
> > https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%
> > 2FRelease-Manager-Notes=02%7C01%7Caharui%40adobe.com
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2F40adobe.com=02%7C01%7Caharui%40adobe.com%7C83d9deb2f89248a812db08d5ae32f0f7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636606456217160033=UXcD0j5Tbbz3ylbUtG%2F8MEJQuHnallIgfT4XZRAEs04%3D=0>
> %
> > 7C2fd9fa97db624afeb36808d5aa7cd94a%7Cfa7b1b5a7b34438794aed2c178de
> > cee1%7C0%7C0%7C636602375606683856=
> M6AXRZTAjFbWerTBnC7Mnk4zS2BkFv
> > fmdHLajtuOLAw%3D=0
> >
> > Piotr
> >
> > 2018-04-25 9:12 GMT+02:00 OmPrakash Mup

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

2018-04-30 Thread OmPrakash Muppirala
Dany,

I haven't tested this on a Mac.  I am told that Mac users need to use "sudo
install npm  " depending on how they installed npm.  Perhaps
you can try that out?

Thanks,
Om

On Mon, Apr 30, 2018 at 12:54 AM, Dany Dhondt  wrote:

> Hi Om,
>
> Thanks for pointing that out.
>
> I’ll have a go with that scenario.
>
> 1. (re) installing royale
> npm install @apache-royale/royale-js -g
> WARN tar invalid entry extract:@apache-royale/royale-js: verb lock using
> /Users/dany/.npm/_locks/staging-3a08f0df5026584d.lock for
> /usr/local/lib/node_modules/.staging
> WARN tar invalid entry
>
> Then hundreds of ‘invalid entry’ lines in the terminal.
>
> And finally
>
> …
>
> WARN tar invalid entry
> /usr/local/bin/asjscompc -> /usr/local/lib/node_modules/@
> apache-royale/royale-js/royale-asjs/js/bin/asjscompcnpm
> /usr/local/bin/asjsc -> /usr/local/lib/node_modules/@
> apache-royale/royale-js/royale-asjs/js/bin/asjscnpm
> /usr/local/bin/compc -> /usr/local/lib/node_modules/@
> apache-royale/royale-js/royale-asjs/js/bin/compcnpm
> /usr/local/bin/externc -> /usr/local/lib/node_modules/@
> apache-royale/royale-js/royale-asjs/js/bin/externcnpm
> /usr/local/bin/asnodec -> /usr/local/lib/node_modules/@
> apache-royale/royale-js/royale-asjs/js/bin/asnodecnpm
> /usr/local/bin/mxmlc -> /usr/local/lib/node_modules/@
> apache-royale/royale-js/royale-asjs/js/bin/mxmlcnpm
> + @apache-royale/royale-js@0.9.3
> updated 1 package in 17.395s
>
>
> What are those invalid entries??
>
> 2. install cli tool
>
> npm install @apache-royale/cli@alpha -g
> no problem here
>
> 3. create royale app
>
> royale new helloWorld
> cd helloWorld
>
> >> no problem
>
> 4. running the app
>
> royale serve:debug
>
> Didn’t work:
>
> helloWorld dany$  > royale serve:debug
> Compiling...
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.common.base.internal.Finalizer
> (file:/usr/local/lib/node_modules/@apache-royale/royale-
> js/royale-asjs/js/lib/guava.jar) to field java.lang.Thread.
> inheritableThreadLocals
> WARNING: Please consider reporting this to the maintainers of
> com.google.common.base.internal.Finalizer
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Error: unable to open 'HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/src/Main.
> mxml'.
>
>
>
> Command failed: mxmlc /Volumes/Macintosh HD/Documents/ARCHEMEDIA/
> ROYALE/helloWorld/src/Main.mxml -debug=true
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.common.base.internal.Finalizer
> (file:/usr/local/lib/node_modules/@apache-royale/royale-
> js/royale-asjs/js/lib/guava.jar) to field java.lang.Thread.
> inheritableThreadLocals
> WARNING: Please consider reporting this to the maintainers of
> com.google.common.base.internal.Finalizer
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Error: unable to open 'HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/src/Main.
> mxml'.
>
>
>
>
> fs.js:646
>   return binding.open(pathModule._makeLong(path), stringToFlags(flags),
> mode);
>  ^
>
> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
> HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/bin/js-debug/index.html'
> at Object.fs.openSync (fs.js:646:18)
> at Object.fs.readFileSync (fs.js:551:33)
> at updateIndex (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:125:24)
> at compileDebug (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:106:9)
> at serveDebug (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:88:5)
> at Object. (/usr/local/lib/node_modules/@
> apache-royale/cli/index.js:59:13)
> at Module._compile (module.js:652:30)
> at Object.Module._extensions..js (module.js:663:10)
> at Module.load (module.js:565:32)
> at tryModuleLoad (module.js:505:12)
> helloWorld dany$  >
>
>
>
>
> Any ideas?
>
> -Dany
>
>
>
>
>


Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

2018-04-29 Thread OmPrakash Muppirala
On Sun, Apr 29, 2018 at 3:50 AM, Dany Dhondt  wrote:

> Hi all,
>
> A few thoughts:
>
>
> In our organization, I built a big backoffice web application in Flex
> about 2 years ago. Now, we are obliged to make it future proof, which
> means, no Flash dependency at all.
> We chose react.js. So the last couple of months, I studied react, npm,
> node, webpack, babel, …
> It’s clear that the most popular technologies for creating web
> applications nowadays are cli driven packages like react, angular, (vue)
> I really think royale should be in this list!
> The whole thing is about getting people up and running in no time. And
> getting started quickly is all about configuration.
> An example: for react, a npm package create-react-app is available which
> is as simple as:
>
> create-react-app my-app
> cd my-app
> yarn start (or npm start)
>
> These commands setup a whole file structure, configures webpack and babel,
> runs a local dev server and start up a boilerplate app. Ready to go!
>
> couldn’t we make a create-royale-app package?
>
>
We do have such a thing.  Please check out the royale cli tool.
Setup instructions here:
https://github.com/apache/royale-asjs/tree/develop/npm/cli
I think it does what you are asking for and more :-)  For example, it
monitors your src folder and recompiles the Royale app and reloads the
browser as well!

One of these days we need to make a blog post about this.  I would really
really like feedback so we can make this tool better.




> This boilerplate could contain a ready-to-go set of components:
> Navigationheader on top, then a left pane and content pane, which are
> responsive and a set of basic components like drop down, button, list, …
>
> All this packed with a clean but robust set of css styling.
>

Right now, the cli installs a very simple hello-world app.  I am planning
on replacing this with a Jewel themed app soon.  Volunteers are more than
welcome to help out here.


>
> I spent the last couple of days searching for a component library for
> react. A few examples: material-ui, React bootstrap, Ant design, Blueprint,
> …
> So far I didn’t find any package which meet my 2 most important criteria:
>
> - Complete set of components
> - Well written component api documentation
>
> I think that a lot of (former) flex developers chose a similar path like
> me but are more than willing to give royale a go.
>
> It is important to know that the majority of these developers (like
> myself) have quite a lot of ‘development skills and experience’ but have
> far less knowledge of what’s going on under the hood.
> We can’t expect them to go through days of configuration frustrations
> before getting started with what is their core business.
>
> So, as much as I agree with the ‘Life after FlashPlayer’ questionnaire, I
> would like to see it posted with a big button at the end saying ‘TRY ROYALE
> NOW'
>
>
> -Dany
>
>
>
>
>
> > Op 29 apr. 2018, om 10:52 heeft Piotr Zarzycki <
> piotrzarzyck...@gmail.com> het volgende geschreven:
> >
> > +1 for Olaf's email and Alex's changes.
> >
> > Piotr
> >
> > On Sun, Apr 29, 2018, 7:15 AM Alex Harui 
> wrote:
> >
> >> Hi Olaf,
> >>
> >> Great first draft!  It is fine as is, and I really like that it is
> short.
> >>
> >> The only thing I'm tempted to try to add is an earlier introduction to
> who
> >> "we" are, that it is the Royale/FlexJS folks asking and not the Flex
> PMC or
> >> some other group.
> >>
> >> So one idea is to just to start with "Hello from the Royale (FlexJS)
> team"
> >> instead of "Hi".
> >> Or enhancing "So, we are really interested..." with "So, we, the Royale
> >> (FlexJS) team, are really interested..."
> >>
> >> My 2 cents,
> >> -Alex
> >>
> >> On 4/28/18, 1:11 PM, "Olaf Krueger"  wrote:
> >>
> >>   Hi,
> >>
> >>> IMO, we don’t need a survey, just the right words in the subject and
> >> body
> >>> of emails that will start > > > discussion and elicit responses...
> >>
> >>   After thinking about it a bit more I came to the conclusion that
> >> there's no
> >>   need to mention Royale as an alternative to Flex in order to start a
> >>   discussion.
> >>   I guess what we all want to know is what all those Flex users and apps
> >> are
> >>   doing out there.
> >>   So I've focused on this and wrote a first draft [1], please take a
> >> look at
> >>   it and make your comments.
> >>   Feel free to revise it.
> >>
> >>   Thanks,
> >>   Olaf
> >>
> >>
> >>   [1]
> >>
> >>   Life after FlashPlayer, are you prepared?
> >>
> >>   Hi,
> >>   even if Flex with AIR is still an awesome and outstanding technology,
> >> Flex
> >>   in the browser ends with the end of FlashPlayer in 2020.
> >>   To be clear: There will be no way to run your Flex apps in current
> >> Browser
> >>   versions around 2020!
> >>
> >>   The Flex mailing lists are followed by a few hundred people and we
> >> assume
> >>   that there are still a lot of Flex browser apps out there.
> >>
> 

Re: 0.9.3 Release

2018-04-27 Thread OmPrakash Muppirala
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 <aha...@adobe.com.invalid>
wrote:

> Yep, that's what we have for you to work with.  I expect there will be
> things missing or needing improvement, but it will be awesome if we can
> make this process work for you.  Then we can hope that anyone can follow
> these instructions and use the scripts to generate a release.
>
> Thanks,
> -Alex
>
> On 4/25/18, 12:19 AM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com> wrote:
>
> Om,
>
> I believe this is some starting point [1]
>
> [1] https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%
> 2FRelease-Manager-Notes=02%7C01%7Caharui%40adobe.com%
> 7C2fd9fa97db624afeb36808d5aa7cd94a%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636602375606683856=M6AXRZTAjFbWerTBnC7Mnk4zS2BkFv
> fmdHLajtuOLAw%3D=0
>
> Piotr
>
> 2018-04-25 9:12 GMT+02:00 OmPrakash Muppirala <bigosma...@gmail.com>:
>
> > 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
> <aha...@adobe.com.invalid>
> > wrote:
> >
> > > 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" <aha...@adobe.com.INVALID>
> wrote:
> > >
> > >
> > >
> > > On 4/24/18, 8:56 AM, "OmPrakash Muppirala" <
> bigosma...@gmail.com>
> > > wrote:
> > >
> > > On Tue, Apr 24, 2018, 12:58 AM Alex Harui
> > <aha...@adobe.com.invalid>
> > > wrote:
> > >
> > > > I think that's been broken forever.  But I don't want to
> take
> > > the time to
> > > > find out.
> > > >
> > > > Try this one:
> > > https://na01.safelinks.protection.outlook.com/?url=
> > > http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%
> > > 3A8080%2Fjob%2Froyale-asjs%2FlastSuccessfulBuild%
> > > 2Fartifact%2Fout%2Fapache-royale-0.9.3-bin-js.tar.gz&
> > > data=02%7C01%7Caharui%40adobe.com%7C5b1248637b664c17102a08d5aa00
> 5e31%
> > > 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636601840922580714=
> > > IqE9VZ5HZXrap4Bi4XV1CUY8PR8YqNaTPzcjHH%2BoSmY%3D=0
> > >
> > >
> > > What is this package supposed to install?
> > >
> > > That link is from the main royale-asjs build that builds both a
> > js-swf
> > > package and a js (only) package.  The link is for the js-only
> package.
> > The
> > > royale-asjs-jsonly build also builds a js-only package but uses a
> > different
> > > set of Ant tasks and I think it has been wrong for a while.
> > >
> > > I will take a look at it now.
> > >
> > > -Alex
> > >
> > >
> > >
> > >
> > >
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki=02%7C01%
> 7Caharui%40adobe.com%7C2fd9fa97db624afeb36808d5aa7cd94a%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636602375606683856=
> PiDsu1q2Fh6Ef9SpxhN%2FVTogKtUMnLVxGBbi3SGjg%2Fo%3D=0
> <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki=02%7C01%
> 7Caharui%40adobe.com%7C2fd9fa97db624afeb36808d5aa7cd94a%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636602375606683856=
> PiDsu1q2Fh6Ef9SpxhN%2FVTogKtUMnLVxGBbi3SGjg%2Fo%3D=0>*
>
>
>


ViewStack equivalent in Royale

2018-04-25 Thread OmPrakash Muppirala
I want to switch views based on selected items in a List.  To build
something like this: https://snag.gy/vQqfRA.jpg

What is the best way to achieve this?

Thanks,
Om


Re: 0.9.3 Release

2018-04-25 Thread OmPrakash Muppirala
On Wed, Apr 25, 2018 at 12:19 AM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
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 Muppirala <bigosma...@gmail.com>:
>
> > 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 <aha...@adobe.com.invalid>
> > wrote:
> >
> > > 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" <aha...@adobe.com.INVALID> wrote:
> > >
> > >
> > >
> > > On 4/24/18, 8:56 AM, "OmPrakash Muppirala" <bigosma...@gmail.com>
> > > wrote:
> > >
> > > On Tue, Apr 24, 2018, 12:58 AM Alex Harui
> > <aha...@adobe.com.invalid>
> > > wrote:
> > >
> > > > I think that's been broken forever.  But I don't want to take
> > > the time to
> > > > find out.
> > > >
> > > > Try this one:
> > > https://na01.safelinks.protection.outlook.com/?url=
> > > http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%
> > > 3A8080%2Fjob%2Froyale-asjs%2FlastSuccessfulBuild%
> > > 2Fartifact%2Fout%2Fapache-royale-0.9.3-bin-js.tar.gz&
> > > data=02%7C01%7Caharui%40adobe.com%7C5b1248637b664c17102a08d5aa005e31%
> > > 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636601840922580714=
> > > IqE9VZ5HZXrap4Bi4XV1CUY8PR8YqNaTPzcjHH%2BoSmY%3D=0
> > >
> > >
> > > What is this package supposed to install?
> > >
> > > That link is from the main royale-asjs build that builds both a
> > js-swf
> > > package and a js (only) package.  The link is for the js-only package.
> > The
> > > royale-asjs-jsonly build also builds a js-only package but uses a
> > different
> > > set of Ant tasks and I think it has been wrong for a while.
> > >
> > > I will take a look at it now.
> > >
> > > -Alex
> > >
> > >
> > >
> > >
> > >
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>


Re: 0.9.3 Release

2018-04-25 Thread OmPrakash Muppirala
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 <aha...@adobe.com.invalid>
wrote:

> 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" <aha...@adobe.com.INVALID> wrote:
>
>
>
> On 4/24/18, 8:56 AM, "OmPrakash Muppirala" <bigosma...@gmail.com>
> wrote:
>
> On Tue, Apr 24, 2018, 12:58 AM Alex Harui <aha...@adobe.com.invalid>
> wrote:
>
> > I think that's been broken forever.  But I don't want to take
> the time to
> > find out.
> >
> > Try this one:
> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapacheroyaleci.westus2.cloudapp.azure.com%
> 3A8080%2Fjob%2Froyale-asjs%2FlastSuccessfulBuild%
> 2Fartifact%2Fout%2Fapache-royale-0.9.3-bin-js.tar.gz&
> data=02%7C01%7Caharui%40adobe.com%7C5b1248637b664c17102a08d5aa005e31%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636601840922580714=
> IqE9VZ5HZXrap4Bi4XV1CUY8PR8YqNaTPzcjHH%2BoSmY%3D=0
>
>
> What is this package supposed to install?
>
> That link is from the main royale-asjs build that builds both a js-swf
> package and a js (only) package.  The link is for the js-only package.  The
> royale-asjs-jsonly build also builds a js-only package but uses a different
> set of Ant tasks and I think it has been wrong for a while.
>
> I will take a look at it now.
>
> -Alex
>
>
>
>
>


  1   2   3   >