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

[Alex Harui]

Hi Om,

If make_branches succeeds, then you shouldn't need to go back and delete 
branches and tags and run make_branches again if the "maven" step fails.

You might need to revert any changes to the release branch that the "maven" 
step did, but then you should be able to delete the local copy of the branches 
and start again with "maven" or "maven_skip_compiler_and_typedefs" if you got 
all the way up to royale-asjs.

What are some of the 200+ files that don't get reverted back to 0.9.4?

You are welcome to try to add the "continue" option.  I would suggest adding a 
dummy parameter.  So if the script currently calls Maven like this:






You can try changing it to something like this:








Then you should be able to set in your local.properties:

continueOption=-rf JewelExample 

You will probably need to use different names for each call to Maven so 
subsequent Maven calls don't pick up the same option.

HTH,
-Alex

On 10/4/18, 11:58 AM, "OmPrakash Muppirala"  wrote:

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.html&data=02%7C01%7Caharui%40adobe.com%7Cdfbb3e1ff11a495826f208d62a2b6bc6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636742763335512825&sdata=%2FoE3nXrnwtRhz3IP%2F8i9DDnmkAcrhdrqo1v1kwVlcYI%3D&reserved=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.c

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

[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.html&data=02%7C01%7Caharui%40adobe.com%7Cf53d1f8543df4d1a82a808d62974c4fa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741978831424956&sdata=rrkMaSLxamQGHfveBJZ6FMMAj9KQY3BxQlOUc4gd2io%3D&reserved=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
> > > 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%2Fmaven2&data=02%7C01%7Caharui%40adobe.com

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

[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&T :-)
> 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%2Fmaven2&data=02%7C01%7Caharui%40adobe.com%7C4113dbce443a4bcbba0008d629d161c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636742376597410393&sdata=%2FA5wGdk8cvC23pci3FUR9nEW%2FBsBGPMyyBa%2BlIxnr3s%3D&reserved=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.
> > >
> > >  [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%2FMojoExecutionException&data=02%7C01%7Caharui%40adobe.com%7C4113dbce443a4bcbba0008d629d161c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636742376597410393&sdata=h7JvjV%2FfSuFmxtd4b9AltWlFmKnpq90N8XRuOGftycE%3D&reserved=0
> > >
> > >  [exec] [INFO] [ERRO

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

[Dave Fisher]

It seems that releases are overly automated.

Seems like once everything is built and tests are passed a set of scripts in a 
runbook can be manually run by the RM.

Regards,
Dave

Sent from my iPhone

> On Oct 4, 2018, at 9:23 AM, Alex Harui  wrote:
> 
> I don't know for sure, but I believe much of it is part of Maven's default 
> release process.  We "must" prove that the example sources pass all standard 
> release requirements (pass the RAT check and compiles without error).  I 
> think by default after those tests, Maven packages up the sources for the 
> example and has to at least deploy that.  There may be a way to block 
> deployment of the compiled output, not sure it will make a huge difference.  
> We have to upload a crapload of stuff anyway.  If your server connection is 
> flaky then it is likely to fail at some point.
> 
> HTH,
> -Alex
> 
> On 10/4/18, 9:16 AM, "OmPrakash Muppirala"  wrote:
> 
>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

[Alex Harui]

Om,

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

-Alex

On 10/4/18, 1:14 AM, "OmPrakash Muppirala"  wrote:

DSL via AT&T :-)
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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fservice%2Flocal%2Fstaging%2Fdeploy%2Fmaven2&data=02%7C01%7Caharui%40adobe.com%7C4113dbce443a4bcbba0008d629d161c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636742376597410393&sdata=%2FA5wGdk8cvC23pci3FUR9nEW%2FBsBGPMyyBa%2BlIxnr3s%3D&reserved=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.
> >
> >  [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%2FMojoExecutionException&data=02%7C01%7Caharui%40adobe.com%7C4113dbce443a4bcbba0008d629d161c5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636742376597410393&sdata=h7JvjV%2FfSuFmxtd4b9AltWlFmKnpq90N8XRuOGftycE%3D&reserved=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-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 
> > > wrot

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

[Alex Harui]

I don't know for sure, but I believe much of it is part of Maven's default 
release process.  We "must" prove that the example sources pass all standard 
release requirements (pass the RAT check and compiles without error).  I think 
by default after those tests, Maven packages up the sources for the example and 
has to at least deploy that.  There may be a way to block deployment of the 
compiled output, not sure it will make a huge difference.  We have to upload a 
crapload of stuff anyway.  If your server connection is flaky then it is likely 
to fail at some point.

HTH,
-Alex

On 10/4/18, 9:16 AM, "OmPrakash Muppirala"  wrote:

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 Roy

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

[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]
> > >>
> 
> > >>
> > >> [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
> > 

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

[Alex Harui]

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 
> 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fservice%2Flocal%2Fstaging%2Fdeploy%2Fmaven2&data=02%7C01%7Caharui%40adobe.com%7Cc54d921a33b241e88efd08d629d92df7%7Cfa7b1b5a7b

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

[Carlos Rovira]

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 
> 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]   m

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

[Alex Harui]

Om, it looks like you are still deleting and recreating the branches.  Does 
this mean you have never completed the make_branches step?  Is make_branches 
failing trying to run a build in the develop branch and uploading 
0.9.5-SNAPSHOT artifacts?  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.

-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.html&data=02%7C01%7Caharui%40adobe.com%7Cf53d1f8543df4d1a82a808d62974c4fa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741978831424956&sdata=rrkMaSLxamQGHfveBJZ6FMMAj9KQY3BxQlOUc4gd2io%3D&reserved=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
> > 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%2Fmaven2&data=02%7C01%7Caharui%40adobe.com%7Cf53d1f8543df4d1a82a808d62974c4fa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741978831424956&sdata=jNrj2JenUBeH4xoeCQkCWv8qFjHqxOu31jl%2Fhuq6jN8%3D&reserved=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%2FMojoExecutionException&data=02%7C01%7Caharui%40adobe.com%7Cf53d1f8543df4d1a82a808d62974c4fa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741978831424956&sdata=

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

[Harbs]

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  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 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

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

[OmPrakash Muppirala]

DSL via AT&T :-)
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 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 Mu

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

[Piotr Zarzycki]

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 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, 201

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

[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:
>>
>> > 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
>> >
>>

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

[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%2Fmaven2&data=02%7C01%7Caharui%40adobe.com%7Cf27e84867a5440c6809008d62962338f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741899088254161&sdata=vzyO7Stsj3pqyE9Sih32heK62GABKGZo0wlgWpxW0bE%3D&reserved=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%2FMojoExecutionException&data=02%7C01%7Caharui%40adobe.com%7Cf27e84867a5440c6809008d62962338f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741899088254161&sdata=RU7b9uJt%2FtsXJiX376HgIqRTvKoiKZcs7Z%2Flr1b4wO8%3D&reserved=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?
> 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
> 

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

[Alex Harui]

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

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?

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 
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%2Fmaven2&data=02%7C01%7Caharui%40adobe.com%7Cf27e84867a5440c6809008d62962338f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741899088254161&sdata=vzyO7Stsj3pqyE9Sih32heK62GABKGZo0wlgWpxW0bE%3D&reserved=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%2FMojoExecutionException&data=02%7C01%7Caharui%40adobe.com%7Cf27e84867a5440c6809008d62962338f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741899088254161&sdata=RU7b9uJt%2FtsXJiX376HgIqRTvKoiKZcs7Z%2Flr1b4wO8%3D&reserved=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?  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

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

[Piotr Zarzycki]

It would be hard to make this happen. I think all artefacts are spread
across target folders and local caches. When artefacts is build I'm not
sure from where Maven is taking it - Cache or Targets folder.

You are almost done with that. If you won't succeed till Monday maybe I
will try to find some time again next week.

Piotr

On Wed, Oct 3, 2018, 8:58 PM 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 
> 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] [INFO] [ERROR] To see the full stack 

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

[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] [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%2FMojoExecutionException&data=02%7C01%7Caharui%40adobe.com%7C128631

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

[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%2FMojoExecutionException&data=02%7C01%7Caharui%40adobe.com%7C1286310eeccc4c57439108d62903e119%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741493968858792&sdata=h0WDkLmfJD1GjTezuQ6GT1bqr%2BlqYai5RAtQIiM9FOM%3D&reserved=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 T

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

[Alex Harui]

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%2FMojoExecutionException&data=02%7C01%7Caharui%40adobe.com%7C1286310eeccc4c57439108d62903e119%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741493968858792&sdata=h0WDkLmfJD1GjTezuQ6GT1bqr%2BlqYai5RAtQIiM9FOM%3D&reserved=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.
> >> > >
> >> > > Thanks and good luck,
> >> > > -Alex
> >> > >
> >> > > On 10/1/18, 10:29 AM, "Piotr Zar

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

[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%2FMojoExecutionException&data=02%7C01%7Caharui%40adobe.com%7C2b91c6a14e704d842f2e08d629025d96%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741487473245214&sdata=l2L26ZMwSr5v20mncG4smoSrRuJeIDxdKMzQMq8dM7A%3D&reserved=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.
> >> > >
> >> > > 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
> >> > > >
> >> >  

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

[Alex Harui]

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%2FMojoExecutionException&data=02%7C01%7Caharui%40adobe.com%7C2b91c6a14e704d842f2e08d629025d96%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636741487473245214&sdata=l2L26ZMwSr5v20mncG4smoSrRuJeIDxdKMzQMq8dM7A%3D&reserved=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 
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:
>> > > >
   

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

[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
>> 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

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

[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 <
> > > > 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

[Alex Harui]

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" 
> 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 :-)
> > > > > > >
> > > > > > > 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
> >  

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

[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 :-)
> > > > > > >
> > > > > > > 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,
> >   

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

[Alex Harui]

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 
> 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
> > > > > >
> > > > > > > > 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 versi

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

[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
> > > > > >
> > > > > > > > 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]
> > > > > > > > > >
>

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

[Alex Harui]

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 
> 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 
> > > > 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:
> > > > > > > > DataGridExample
> > > > > > > > > ... SKIPPED
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Detailed error:
> > > > > > > > >
> > > > > > > > >
> >

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

[Piotr Zarzycki]

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 
> 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 
> > > > 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:
> > > > > > > > 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]
> > > > > > > > >
> > > > > > >
> > > > >
> > >
> 
> > > >

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

[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:
> > > > > > > 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/cont

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

[Carlos Rovira]

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 ()
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  >
> > > 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:
> > > > > > 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] [

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

[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.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:
> > > > > >
> > > > > >  

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

[Piotr Zarzycki]

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.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),
> > > > >
> > > >

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

[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.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
> > > > deb

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

[Carlos Rovira]

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 ()
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.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]
> > >
> 

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

[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
> >
> >  [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 <
> bigosma...@gmail.com>
> > wrote:
> >
> > > Thanks for the quick fix!  Will pull develop and try again.  Will
> report
> > > in a whi

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

[Carlos Rovira]

Hi Om,
just saw that some poms was not changed to 0.9.6-SNAPSHOT.
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
>
>  [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

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

[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 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

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

[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:
> Integrationtests
> >>> > > > .. SKIPPED
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] compc
> >>> > > > .. SKIPPED
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] compiler-asc
> >>> > > > ... SKIPPED
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] compiler-compc
> >>> > > > . SKIPPED
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] compiler-mxmlc
> >>> > > > . SKIPPED
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] compiler-optimizer
> >>> > > > . SKIPPED
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] compiler-swfdump
> >>> > > > ... SKIPPED
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] mxmlc
> >>> > > > .. SKIPPED
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] Apache Royale: Distribution
> >>> > > >  SKIPPED
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] Apache Royale: ManualTests
> >>> > > > . SKIPPED
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] Apache Royale: ManualTests: UnitTests
> >>> > > > .. SKIPPED
> >>> > > >
> >>> > > >  [exec] [INFO] [INFO] Apache Royale: Testsuite 0.9.4
> >>> > > > .

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

[Carlos Rovira]

Side note...I searched for javadoc or maven-javadoc-pluign and didn't find
anything
So it's a completely mystery to me how release process is triggering the
creation of javadocs. :?

El dom., 30 sept. 2018 a las 17:47, Carlos Rovira ()
escribió:

> 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:
 Integrationtests
 > > > .. SKIPPED
 > > >
 > > >  [exec] [INFO] [INFO] compc
 > > > .. SKIPPED
 > > >
 > > >  [exec] [INFO] [INFO] compiler-asc
 > > > ... SKIPPED
 > > >
 > > >  [exec] [INFO] [INFO] compiler-compc
 > > > . SKIPPED
 > > >
 > > >  [exec] [INFO] [INFO] compiler-mxmlc
 > > > . SKIPPED
 > > >
 > > >  [exec] [INFO] [INFO] compiler-optimizer
 > > > . SKIPPED
 > > >
 > > >  [exec] [INFO] [INFO] compiler-swfdump
 > > > ... SKIPPED
 > > >
 > > >  [exec] [INFO] [INFO] mxmlc
 > > > .. SKIPPED
 > > >
 > > >  [exec] [INFO] [INFO] Apache Royale: Distribution
 > > >  SKIPPED
 > > >
 > > >  [exec] [INFO] [INFO] Apache Royale: ManualTests
 > > > . SKIPPED
 > > >
 > > >  [exec] [INFO] [INFO] Apache Royale: ManualTests: UnitTests
 > > > .. SKIPPED
 > > >
 > > >  [exec] [INFO] [INFO] Apache Royale: Testsuite 0.9.4
 > > > . SKIPPED
 > > >
 > > >  [e

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

[Carlos Rovira]

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 ()
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 >> >
>>> 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: Integrationtests
>>> > > > .. SKIPPED
>>> > > >
>>> > > >  [exec] [INFO] [INFO] compc
>>> > > > .. SKIPPED
>>> > > >
>>> > > >  [exec] [INFO] [INFO] compiler-asc
>>> > > > ... SKIPPED
>>> > > >
>>> > > >  [exec] [INFO] [INFO] compiler-compc
>>> > > > . SKIPPED
>>> > > >
>>> > > >  [exec] [INFO] [INFO] compiler-mxmlc
>>> > > > . SKIPPED
>>> > > >
>>> > > >  [exec] [INFO] [INFO] compiler-optimizer
>>> > > > . SKIPPED
>>> > > >
>>> > > >  [exec] [INFO] [INFO] compiler-swfdump
>>> > > > ... SKIPPED
>>> > > >
>>> > > >  [exec] [INFO] [INFO] mxmlc
>>> > > > .. SKIPPED
>>> > > >
>>> > > >  [exec] [INFO] [INFO] Apache Royale: Distribution
>>> > > >  SKIPPED
>>> > > >
>>> > > >  [exec] [INFO] [INFO] Apache Royale: ManualTests
>>> > > > . SKIPPED
>>> > > >
>>> > > >  [exec] [INFO] [INFO] Apache Royale: ManualTests: UnitTests
>>> > > > .. SKIPPED
>>> > > >
>>> > > >  [exec] [INFO] [INFO] Apache Royale: Testsuite 0.9.4
>>> > > > . SKIPPED
>>> > > >
>>> > > >  [exec] [INFO] [INFO]
>>> > > >
>>> >
>>> 
>>> > > >
>>> > > >  [exec] [INFO] [INFO] BUILD FAILURE
>>> > > >
>>> > > >  [exec] [INFO] [INFO]
>>> > > >
>>> >
>>> 
>>> > > >
>>> > > >  [exec] [INFO] [INFO] Total time: 14:11 min
>>> > > >
>>> > > >  [exec] [INFO] [INFO] Finished at: 2018-09-30T00:25:37-07:00

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

[Carlos Rovira]

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 ()
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 
>> 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: Integrationtests
>> > > > .. SKIPPED
>> > > >
>> > > >  [exec] [INFO] [INFO] compc
>> > > > .. SKIPPED
>> > > >
>> > > >  [exec] [INFO] [INFO] compiler-asc
>> > > > ... SKIPPED
>> > > >
>> > > >  [exec] [INFO] [INFO] compiler-compc
>> > > > . SKIPPED
>> > > >
>> > > >  [exec] [INFO] [INFO] compiler-mxmlc
>> > > > . SKIPPED
>> > > >
>> > > >  [exec] [INFO] [INFO] compiler-optimizer
>> > > > . SKIPPED
>> > > >
>> > > >  [exec] [INFO] [INFO] compiler-swfdump
>> > > > ... SKIPPED
>> > > >
>> > > >  [exec] [INFO] [INFO] mxmlc
>> > > > .. SKIPPED
>> > > >
>> > > >  [exec] [INFO] [INFO] Apache Royale: Distribution
>> > > >  SKIPPED
>> > > >
>> > > >  [exec] [INFO] [INFO] Apache Royale: ManualTests
>> > > > . SKIPPED
>> > > >
>> > > >  [exec] [INFO] [INFO] Apache Royale: ManualTests: UnitTests
>> > > > .. SKIPPED
>> > > >
>> > > >  [exec] [INFO] [INFO] Apache Royale: Testsuite 0.9.4
>> > > > . SKIPPED
>> > > >
>> > > >  [exec] [INFO] [INFO]
>> > > >
>> > 
>> > > >
>> > > >  [exec] [INFO] [INFO] BUILD FAILURE
>> > > >
>> > > >  [exec] [INFO] [INFO]
>> > > >
>> > 
>> > > >
>> > > >  [exec] [INFO] [INFO] Total time: 14:11 min
>> > > >
>> > > >  [exec] [INFO] [INFO] Finished at: 2018-09-30T00:25:37-07:00
>> > > >
>> > > >  [exec] [INFO] [INFO]
>> > > >
>> > 
>> > > >
>> > > >  [exec] [INFO] [ERROR] Failed to execute goal
>> > > > org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:jar
>> > > (attach-javadocs)
>> > > > on project SampleAmfWebApp: MavenReport

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

[Carlos Rovira]

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 
> 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: Integrationtests
> > > > .. SKIPPED
> > > >
> > > >  [exec] [INFO] [INFO] compc
> > > > .. SKIPPED
> > > >
> > > >  [exec] [INFO] [INFO] compiler-asc
> > > > ... SKIPPED
> > > >
> > > >  [exec] [INFO] [INFO] compiler-compc
> > > > . SKIPPED
> > > >
> > > >  [exec] [INFO] [INFO] compiler-mxmlc
> > > > . SKIPPED
> > > >
> > > >  [exec] [INFO] [INFO] compiler-optimizer
> > > > . SKIPPED
> > > >
> > > >  [exec] [INFO] [INFO] compiler-swfdump
> > > > ... SKIPPED
> > > >
> > > >  [exec] [INFO] [INFO] mxmlc
> > > > .. SKIPPED
> > > >
> > > >  [exec] [INFO] [INFO] Apache Royale: Distribution
> > > >  SKIPPED
> > > >
> > > >  [exec] [INFO] [INFO] Apache Royale: ManualTests
> > > > . SKIPPED
> > > >
> > > >  [exec] [INFO] [INFO] Apache Royale: ManualTests: UnitTests
> > > > .. SKIPPED
> > > >
> > > >  [exec] [INFO] [INFO] Apache Royale: Testsuite 0.9.4
> > > > . SKIPPED
> > > >
> > > >  [exec] [INFO] [INFO]
> > > >
> > 
> > > >
> > > >  [exec] [INFO] [INFO] BUILD FAILURE
> > > >
> > > >  [exec] [INFO] [INFO]
> > > >
> > 
> > > >
> > > >  [exec] [INFO] [INFO] Total time: 14:11 min
> > > >
> > > >  [exec] [INFO] [INFO] Finished at: 2018-09-30T00:25:37-07:00
> > > >
> > > >  [exec] [INFO] [INFO]
> > > >
> > 
> > > >
> > > >  [exec] [INFO] [ERROR] Failed to execute goal
> > > > org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:jar
> > > (attach-javadocs)
> > > > on project SampleAmfWebApp: MavenReportException: Error while
> > generating
> > > > Javadoc:
> > > >
> > > >  [exec] [INFO] [ERROR] Exit code: 1 -
> > > >
> > > >
> > >
> >
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:31:
> > > > error: @param name not found
> > > >
> > > >  [exec] [INFO] [ERROR]  * @param code
> > > >
> > > >  [exec] [INFO] [ERROR]   ^
> > > >
> > > >  [exec] [INFO] [ERROR]
> > > >
> > > >
> > >
> >
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:31:
> > > > warning: no description for @param
> > > >
> > > >  [exec] [INFO] [ERROR]  * @param code
> > > >
> > > >  [exec] [INFO] [ERROR]^
> > > >
> > > >  [exec] [INFO]

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

[Piotr Zarzycki]

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 
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 
> > 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: Integrationtests
> > > .. SKIPPED
> > >
> > >  [exec] [INFO] [INFO] compc
> > > .. SKIPPED
> > >
> > >  [exec] [INFO] [INFO] compiler-asc
> > > ... SKIPPED
> > >
> > >  [exec] [INFO] [INFO] compiler-compc
> > > . SKIPPED
> > >
> > >  [exec] [INFO] [INFO] compiler-mxmlc
> > > . SKIPPED
> > >
> > >  [exec] [INFO] [INFO] compiler-optimizer
> > > . SKIPPED
> > >
> > >  [exec] [INFO] [INFO] compiler-swfdump
> > > ... SKIPPED
> > >
> > >  [exec] [INFO] [INFO] mxmlc
> > > .. SKIPPED
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: Distribution
> > >  SKIPPED
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: ManualTests
> > > . SKIPPED
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: ManualTests: UnitTests
> > > .. SKIPPED
> > >
> > >  [exec] [INFO] [INFO] Apache Royale: Testsuite 0.9.4
> > > . SKIPPED
> > >
> > >  [exec] [INFO] [INFO]
> > >
> 
> > >
> > >  [exec] [INFO] [INFO] BUILD FAILURE
> > >
> > >  [exec] [INFO] [INFO]
> > >
> 
> > >
> > >  [exec] [INFO] [INFO] Total time: 14:11 min
> > >
> > >  [exec] [INFO] [INFO] Finished at: 2018-09-30T00:25:37-07:00
> > >
> > >  [exec] [INFO] [INFO]
> > >
> 
> > >
> > >  [exec] [INFO] [ERROR] Failed to execute goal
> > > org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:jar
> > (attach-javadocs)
> > > on project SampleAmfWebApp: MavenReportException: Error while
> generating
> > > Javadoc:
> > >
> > >  [exec] [INFO] [ERROR] Exit code: 1 -
> > >
> > >
> >
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:31:
> > > error: @param name not found
> > >
> > >  [exec] [INFO] [ERROR]  * @param code
> > >
> > >  [exec] [INFO] [ERROR]   ^
> > >
> > >  [exec] [INFO] [ERROR]
> > >
> > >
> >
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:31:
> > > warning: no description for @param
> > >
> > >  [exec] [INFO] [ERROR]  * @param code
> > >
> > >  [exec] [INFO] [ERROR]^
> > >
> > >  [exec] [INFO] [ERROR]
> > >
> > >
> >
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:33:
> > > warning: no @param for compressionError
> > >
> > >  [exec] [INFO] [ERROR] public
> > > AMFCompressionException(AMFCompressionError compressionError) {
> > >
> > >  [exec] [INFO] [ERROR]^
> > >
> > >  [exec] [INFO] [ERROR]
> > >
> > >
> >
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFC

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

[Carlos Rovira]

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 
> 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: Integrationtests
> > .. SKIPPED
> >
> >  [exec] [INFO] [INFO] compc
> > .. SKIPPED
> >
> >  [exec] [INFO] [INFO] compiler-asc
> > ... SKIPPED
> >
> >  [exec] [INFO] [INFO] compiler-compc
> > . SKIPPED
> >
> >  [exec] [INFO] [INFO] compiler-mxmlc
> > . SKIPPED
> >
> >  [exec] [INFO] [INFO] compiler-optimizer
> > . SKIPPED
> >
> >  [exec] [INFO] [INFO] compiler-swfdump
> > ... SKIPPED
> >
> >  [exec] [INFO] [INFO] mxmlc
> > .. SKIPPED
> >
> >  [exec] [INFO] [INFO] Apache Royale: Distribution
> >  SKIPPED
> >
> >  [exec] [INFO] [INFO] Apache Royale: ManualTests
> > . SKIPPED
> >
> >  [exec] [INFO] [INFO] Apache Royale: ManualTests: UnitTests
> > .. SKIPPED
> >
> >  [exec] [INFO] [INFO] Apache Royale: Testsuite 0.9.4
> > . SKIPPED
> >
> >  [exec] [INFO] [INFO]
> > 
> >
> >  [exec] [INFO] [INFO] BUILD FAILURE
> >
> >  [exec] [INFO] [INFO]
> > 
> >
> >  [exec] [INFO] [INFO] Total time: 14:11 min
> >
> >  [exec] [INFO] [INFO] Finished at: 2018-09-30T00:25:37-07:00
> >
> >  [exec] [INFO] [INFO]
> > 
> >
> >  [exec] [INFO] [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:jar
> (attach-javadocs)
> > on project SampleAmfWebApp: MavenReportException: Error while generating
> > Javadoc:
> >
> >  [exec] [INFO] [ERROR] Exit code: 1 -
> >
> >
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:31:
> > error: @param name not found
> >
> >  [exec] [INFO] [ERROR]  * @param code
> >
> >  [exec] [INFO] [ERROR]   ^
> >
> >  [exec] [INFO] [ERROR]
> >
> >
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:31:
> > warning: no description for @param
> >
> >  [exec] [INFO] [ERROR]  * @param code
> >
> >  [exec] [INFO] [ERROR]^
> >
> >  [exec] [INFO] [ERROR]
> >
> >
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:33:
> > warning: no @param for compressionError
> >
> >  [exec] [INFO] [ERROR] public
> > AMFCompressionException(AMFCompressionError compressionError) {
> >
> >  [exec] [INFO] [ERROR]^
> >
> >  [exec] [INFO] [ERROR]
> >
> >
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:40:
> > error: @param name not found
> >
> >  [exec] [INFO] [ERROR]  * @param code
> >
> >  [exec] [INFO] [ERROR]   ^
> >
> >  [exec] [INFO] [ERROR]
> >
> >
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:40:
> > warning: no description for @param
> >
> >  [exec] [INFO] [ERROR]  * @param code
> >
> >  [exec] [INFO] [ERROR]^
> >
> >  [exec] [INFO] [ERROR]
> >
> >
> /Us

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

[Piotr Zarzycki]

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 
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: Integrationtests
> .. SKIPPED
>
>  [exec] [INFO] [INFO] compc
> .. SKIPPED
>
>  [exec] [INFO] [INFO] compiler-asc
> ... SKIPPED
>
>  [exec] [INFO] [INFO] compiler-compc
> . SKIPPED
>
>  [exec] [INFO] [INFO] compiler-mxmlc
> . SKIPPED
>
>  [exec] [INFO] [INFO] compiler-optimizer
> . SKIPPED
>
>  [exec] [INFO] [INFO] compiler-swfdump
> ... SKIPPED
>
>  [exec] [INFO] [INFO] mxmlc
> .. SKIPPED
>
>  [exec] [INFO] [INFO] Apache Royale: Distribution
>  SKIPPED
>
>  [exec] [INFO] [INFO] Apache Royale: ManualTests
> . SKIPPED
>
>  [exec] [INFO] [INFO] Apache Royale: ManualTests: UnitTests
> .. SKIPPED
>
>  [exec] [INFO] [INFO] Apache Royale: Testsuite 0.9.4
> . SKIPPED
>
>  [exec] [INFO] [INFO]
> 
>
>  [exec] [INFO] [INFO] BUILD FAILURE
>
>  [exec] [INFO] [INFO]
> 
>
>  [exec] [INFO] [INFO] Total time: 14:11 min
>
>  [exec] [INFO] [INFO] Finished at: 2018-09-30T00:25:37-07:00
>
>  [exec] [INFO] [INFO]
> 
>
>  [exec] [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:jar (attach-javadocs)
> on project SampleAmfWebApp: MavenReportException: Error while generating
> Javadoc:
>
>  [exec] [INFO] [ERROR] Exit code: 1 -
>
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:31:
> error: @param name not found
>
>  [exec] [INFO] [ERROR]  * @param code
>
>  [exec] [INFO] [ERROR]   ^
>
>  [exec] [INFO] [ERROR]
>
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:31:
> warning: no description for @param
>
>  [exec] [INFO] [ERROR]  * @param code
>
>  [exec] [INFO] [ERROR]^
>
>  [exec] [INFO] [ERROR]
>
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:33:
> warning: no @param for compressionError
>
>  [exec] [INFO] [ERROR] public
> AMFCompressionException(AMFCompressionError compressionError) {
>
>  [exec] [INFO] [ERROR]^
>
>  [exec] [INFO] [ERROR]
>
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:40:
> error: @param name not found
>
>  [exec] [INFO] [ERROR]  * @param code
>
>  [exec] [INFO] [ERROR]   ^
>
>  [exec] [INFO] [ERROR]
>
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:40:
> warning: no description for @param
>
>  [exec] [INFO] [ERROR]  * @param code
>
>  [exec] [INFO] [ERROR]^
>
>  [exec] [INFO] [ERROR]
>
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:41:
> warning: no description for @param
>
>  [exec] [INFO] [ERROR]  * @param cause
>
>  [exec] [INFO] [ERROR]^
>
>  [exec] [INFO] [ERROR]
>
> /Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:43:
> warning: no @param for compressionError
>
>  [exec] [INFO] [ERROR] public
> AMFCompres

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

[OmPrakash Muppirala]

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: Integrationtests
.. SKIPPED

 [exec] [INFO] [INFO] compc
.. SKIPPED

 [exec] [INFO] [INFO] compiler-asc
... SKIPPED

 [exec] [INFO] [INFO] compiler-compc
. SKIPPED

 [exec] [INFO] [INFO] compiler-mxmlc
. SKIPPED

 [exec] [INFO] [INFO] compiler-optimizer
. SKIPPED

 [exec] [INFO] [INFO] compiler-swfdump
... SKIPPED

 [exec] [INFO] [INFO] mxmlc
.. SKIPPED

 [exec] [INFO] [INFO] Apache Royale: Distribution
 SKIPPED

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

 [exec] [INFO] [INFO] Apache Royale: ManualTests: UnitTests
.. SKIPPED

 [exec] [INFO] [INFO] Apache Royale: Testsuite 0.9.4
. SKIPPED

 [exec] [INFO] [INFO]


 [exec] [INFO] [INFO] BUILD FAILURE

 [exec] [INFO] [INFO]


 [exec] [INFO] [INFO] Total time: 14:11 min

 [exec] [INFO] [INFO] Finished at: 2018-09-30T00:25:37-07:00

 [exec] [INFO] [INFO]


 [exec] [INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:jar (attach-javadocs)
on project SampleAmfWebApp: MavenReportException: Error while generating
Javadoc:

 [exec] [INFO] [ERROR] Exit code: 1 -
/Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:31:
error: @param name not found

 [exec] [INFO] [ERROR]  * @param code

 [exec] [INFO] [ERROR]   ^

 [exec] [INFO] [ERROR]
/Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:31:
warning: no description for @param

 [exec] [INFO] [ERROR]  * @param code

 [exec] [INFO] [ERROR]^

 [exec] [INFO] [ERROR]
/Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:33:
warning: no @param for compressionError

 [exec] [INFO] [ERROR] public
AMFCompressionException(AMFCompressionError compressionError) {

 [exec] [INFO] [ERROR]^

 [exec] [INFO] [ERROR]
/Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:40:
error: @param name not found

 [exec] [INFO] [ERROR]  * @param code

 [exec] [INFO] [ERROR]   ^

 [exec] [INFO] [ERROR]
/Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:40:
warning: no description for @param

 [exec] [INFO] [ERROR]  * @param code

 [exec] [INFO] [ERROR]^

 [exec] [INFO] [ERROR]
/Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:41:
warning: no description for @param

 [exec] [INFO] [ERROR]  * @param cause

 [exec] [INFO] [ERROR]^

 [exec] [INFO] [ERROR]
/Users/om/p/os/royale/release/royale-asjs/examples/amf/SampleAmfWebApp/src/main/java/org/apache/royale/net/remoting/amf/adapter/AMFCompressionException.java:43:
warning: no @param for compressionError

 [exec] [INFO] [ERROR] public
AMFCompressionException(AMFCompressionError compressionError, Throwable
cause) {

 [exec] [INFO] [ERROR]^

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] Command line was:
/Library/Java/JavaVirtualMachines/jdk1.8.0_181.jdk/Contents/Home/jre/../bin/javadoc
@options @packages

 [exec] [INFO] [ERROR]

 [exec] [INFO] [ERROR] Refer to the generated Javadoc files in
'/Users/om/p/os/royale/

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

[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%2Freleases&data=02%7C01%7Caharui%40adobe.com%7C2f3f5b1ac35b4355b12008d621a6b2e7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636733397180561746&sdata=MWZN3TH8kh%2BKbX5CidHQhPOU6mKPIp2e7UP%2FwPXa2Mk%3D&reserved=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%2Freleases&data=02%7C01%7Caharui%40adobe.com%7C2f3f5b1ac35b4355b12008d621a6b2e7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636733397180561746&sdata=MWZN3TH8kh%2BKbX5CidHQhPOU6mKPIp2e7UP%2FwPXa2Mk%3D&reserved=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! :)
> > >> > >
> > >> > > 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" <
> > bigosma...@gmail.com>
> > >> > > 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
> > >> > > > 

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

[Piotr Zarzycki]

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%2Freleases&data=02%7C01%7Caharui%40adobe.com%7C2f3f5b1ac35b4355b12008d621a6b2e7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636733397180561746&sdata=MWZN3TH8kh%2BKbX5CidHQhPOU6mKPIp2e7UP%2FwPXa2Mk%3D&reserved=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%2Freleases&data=02%7C01%7Caharui%40adobe.com%7C2f3f5b1ac35b4355b12008d621a6b2e7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636733397180561746&sdata=MWZN3TH8kh%2BKbX5CidHQhPOU6mKPIp2e7UP%2FwPXa2Mk%3D&reserved=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! :)
> >> > >
> >> > > 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" <
> bigosma...@gmail.com>
> >> > > 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 r

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

[Alex Harui]

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 
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%2Freleases&data=02%7C01%7Caharui%40adobe.com%7C2f3f5b1ac35b4355b12008d621a6b2e7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636733397180561746&sdata=MWZN3TH8kh%2BKbX5CidHQhPOU6mKPIp2e7UP%2FwPXa2Mk%3D&reserved=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%2Freleases&data=02%7C01%7Caharui%40adobe.com%7C2f3f5b1ac35b4355b12008d621a6b2e7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636733397180561746&sdata=MWZN3TH8kh%2BKbX5CidHQhPOU6mKPIp2e7UP%2FwPXa2Mk%3D&reserved=0
>
> 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, Ale

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

[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>
>> > > > > > 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 

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

[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 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
> > > >   

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

[Carlos Rovira]

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 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 hop

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

[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
> > > > > 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
> > > > >
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cdb30ed90e46d4f4a1e9508d61fdb15d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636731423152768393&sdata=veGxp96IIELNTLlVFcclWR2UjezGP6nZIs%2FRTWkdyzg%3D&reserved=0
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cdb30ed90e46d4f4a1e9508d61

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

[Carlos Rovira]

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
> > > > 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
> > > >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cdb30ed90e46d4f4a1e9508d61fdb15d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636731423152768393&sdata=veGxp96IIELNTLlVFcclWR2UjezGP6nZIs%2FRTWkdyzg%3D&reserved=0
> > > >
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cdb30ed90e46d4f4a1e9508d61fdb15d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636731423152778398&sdata=%2BSZmNefKrj5UVuIYD3UISFlFLrkVZWy42DT0Zq6zkbw%3D&reserved=0
> > <
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cdb30ed90e46d4f4a1e9508d61fdb15d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636731423152778398&sdata=%2BSZmNefKrj5UVuIYD3UISFlFLrkVZWy42DT0Zq6zkbw%3D&reserved=0
> >*
> >
>
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

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

[Alex Harui]

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 
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
> > > 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cdb30ed90e46d4f4a1e9508d61fdb15d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636731423152768393&sdata=veGxp96IIELNTLlVFcclWR2UjezGP6nZIs%2FRTWkdyzg%3D&reserved=0
> > >
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: 
*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Cdb30ed90e46d4f4a1e9508d61fdb15d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636731423152778398&sdata=%2BSZmNefKrj5UVuIYD3UISFlFLrkVZWy42DT0Zq6zkbw%3D&reserved=0
> 
*
>

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

[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
> *
>

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

[Piotr Zarzycki]

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
*

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

[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

[Carlos Rovira]

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

[Piotr Zarzycki]

Hey Om,

If you have capacity please finish that release. Users of VSCode and
Moonshine will be happy!

Thanks,
Piotr

On Thu, Sep 20, 2018, 5:08 PM OmPrakash Muppirala 
wrote:

> 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-422870607&data=02%7C01%7Caharui%40adobe.com%7C7b170880a70a4b8d340c08d61ec539b7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636730229757292613&sdata=54aFEiUJ%2FRTCiBooZaJADt9CvYamAcvzNyWY1wP0%2Fjg%3D&reserved=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 peop

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

[Alex Harui]

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.

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?

Thanks,
-Alex

On 9/20/18, 8:29 AM, "Carlos Rovira"  wrote:

Hi Om,
that's great! :)
Hope you could take on the release and get it out of the door :)

Thanks!

Carlos



El jue., 20 sept. 2018 a las 17:08, OmPrakash Muppirala (<
bigosma...@gmail.com>) escribió:

> 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Flist.html%3Fusers%40royale.apache.org&data=02%7C01%7Caharui%40adobe.com%7C7d734bb076fc4aa694eb08d61f0de787%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636730541915655402&sdata=H72NLqj1sCExgvsb9ZSO7CYeh3uGh76saw1rkACEGtU%3D&reserved=0
> > >
> > > 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-422870607&data=02%7C01%

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

[Carlos Rovira]

Hi Om,
that's great! :)
Hope you could take on the release and get it out of the door :)

Thanks!

Carlos



El jue., 20 sept. 2018 a las 17:08, OmPrakash Muppirala (<
bigosma...@gmail.com>) escribió:

> 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-422870607&data=02%7C01%7Caharui%40adobe.com%7C7b170880a70a4b8d340c08d61ec539b7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636730229757292613&sdata=54aFEiUJ%2FRTCiBooZaJADt9CvYamAcvzNyWY1wP0%2Fjg%3D&reserved=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

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

[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-422870607&data=02%7C01%7Caharui%40adobe.com%7C7b170880a70a4b8d340c08d61ec539b7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636730229757292613&sdata=54aFEiUJ%2FRTCiBooZaJADt9CvYamAcvzNyWY1wP0%2Fjg%3D&reserved=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 ge

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

[Carlos Rovira]

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-422870607&data=02%7C01%7Caharui%40adobe.com%7C7b170880a70a4b8d340c08d61ec539b7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636730229757292613&sdata=54aFEiUJ%2FRTCiBooZaJADt9CvYamAcvzNyWY1wP0%2Fjg%3D&reserved=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 the most stable API I can so things are as most
> organized
> > and
> > well named as possible).
> >
> > If someone could continue the effort will be very good, but if
> none of
> > us
> > can do, it I think nothing can be done but continue working hard
> to get
> > things done.
> >
> > just my 2
> >
> > Carlos
> >
> >
> >
> >
> >
> >
> >
> > El mié., 19 sept. 2018 a las 22:57, Harbs (<
> harbs.li...@gmail.com>)
> > escribió:
> >
> > > Jewel is another reason.
> > >
> > > Carlos wrote a lot of blog posts which can’t be run until we
> release.
> > >
> > > (Plus lots of little things that were fixed…)
> > >
> > > > On Sep 19, 2018, at 11:26 PM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > > wrote:
> > > >
> > > > I personally express important reason. Releasing can help
> community
> > > around
> > > > VSCod

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

[Alex Harui]

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-422870607&data=02%7C01%7Caharui%40adobe.com%7C7b170880a70a4b8d340c08d61ec539b7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636730229757292613&sdata=54aFEiUJ%2FRTCiBooZaJADt9CvYamAcvzNyWY1wP0%2Fjg%3D&reserved=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 the most stable API I can so things are as most organized
> and
> well named as possible).
>
> If someone could continue the effort will be very good, but if none of
> us
> can do, it I think nothing can be done but continue working hard to 
get
> things done.
>
> just my 2
>
> Carlos
>
>
>
>
>
>
>
> El mié., 19 sept. 2018 a las 22:57, Harbs ()
> escribió:
>
> > Jewel is another reason.
> >
> > Carlos wrote a lot of blog posts which can’t be run until we 
release.
> >
> > (Plus lots of little things that were fixed…)
> >
> > > On Sep 19, 2018, at 11:26 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > wrote:
> > >
> > > I personally express important reason. Releasing can help 
community
> > around
> > > VSCode and Moonshine.
> > >
> > > Piotr
> > >
> > > On Wed, Sep 19, 2018, 9:41 PM Alex Harui  >
> > wrote:
> > >
> > >> What do you see as the important reasons?  I know the Apache
> mantra is
> > to
> > >> release early and often, but if it were up to me, we would 
release
> > after we
> > >> hit some interesting milestone, like getting Al

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

[Carlos Rovira]

Hi Alex,

what Zend-AMF issue you refer? can you post the link to that issue?
thanks

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". My vision is that anyone that try and find problems will need to
join us to help in some way or another, or be passive and wait for another
release. I, that plan to start a project soon, think the second option is
not possible. I need to solve the things I can my self, so I'll be using my
own custom local snapshot SDKs in the meanwhile. I think this is valid for
others. the SDK we release now should only be needed for people to try
quickly and then want to know more of Royale, in fact I think old releases,
compared with what we have right now are not very usable right now due to
all the things solved this months, same will happen with a release now.

If I have to put things to not release I can put as well others:

1) Jewel Table component needs some rework
2) Sometimes in tablets and phones responsivity is not working ok, I need
to see what's happen.
3) Jewel DropDownList needs more work
4) ...

And most of this can be applied to Basic as well since Jewel is somewhat a
continuation of the Basic work...

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.

just my 2

Carlos








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://github.com/apache/royale-asjs/issues/297#issuecomment-422870607
>
> 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 the most stable API I can so things are as most organized
> and
> well named as possible).
>
> If someone could continue the effort will be very good, but if none of
> us
> can do, it I think nothing can be done but continue working hard to get
> things done.
>
> just my 2
>
> Carlos
>
>
>
>
>
>
>
> El mié., 19 sept. 2018 a las 22:57, Harbs ()
> escribió:
>
> > Jewel is another reason.
> >
> > Carlos wrote a lot of blog posts which can’t be run until we release.
> >
> > (Plus lots of little things that were fixed…)
> >
> > > On Sep 19, 2018, at 11:26 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > wrote:
> > >
> > > I personally express important reason. Releasing can help community
> > around
> > > VSCode and Moonshine.
> > >
> > > Piotr
> > >
> > > On Wed, Sep 19, 2018, 9:41 PM Alex Harui  >
> > wrote:
> > >
> > >> What do you see as the important reasons?  I know the Apache
> mantra is
> > to
> > >> release early and often, but if it were up to me, we would release
> > after we
> > >> hit some interesting milestone, like getting Alina's app to
> compile
> > >> completely, or someone else says they are ready to go to
> production and
> > >> need a released version of Royale.  There are some bugs blocking
> users
> > that
> > >> I would rather get done before releasing.
> > >>
> > >> My 2 cents,
> > >> -Alex
> > >>
> > >> On 9/19/18, 10:34 AM, "Harbs"  wrote:
> > >>
> > >>I’m happy 

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

[Alex Harui]

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://github.com/apache/royale-asjs/issues/297#issuecomment-422870607

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 the most stable API I can so things are as most organized and
well named as possible).

If someone could continue the effort will be very good, but if none of us
can do, it I think nothing can be done but continue working hard to get
things done.

just my 2

Carlos







El mié., 19 sept. 2018 a las 22:57, Harbs ()
escribió:

> Jewel is another reason.
>
> Carlos wrote a lot of blog posts which can’t be run until we release.
>
> (Plus lots of little things that were fixed…)
>
> > On Sep 19, 2018, at 11:26 PM, Piotr Zarzycki 
> wrote:
> >
> > I personally express important reason. Releasing can help community
> around
> > VSCode and Moonshine.
> >
> > Piotr
> >
> > On Wed, Sep 19, 2018, 9:41 PM Alex Harui 
> wrote:
> >
> >> What do you see as the important reasons?  I know the Apache mantra is
> to
> >> release early and often, but if it were up to me, we would release
> after we
> >> hit some interesting milestone, like getting Alina's app to compile
> >> completely, or someone else says they are ready to go to production and
> >> need a released version of Royale.  There are some bugs blocking users
> that
> >> I would rather get done before releasing.
> >>
> >> My 2 cents,
> >> -Alex
> >>
> >> On 9/19/18, 10:34 AM, "Harbs"  wrote:
> >>
> >>I’m happy to try and be a release manager, but I don’t have time for
> >> at least a month. I think it’s pretty important to get this release out
> >> sooner rather than later.
> >>
> >>If you can help Piotr finish this release, I’ll try to do the 0.9.5
> >> release.
> >>
> >>Thanks,
> >>Harbs
> >>
> >>> On Sep 19, 2018, at 6:54 PM, Alex Harui 
> >> wrote:
> >>>
> >>> Hi Piotr,
> >>>
> >>> In my previous email, I was trying to say that you don't need to run
> >> update.versions because I already did.
> >>> In that and even earlier emails, we discussed running make_branches
> >> twice.  IMO, you are getting the right results by running 
make_branches.
> >> Given the current state of the repo, running make_branches once will 
set
> >> the develop branch to 0.9.4-SNAPSHOT and the release branch to 0.9.3.
> >> That's because that's how Maven works. The current poms in develop are
> set
> >> to 0.9.3-SNAPSHOT.  Maven removes the "SNAPSHOT" in the release branch
> and
> >> bumps the version in the develop branch.
> >>>
> >>> I think you can just run make_branches again and it should create a
> >> release branch with 0.9.4 and bump the develop branch to 
0.9.5-SNAPSHOT.
> >> That would be what we want.
> >>> If you want me to help more, I will take the time to do so.  I can:
> >>> -Get the repos to the point where the current scripts should "just
> >> work".
> >>> -Make sure make_branches works and is complete.
> >>> -Do all of the other steps.
> >>>
> >>> I still think it is important that someone else besides me can run
> >> the scripts and generate a release.  So I would prefer to just get the
> >> repos ready so that you can try running the scripts.  If there are
> >> important things 

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

[Carlos Rovira]

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 the most stable API I can so things are as most organized and
well named as possible).

If someone could continue the effort will be very good, but if none of us
can do, it I think nothing can be done but continue working hard to get
things done.

just my 2

Carlos







El mié., 19 sept. 2018 a las 22:57, Harbs ()
escribió:

> Jewel is another reason.
>
> Carlos wrote a lot of blog posts which can’t be run until we release.
>
> (Plus lots of little things that were fixed…)
>
> > On Sep 19, 2018, at 11:26 PM, Piotr Zarzycki 
> wrote:
> >
> > I personally express important reason. Releasing can help community
> around
> > VSCode and Moonshine.
> >
> > Piotr
> >
> > On Wed, Sep 19, 2018, 9:41 PM Alex Harui 
> wrote:
> >
> >> What do you see as the important reasons?  I know the Apache mantra is
> to
> >> release early and often, but if it were up to me, we would release
> after we
> >> hit some interesting milestone, like getting Alina's app to compile
> >> completely, or someone else says they are ready to go to production and
> >> need a released version of Royale.  There are some bugs blocking users
> that
> >> I would rather get done before releasing.
> >>
> >> My 2 cents,
> >> -Alex
> >>
> >> On 9/19/18, 10:34 AM, "Harbs"  wrote:
> >>
> >>I’m happy to try and be a release manager, but I don’t have time for
> >> at least a month. I think it’s pretty important to get this release out
> >> sooner rather than later.
> >>
> >>If you can help Piotr finish this release, I’ll try to do the 0.9.5
> >> release.
> >>
> >>Thanks,
> >>Harbs
> >>
> >>> On Sep 19, 2018, at 6:54 PM, Alex Harui 
> >> wrote:
> >>>
> >>> Hi Piotr,
> >>>
> >>> In my previous email, I was trying to say that you don't need to run
> >> update.versions because I already did.
> >>> In that and even earlier emails, we discussed running make_branches
> >> twice.  IMO, you are getting the right results by running make_branches.
> >> Given the current state of the repo, running make_branches once will set
> >> the develop branch to 0.9.4-SNAPSHOT and the release branch to 0.9.3.
> >> That's because that's how Maven works. The current poms in develop are
> set
> >> to 0.9.3-SNAPSHOT.  Maven removes the "SNAPSHOT" in the release branch
> and
> >> bumps the version in the develop branch.
> >>>
> >>> I think you can just run make_branches again and it should create a
> >> release branch with 0.9.4 and bump the develop branch to 0.9.5-SNAPSHOT.
> >> That would be what we want.
> >>> If you want me to help more, I will take the time to do so.  I can:
> >>> -Get the repos to the point where the current scripts should "just
> >> work".
> >>> -Make sure make_branches works and is complete.
> >>> -Do all of the other steps.
> >>>
> >>> I still think it is important that someone else besides me can run
> >> the scripts and generate a release.  So I would prefer to just get the
> >> repos ready so that you can try running the scripts.  If there are
> >> important things you've learned that other RMs will need to know, please
> >> try to capture them in the wiki document.
> >>>
> >>> @Carlos, I have spent a lot of time trying to automate releasing.
> >> As Piotr said, skipping a version wasn't planned for and I hope it won't
> >> ever happen again.  Unless you've actually looked at the scripts and
> read
> >> the wiki document and tried it, saying you think there are too many
> manual
> >> steps is not only wrong, but discouraging to those who have put effort
> into
> >> it.  If you really think it needs to be better automated, then do it
> >> yourself.  Don’t expect others to do things for you when you make
> negative
> >> comments about their work.  I have other things I want to work on other
> >> than release automation.  Release automation is only going to be "good
> >> enough" and always in need of improvement.  We've only done two releases
> >> and we are still debugging the scripts.   Join the effort instead of
> >> complaining about it.
> >>>
> >>> Thanks,
> >>> -Alex
> >>>
> >>>
> >>> On 9/19/18, 7:39 AM, "Carlos Rovira"  >> > wrote:
> >>>
> >>>   Hi Piotr,
> >>>
> >>>   sorry to hear that, I think we're out of resources. I'm
> >> concentrating in
> >>>   make Jewel as stable as possible since in few days we can start a
> >> new
> >

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

[Harbs]

Jewel is another reason.

Carlos wrote a lot of blog posts which can’t be run until we release.

(Plus lots of little things that were fixed…)

> On Sep 19, 2018, at 11:26 PM, Piotr Zarzycki  
> wrote:
> 
> I personally express important reason. Releasing can help community around
> VSCode and Moonshine.
> 
> Piotr
> 
> On Wed, Sep 19, 2018, 9:41 PM Alex Harui  wrote:
> 
>> What do you see as the important reasons?  I know the Apache mantra is to
>> release early and often, but if it were up to me, we would release after we
>> hit some interesting milestone, like getting Alina's app to compile
>> completely, or someone else says they are ready to go to production and
>> need a released version of Royale.  There are some bugs blocking users that
>> I would rather get done before releasing.
>> 
>> My 2 cents,
>> -Alex
>> 
>> On 9/19/18, 10:34 AM, "Harbs"  wrote:
>> 
>>I’m happy to try and be a release manager, but I don’t have time for
>> at least a month. I think it’s pretty important to get this release out
>> sooner rather than later.
>> 
>>If you can help Piotr finish this release, I’ll try to do the 0.9.5
>> release.
>> 
>>Thanks,
>>Harbs
>> 
>>> On Sep 19, 2018, at 6:54 PM, Alex Harui 
>> wrote:
>>> 
>>> Hi Piotr,
>>> 
>>> In my previous email, I was trying to say that you don't need to run
>> update.versions because I already did.
>>> In that and even earlier emails, we discussed running make_branches
>> twice.  IMO, you are getting the right results by running make_branches.
>> Given the current state of the repo, running make_branches once will set
>> the develop branch to 0.9.4-SNAPSHOT and the release branch to 0.9.3.
>> That's because that's how Maven works. The current poms in develop are set
>> to 0.9.3-SNAPSHOT.  Maven removes the "SNAPSHOT" in the release branch and
>> bumps the version in the develop branch.
>>> 
>>> I think you can just run make_branches again and it should create a
>> release branch with 0.9.4 and bump the develop branch to 0.9.5-SNAPSHOT.
>> That would be what we want.
>>> If you want me to help more, I will take the time to do so.  I can:
>>> -Get the repos to the point where the current scripts should "just
>> work".
>>> -Make sure make_branches works and is complete.
>>> -Do all of the other steps.
>>> 
>>> I still think it is important that someone else besides me can run
>> the scripts and generate a release.  So I would prefer to just get the
>> repos ready so that you can try running the scripts.  If there are
>> important things you've learned that other RMs will need to know, please
>> try to capture them in the wiki document.
>>> 
>>> @Carlos, I have spent a lot of time trying to automate releasing.
>> As Piotr said, skipping a version wasn't planned for and I hope it won't
>> ever happen again.  Unless you've actually looked at the scripts and read
>> the wiki document and tried it, saying you think there are too many manual
>> steps is not only wrong, but discouraging to those who have put effort into
>> it.  If you really think it needs to be better automated, then do it
>> yourself.  Don’t expect others to do things for you when you make negative
>> comments about their work.  I have other things I want to work on other
>> than release automation.  Release automation is only going to be "good
>> enough" and always in need of improvement.  We've only done two releases
>> and we are still debugging the scripts.   Join the effort instead of
>> complaining about it.
>>> 
>>> Thanks,
>>> -Alex
>>> 
>>> 
>>> On 9/19/18, 7:39 AM, "Carlos Rovira" > > wrote:
>>> 
>>>   Hi Piotr,
>>> 
>>>   sorry to hear that, I think we're out of resources. I'm
>> concentrating in
>>>   make Jewel as stable as possible since in few days we can start a
>> new
>>>   project with Royale-Jewel, so I still don't know how I'll be
>> doing to
>>>   continuer Jewel, make that project and continue with my other
>> tasks that my
>>>   position require.
>>> 
>>>   Maybe others could take this opportunity to make this happen
>>> 
>>>   Thanks
>>> 
>>>   Carlos
>>> 
>>> 
>>> 
>>>   El mié., 19 sept. 2018 a las 13:58, Piotr Zarzycki (<
>>>   piotrzarzyck...@gmail.com>) escribió:
>>> 
 Btw. The process is quite automatic, but skipping the version wasn't
 something considered before.
 
 On Wed, Sep 19, 2018, 1:31 PM Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
 wrote:
 
> Carlos,
> 
> Unfortunately I'm giving up doing that. I have spent on this too
>> much
 time
> and money. Someone else can continue from my point.
> 
> Dev branch is setup to 0.9.4-SNAPSHOT. Even with detailed
>> instruction
 from
> Alex I don't know what to do next.
> 
> Details are in previous email.
> 
> Good Luck!
> Piotr
> 
> On Wed, Sep 19, 2018, 1:15 PM Carlos Rovira <
>> carlosrov...@apache.org>
> wrote:
> 
>> Hi Piotr,
>> 
>> I encourage you and Alex to try to refine 

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

[Piotr Zarzycki]

I personally express important reason. Releasing can help community around
VSCode and Moonshine.

Piotr

On Wed, Sep 19, 2018, 9:41 PM Alex Harui  wrote:

> What do you see as the important reasons?  I know the Apache mantra is to
> release early and often, but if it were up to me, we would release after we
> hit some interesting milestone, like getting Alina's app to compile
> completely, or someone else says they are ready to go to production and
> need a released version of Royale.  There are some bugs blocking users that
> I would rather get done before releasing.
>
> My 2 cents,
> -Alex
>
> On 9/19/18, 10:34 AM, "Harbs"  wrote:
>
> I’m happy to try and be a release manager, but I don’t have time for
> at least a month. I think it’s pretty important to get this release out
> sooner rather than later.
>
> If you can help Piotr finish this release, I’ll try to do the 0.9.5
> release.
>
> Thanks,
> Harbs
>
> > On Sep 19, 2018, at 6:54 PM, Alex Harui 
> wrote:
> >
> > Hi Piotr,
> >
> > In my previous email, I was trying to say that you don't need to run
> update.versions because I already did.
> > In that and even earlier emails, we discussed running make_branches
> twice.  IMO, you are getting the right results by running make_branches.
>  Given the current state of the repo, running make_branches once will set
> the develop branch to 0.9.4-SNAPSHOT and the release branch to 0.9.3.
> That's because that's how Maven works. The current poms in develop are set
> to 0.9.3-SNAPSHOT.  Maven removes the "SNAPSHOT" in the release branch and
> bumps the version in the develop branch.
> >
> > I think you can just run make_branches again and it should create a
> release branch with 0.9.4 and bump the develop branch to 0.9.5-SNAPSHOT.
> That would be what we want.
> > If you want me to help more, I will take the time to do so.  I can:
> > -Get the repos to the point where the current scripts should "just
> work".
> > -Make sure make_branches works and is complete.
> > -Do all of the other steps.
> >
> > I still think it is important that someone else besides me can run
> the scripts and generate a release.  So I would prefer to just get the
> repos ready so that you can try running the scripts.  If there are
> important things you've learned that other RMs will need to know, please
> try to capture them in the wiki document.
> >
> > @Carlos, I have spent a lot of time trying to automate releasing.
> As Piotr said, skipping a version wasn't planned for and I hope it won't
> ever happen again.  Unless you've actually looked at the scripts and read
> the wiki document and tried it, saying you think there are too many manual
> steps is not only wrong, but discouraging to those who have put effort into
> it.  If you really think it needs to be better automated, then do it
> yourself.  Don’t expect others to do things for you when you make negative
> comments about their work.  I have other things I want to work on other
> than release automation.  Release automation is only going to be "good
> enough" and always in need of improvement.  We've only done two releases
> and we are still debugging the scripts.   Join the effort instead of
> complaining about it.
> >
> > Thanks,
> > -Alex
> >
> >
> > On 9/19/18, 7:39 AM, "Carlos Rovira"  > wrote:
> >
> >Hi Piotr,
> >
> >sorry to hear that, I think we're out of resources. I'm
> concentrating in
> >make Jewel as stable as possible since in few days we can start a
> new
> >project with Royale-Jewel, so I still don't know how I'll be
> doing to
> >continuer Jewel, make that project and continue with my other
> tasks that my
> >position require.
> >
> >Maybe others could take this opportunity to make this happen
> >
> >Thanks
> >
> >Carlos
> >
> >
> >
> >El mié., 19 sept. 2018 a las 13:58, Piotr Zarzycki (<
> >piotrzarzyck...@gmail.com>) escribió:
> >
> >> Btw. The process is quite automatic, but skipping the version wasn't
> >> something considered before.
> >>
> >> On Wed, Sep 19, 2018, 1:31 PM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >> wrote:
> >>
> >>> Carlos,
> >>>
> >>> Unfortunately I'm giving up doing that. I have spent on this too
> much
> >> time
> >>> and money. Someone else can continue from my point.
> >>>
> >>> Dev branch is setup to 0.9.4-SNAPSHOT. Even with detailed
> instruction
> >> from
> >>> Alex I don't know what to do next.
> >>>
> >>> Details are in previous email.
> >>>
> >>> Good Luck!
> >>> Piotr
> >>>
> >>> On Wed, Sep 19, 2018, 1:15 PM Carlos Rovira <
> carlosrov...@apache.org>
> >>> wrote:
> >>>
>  Hi Piotr,
> 
>  I encourage you and Alex to try to refine more the process

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

[Alex Harui]

What do you see as the important reasons?  I know the Apache mantra is to 
release early and often, but if it were up to me, we would release after we hit 
some interesting milestone, like getting Alina's app to compile completely, or 
someone else says they are ready to go to production and need a released 
version of Royale.  There are some bugs blocking users that I would rather get 
done before releasing.

My 2 cents,
-Alex

On 9/19/18, 10:34 AM, "Harbs"  wrote:

I’m happy to try and be a release manager, but I don’t have time for at 
least a month. I think it’s pretty important to get this release out sooner 
rather than later.

If you can help Piotr finish this release, I’ll try to do the 0.9.5 release.

Thanks,
Harbs

> On Sep 19, 2018, at 6:54 PM, Alex Harui  wrote:
> 
> Hi Piotr,
> 
> In my previous email, I was trying to say that you don't need to run 
update.versions because I already did.
> In that and even earlier emails, we discussed running make_branches 
twice.  IMO, you are getting the right results by running make_branches.   
Given the current state of the repo, running make_branches once will set the 
develop branch to 0.9.4-SNAPSHOT and the release branch to 0.9.3.  That's 
because that's how Maven works. The current poms in develop are set to 
0.9.3-SNAPSHOT.  Maven removes the "SNAPSHOT" in the release branch and bumps 
the version in the develop branch.
> 
> I think you can just run make_branches again and it should create a 
release branch with 0.9.4 and bump the develop branch to 0.9.5-SNAPSHOT.  That 
would be what we want.
> If you want me to help more, I will take the time to do so.  I can:
> -Get the repos to the point where the current scripts should "just work".
> -Make sure make_branches works and is complete.
> -Do all of the other steps.
> 
> I still think it is important that someone else besides me can run the 
scripts and generate a release.  So I would prefer to just get the repos ready 
so that you can try running the scripts.  If there are important things you've 
learned that other RMs will need to know, please try to capture them in the 
wiki document.
> 
> @Carlos, I have spent a lot of time trying to automate releasing.  As 
Piotr said, skipping a version wasn't planned for and I hope it won't ever 
happen again.  Unless you've actually looked at the scripts and read the wiki 
document and tried it, saying you think there are too many manual steps is not 
only wrong, but discouraging to those who have put effort into it.  If you 
really think it needs to be better automated, then do it yourself.  Don’t 
expect others to do things for you when you make negative comments about their 
work.  I have other things I want to work on other than release automation.  
Release automation is only going to be "good enough" and always in need of 
improvement.  We've only done two releases and we are still debugging the 
scripts.   Join the effort instead of complaining about it.
> 
> Thanks,
> -Alex
> 
> 
> On 9/19/18, 7:39 AM, "Carlos Rovira" mailto:carlosrov...@apache.org>> wrote:
> 
>Hi Piotr,
> 
>sorry to hear that, I think we're out of resources. I'm concentrating 
in
>make Jewel as stable as possible since in few days we can start a new
>project with Royale-Jewel, so I still don't know how I'll be doing to
>continuer Jewel, make that project and continue with my other tasks 
that my
>position require.
> 
>Maybe others could take this opportunity to make this happen
> 
>Thanks
> 
>Carlos
> 
> 
> 
>El mié., 19 sept. 2018 a las 13:58, Piotr Zarzycki (<
>piotrzarzyck...@gmail.com>) escribió:
> 
>> Btw. The process is quite automatic, but skipping the version wasn't
>> something considered before.
>> 
>> On Wed, Sep 19, 2018, 1:31 PM Piotr Zarzycki 
>> wrote:
>> 
>>> Carlos,
>>> 
>>> Unfortunately I'm giving up doing that. I have spent on this too much
>> time
>>> and money. Someone else can continue from my point.
>>> 
>>> Dev branch is setup to 0.9.4-SNAPSHOT. Even with detailed instruction
>> from
>>> Alex I don't know what to do next.
>>> 
>>> Details are in previous email.
>>> 
>>> Good Luck!
>>> Piotr
>>> 
>>> On Wed, Sep 19, 2018, 1:15 PM Carlos Rovira 
>>> wrote:
>>> 
 Hi Piotr,
 
 I encourage you and Alex to try to refine more the process so we can
 release more easily. I think right now the process is very dependent of
 many manual tasks, and that impact in all: huge effort to do the
>> release,
 many time involved, impossible to reproduce in next release,..
 
 I think this effort you're doing could be maybe the most important 
right
 now in Royale.
 

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

[Harbs]

I’m happy to try and be a release manager, but I don’t have time for at least a 
month. I think it’s pretty important to get this release out sooner rather than 
later.

If you can help Piotr finish this release, I’ll try to do the 0.9.5 release.

Thanks,
Harbs

> On Sep 19, 2018, at 6:54 PM, Alex Harui  wrote:
> 
> Hi Piotr,
> 
> In my previous email, I was trying to say that you don't need to run 
> update.versions because I already did.
> In that and even earlier emails, we discussed running make_branches twice.  
> IMO, you are getting the right results by running make_branches.   Given the 
> current state of the repo, running make_branches once will set the develop 
> branch to 0.9.4-SNAPSHOT and the release branch to 0.9.3.  That's because 
> that's how Maven works. The current poms in develop are set to 
> 0.9.3-SNAPSHOT.  Maven removes the "SNAPSHOT" in the release branch and bumps 
> the version in the develop branch.
> 
> I think you can just run make_branches again and it should create a release 
> branch with 0.9.4 and bump the develop branch to 0.9.5-SNAPSHOT.  That would 
> be what we want.
> If you want me to help more, I will take the time to do so.  I can:
> -Get the repos to the point where the current scripts should "just work".
> -Make sure make_branches works and is complete.
> -Do all of the other steps.
> 
> I still think it is important that someone else besides me can run the 
> scripts and generate a release.  So I would prefer to just get the repos 
> ready so that you can try running the scripts.  If there are important things 
> you've learned that other RMs will need to know, please try to capture them 
> in the wiki document.
> 
> @Carlos, I have spent a lot of time trying to automate releasing.  As Piotr 
> said, skipping a version wasn't planned for and I hope it won't ever happen 
> again.  Unless you've actually looked at the scripts and read the wiki 
> document and tried it, saying you think there are too many manual steps is 
> not only wrong, but discouraging to those who have put effort into it.  If 
> you really think it needs to be better automated, then do it yourself.  Don’t 
> expect others to do things for you when you make negative comments about 
> their work.  I have other things I want to work on other than release 
> automation.  Release automation is only going to be "good enough" and always 
> in need of improvement.  We've only done two releases and we are still 
> debugging the scripts.   Join the effort instead of complaining about it.
> 
> Thanks,
> -Alex
> 
> 
> On 9/19/18, 7:39 AM, "Carlos Rovira"  > wrote:
> 
>Hi Piotr,
> 
>sorry to hear that, I think we're out of resources. I'm concentrating in
>make Jewel as stable as possible since in few days we can start a new
>project with Royale-Jewel, so I still don't know how I'll be doing to
>continuer Jewel, make that project and continue with my other tasks that my
>position require.
> 
>Maybe others could take this opportunity to make this happen
> 
>Thanks
> 
>Carlos
> 
> 
> 
>El mié., 19 sept. 2018 a las 13:58, Piotr Zarzycki (<
>piotrzarzyck...@gmail.com>) escribió:
> 
>> Btw. The process is quite automatic, but skipping the version wasn't
>> something considered before.
>> 
>> On Wed, Sep 19, 2018, 1:31 PM Piotr Zarzycki 
>> wrote:
>> 
>>> Carlos,
>>> 
>>> Unfortunately I'm giving up doing that. I have spent on this too much
>> time
>>> and money. Someone else can continue from my point.
>>> 
>>> Dev branch is setup to 0.9.4-SNAPSHOT. Even with detailed instruction
>> from
>>> Alex I don't know what to do next.
>>> 
>>> Details are in previous email.
>>> 
>>> Good Luck!
>>> Piotr
>>> 
>>> On Wed, Sep 19, 2018, 1:15 PM Carlos Rovira 
>>> wrote:
>>> 
 Hi Piotr,
 
 I encourage you and Alex to try to refine more the process so we can
 release more easily. I think right now the process is very dependent of
 many manual tasks, and that impact in all: huge effort to do the
>> release,
 many time involved, impossible to reproduce in next release,..
 
 I think this effort you're doing could be maybe the most important right
 now in Royale.
 
 Maybe you could ask for some help to other Apache teams, maybe infra
 people?, or maven people?
 
 Thanks for taking over this
 
 Carlos
 
 
 
 
 El mié., 19 sept. 2018 a las 11:16, Olaf Krueger (>> )
 escribió:
 
>> All of that things are complex because we need to skip one
>> version...
> 
> Would it be possible to create something like a fake release v0.9.3?
> Just to satisfy all those tools and automatism?
> 
> Olaf
> 
> 
> 
> 
> --
> Sent from: 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7Cb352978d4d564be3bf8408d61e3da3a8%7Cfa7b1b5a7b3443879

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

[Piotr Zarzycki]

Process is definitely automated. If we would not skip version we would have
RC1 two days ago from me. I got dedicated time for making that release,
cause it can help improve Josh's plugin - which is using Royale compiler.
As you know that plugin is used in VSCode and Moonshine, so Framework part
release is not as important as you may think from my point of view.

If someone finish current release my proposition is to have ability of
releasing compiler only without Framework next time. - I hope to get more
dedicated time and make it happen.

I hope someone pickup what has been left and make RC1.

Thanks,
Piotr

śr., 19 wrz 2018 o 18:43 Alex Harui  napisał(a):

> IMO, speculating things to be worse than they are without being informed
> is not good for the community.
>
> Piotr ran into problems because we were forced to try to skip a version.
> Again, there is nobody whose job it is to make releasing simple, and who
> will take the time to try to anticipate these situations and make the
> automation handle them.  This is a volunteer effort.
>
> Think about how it will help the community before saying something
> negative.  What change did you expect volunteers to be motivated to do  by
> saying there are too many manual steps?
>
> -Alex
>
> On 9/19/18, 9:25 AM, "Carlos Rovira"  wrote:
>
> Hi Alex,
>
> don't think each comment is negative only because is not positive! I
> already said some words recognizing the huge effort behind that task. I
> know how hard it is.
> But as I said the great work done, I want to expose the only point I
> think
> is problematic, the difficult of the process. And I think is something
> all
> people here is aware that the process is non trivial at all. For that
> reason I only said that maybe even more automation is needed.
>
> One thing is clear, I want to be release manager soon, the only thing
> that
> stops me is that I have plenty of things on my plate right now, so my
> effort is more needed in the actual fronts that is mostly complete and
> stabilize Jewel and make the first real project with it for an
> important
> company. Both things are, IMHO, very needed as well, even more than
> release
> now for me, so for that reason and prioritizing, if I have to choose,
> I'll
> have to put that on third place.
>
> So please, only because I expose a thing that is happening don't think
> it
> could be seen as a critic about your work, since is not what I'm
> saying. I
> think you did a great job automatizing the release process. I only say
> that
> maybe it needs to go a bit far and solve final problems so others like
> me
> can jump to that wagon some day and help in that task. If we think
> there's
> no problem now, we must why Piotr is throwing the towel since he
> doesn't
> see the way to continue, and I think we'll end thinking that we need
> that
> final refinement in the process.
>
> As you say, I still don't have the knowledge since I still didn't get
> my
> hands dirty with the release process, so anything I say maybe is wrong,
> only  is what I can say from what I see / read this days.
>
> Thanks
>
> Carlos
>
>
>
>
>
>
> El mié., 19 sept. 2018 a las 17:54, Alex Harui
> ()
> escribió:
>
> > Hi Piotr,
> >
> > In my previous email, I was trying to say that you don't need to run
> > update.versions because I already did.
> > In that and even earlier emails, we discussed running make_branches
> > twice.  IMO, you are getting the right results by running
> make_branches.
> >  Given the current state of the repo, running make_branches once
> will set
> > the develop branch to 0.9.4-SNAPSHOT and the release branch to 0.9.3.
> > That's because that's how Maven works.  The current poms in develop
> are set
> > to 0.9.3-SNAPSHOT.  Maven removes the "SNAPSHOT" in the release
> branch and
> > bumps the version in the develop branch.
> >
> > I think you can just run make_branches again and it should create a
> > release branch with 0.9.4 and bump the develop branch to
> 0.9.5-SNAPSHOT.
> > That would be what we want.
> > If you want me to help more, I will take the time to do so.  I can:
> > -Get the repos to the point where the current scripts should "just
> work".
> > -Make sure make_branches works and is complete.
> > -Do all of the other steps.
> >
> > I still think it is important that someone else besides me can run
> the
> > scripts and generate a release.  So I would prefer to just get the
> repos
> > ready so that you can try running the scripts.  If there are
> important
> > things you've learned that other RMs will need to know, please try to
> > capture them in the wiki document.
> >
> > @Carlos, I have spent a lot of time trying to automate releasing.  As
> > Piotr said, skipping a version wasn't planned for and I hope it
> won't ever
> > 

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

[Alex Harui]

IMO, speculating things to be worse than they are without being informed is not 
good for the community.

Piotr ran into problems because we were forced to try to skip a version.  
Again, there is nobody whose job it is to make releasing simple, and who will 
take the time to try to anticipate these situations and make the automation 
handle them.  This is a volunteer effort.

Think about how it will help the community before saying something negative.  
What change did you expect volunteers to be motivated to do  by saying there 
are too many manual steps?

-Alex

On 9/19/18, 9:25 AM, "Carlos Rovira"  wrote:

Hi Alex,

don't think each comment is negative only because is not positive! I
already said some words recognizing the huge effort behind that task. I
know how hard it is.
But as I said the great work done, I want to expose the only point I think
is problematic, the difficult of the process. And I think is something all
people here is aware that the process is non trivial at all. For that
reason I only said that maybe even more automation is needed.

One thing is clear, I want to be release manager soon, the only thing that
stops me is that I have plenty of things on my plate right now, so my
effort is more needed in the actual fronts that is mostly complete and
stabilize Jewel and make the first real project with it for an important
company. Both things are, IMHO, very needed as well, even more than release
now for me, so for that reason and prioritizing, if I have to choose, I'll
have to put that on third place.

So please, only because I expose a thing that is happening don't think it
could be seen as a critic about your work, since is not what I'm saying. I
think you did a great job automatizing the release process. I only say that
maybe it needs to go a bit far and solve final problems so others like me
can jump to that wagon some day and help in that task. If we think there's
no problem now, we must why Piotr is throwing the towel since he doesn't
see the way to continue, and I think we'll end thinking that we need that
final refinement in the process.

As you say, I still don't have the knowledge since I still didn't get my
hands dirty with the release process, so anything I say maybe is wrong,
only  is what I can say from what I see / read this days.

Thanks

Carlos






El mié., 19 sept. 2018 a las 17:54, Alex Harui ()
escribió:

> Hi Piotr,
>
> In my previous email, I was trying to say that you don't need to run
> update.versions because I already did.
> In that and even earlier emails, we discussed running make_branches
> twice.  IMO, you are getting the right results by running make_branches.
>  Given the current state of the repo, running make_branches once will set
> the develop branch to 0.9.4-SNAPSHOT and the release branch to 0.9.3.
> That's because that's how Maven works.  The current poms in develop are 
set
> to 0.9.3-SNAPSHOT.  Maven removes the "SNAPSHOT" in the release branch and
> bumps the version in the develop branch.
>
> I think you can just run make_branches again and it should create a
> release branch with 0.9.4 and bump the develop branch to 0.9.5-SNAPSHOT.
> That would be what we want.
> If you want me to help more, I will take the time to do so.  I can:
> -Get the repos to the point where the current scripts should "just work".
> -Make sure make_branches works and is complete.
> -Do all of the other steps.
>
> I still think it is important that someone else besides me can run the
> scripts and generate a release.  So I would prefer to just get the repos
> ready so that you can try running the scripts.  If there are important
> things you've learned that other RMs will need to know, please try to
> capture them in the wiki document.
>
> @Carlos, I have spent a lot of time trying to automate releasing.  As
> Piotr said, skipping a version wasn't planned for and I hope it won't ever
> happen again.  Unless you've actually looked at the scripts and read the
> wiki document and tried it, saying you think there are too many manual
> steps is not only wrong, but discouraging to those who have put effort 
into
> it.  If you really think it needs to be better automated, then do it
> yourself.  Don’t expect others to do things for you when you make negative
> comments about their work.  I have other things I want to work on other
> than release automation.  Release automation is only going to be "good
> enough" and always in need of improvement.  We've only done two releases
> and we are still debugging the scripts.   Join the effort instead of
> complaining about it.
>
> Thanks,
> -Alex
>
>
> On 9/19/18, 7:39 AM, "Carlos Rovira"  wr

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

[Carlos Rovira]

Hi Alex,

don't think each comment is negative only because is not positive! I
already said some words recognizing the huge effort behind that task. I
know how hard it is.
But as I said the great work done, I want to expose the only point I think
is problematic, the difficult of the process. And I think is something all
people here is aware that the process is non trivial at all. For that
reason I only said that maybe even more automation is needed.

One thing is clear, I want to be release manager soon, the only thing that
stops me is that I have plenty of things on my plate right now, so my
effort is more needed in the actual fronts that is mostly complete and
stabilize Jewel and make the first real project with it for an important
company. Both things are, IMHO, very needed as well, even more than release
now for me, so for that reason and prioritizing, if I have to choose, I'll
have to put that on third place.

So please, only because I expose a thing that is happening don't think it
could be seen as a critic about your work, since is not what I'm saying. I
think you did a great job automatizing the release process. I only say that
maybe it needs to go a bit far and solve final problems so others like me
can jump to that wagon some day and help in that task. If we think there's
no problem now, we must why Piotr is throwing the towel since he doesn't
see the way to continue, and I think we'll end thinking that we need that
final refinement in the process.

As you say, I still don't have the knowledge since I still didn't get my
hands dirty with the release process, so anything I say maybe is wrong,
only  is what I can say from what I see / read this days.

Thanks

Carlos






El mié., 19 sept. 2018 a las 17:54, Alex Harui ()
escribió:

> Hi Piotr,
>
> In my previous email, I was trying to say that you don't need to run
> update.versions because I already did.
> In that and even earlier emails, we discussed running make_branches
> twice.  IMO, you are getting the right results by running make_branches.
>  Given the current state of the repo, running make_branches once will set
> the develop branch to 0.9.4-SNAPSHOT and the release branch to 0.9.3.
> That's because that's how Maven works.  The current poms in develop are set
> to 0.9.3-SNAPSHOT.  Maven removes the "SNAPSHOT" in the release branch and
> bumps the version in the develop branch.
>
> I think you can just run make_branches again and it should create a
> release branch with 0.9.4 and bump the develop branch to 0.9.5-SNAPSHOT.
> That would be what we want.
> If you want me to help more, I will take the time to do so.  I can:
> -Get the repos to the point where the current scripts should "just work".
> -Make sure make_branches works and is complete.
> -Do all of the other steps.
>
> I still think it is important that someone else besides me can run the
> scripts and generate a release.  So I would prefer to just get the repos
> ready so that you can try running the scripts.  If there are important
> things you've learned that other RMs will need to know, please try to
> capture them in the wiki document.
>
> @Carlos, I have spent a lot of time trying to automate releasing.  As
> Piotr said, skipping a version wasn't planned for and I hope it won't ever
> happen again.  Unless you've actually looked at the scripts and read the
> wiki document and tried it, saying you think there are too many manual
> steps is not only wrong, but discouraging to those who have put effort into
> it.  If you really think it needs to be better automated, then do it
> yourself.  Don’t expect others to do things for you when you make negative
> comments about their work.  I have other things I want to work on other
> than release automation.  Release automation is only going to be "good
> enough" and always in need of improvement.  We've only done two releases
> and we are still debugging the scripts.   Join the effort instead of
> complaining about it.
>
> Thanks,
> -Alex
>
>
> On 9/19/18, 7:39 AM, "Carlos Rovira"  wrote:
>
> Hi Piotr,
>
> sorry to hear that, I think we're out of resources. I'm concentrating
> in
> make Jewel as stable as possible since in few days we can start a new
> project with Royale-Jewel, so I still don't know how I'll be doing to
> continuer Jewel, make that project and continue with my other tasks
> that my
> position require.
>
> Maybe others could take this opportunity to make this happen
>
> Thanks
>
> Carlos
>
>
>
> El mié., 19 sept. 2018 a las 13:58, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Btw. The process is quite automatic, but skipping the version wasn't
> > something considered before.
> >
> > On Wed, Sep 19, 2018, 1:31 PM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > wrote:
> >
> > > Carlos,
> > >
> > > Unfortunately I'm giving up doing that. I have spent on this too
> much
> > time
> > > and money. Someone else can c

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

[Alex Harui]

Hi Piotr,

In my previous email, I was trying to say that you don't need to run 
update.versions because I already did.
In that and even earlier emails, we discussed running make_branches twice.  
IMO, you are getting the right results by running make_branches.   Given the 
current state of the repo, running make_branches once will set the develop 
branch to 0.9.4-SNAPSHOT and the release branch to 0.9.3.  That's because 
that's how Maven works.  The current poms in develop are set to 0.9.3-SNAPSHOT. 
 Maven removes the "SNAPSHOT" in the release branch and bumps the version in 
the develop branch.

I think you can just run make_branches again and it should create a release 
branch with 0.9.4 and bump the develop branch to 0.9.5-SNAPSHOT.  That would be 
what we want.
If you want me to help more, I will take the time to do so.  I can:
-Get the repos to the point where the current scripts should "just work".
-Make sure make_branches works and is complete.
-Do all of the other steps.

I still think it is important that someone else besides me can run the scripts 
and generate a release.  So I would prefer to just get the repos ready so that 
you can try running the scripts.  If there are important things you've learned 
that other RMs will need to know, please try to capture them in the wiki 
document.

@Carlos, I have spent a lot of time trying to automate releasing.  As Piotr 
said, skipping a version wasn't planned for and I hope it won't ever happen 
again.  Unless you've actually looked at the scripts and read the wiki document 
and tried it, saying you think there are too many manual steps is not only 
wrong, but discouraging to those who have put effort into it.  If you really 
think it needs to be better automated, then do it yourself.  Don’t expect 
others to do things for you when you make negative comments about their work.  
I have other things I want to work on other than release automation.  Release 
automation is only going to be "good enough" and always in need of improvement. 
 We've only done two releases and we are still debugging the scripts.   Join 
the effort instead of complaining about it.

Thanks,
-Alex


On 9/19/18, 7:39 AM, "Carlos Rovira"  wrote:

Hi Piotr,

sorry to hear that, I think we're out of resources. I'm concentrating in
make Jewel as stable as possible since in few days we can start a new
project with Royale-Jewel, so I still don't know how I'll be doing to
continuer Jewel, make that project and continue with my other tasks that my
position require.

Maybe others could take this opportunity to make this happen

Thanks

Carlos



El mié., 19 sept. 2018 a las 13:58, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Btw. The process is quite automatic, but skipping the version wasn't
> something considered before.
>
> On Wed, Sep 19, 2018, 1:31 PM Piotr Zarzycki 
> wrote:
>
> > Carlos,
> >
> > Unfortunately I'm giving up doing that. I have spent on this too much
> time
> > and money. Someone else can continue from my point.
> >
> > Dev branch is setup to 0.9.4-SNAPSHOT. Even with detailed instruction
> from
> > Alex I don't know what to do next.
> >
> > Details are in previous email.
> >
> > Good Luck!
> > Piotr
> >
> > On Wed, Sep 19, 2018, 1:15 PM Carlos Rovira 
> > wrote:
> >
> >> Hi Piotr,
> >>
> >> I encourage you and Alex to try to refine more the process so we can
> >> release more easily. I think right now the process is very dependent of
> >> many manual tasks, and that impact in all: huge effort to do the
> release,
> >> many time involved, impossible to reproduce in next release,..
> >>
> >> I think this effort you're doing could be maybe the most important 
right
> >> now in Royale.
> >>
> >> Maybe you could ask for some help to other Apache teams, maybe infra
> >> people?, or maven people?
> >>
> >> Thanks for taking over this
> >>
> >> Carlos
> >>
> >>
> >>
> >>
> >> El mié., 19 sept. 2018 a las 11:16, Olaf Krueger ( >)
> >> escribió:
> >>
> >> > > All of that things are complex because we need to skip one
> version...
> >> >
> >> > Would it be possible to create something like a fake release v0.9.3?
> >> > Just to satisfy all those tools and automatism?
> >> >
> >> > Olaf
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7Cb352978d4d564be3bf8408d61e3da3a8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636729647419991836&sdata=vN2nU7GGQsBYX7QMUuqYinlUJax6IGbjJJjCCRmJrc4%3D&reserved=0
> >> >
> >>
> >>
> >> --
> >> Carlos Rovira
> >> 
https://na01.safelinks.protectio

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

[Carlos Rovira]

Hi Piotr,

sorry to hear that, I think we're out of resources. I'm concentrating in
make Jewel as stable as possible since in few days we can start a new
project with Royale-Jewel, so I still don't know how I'll be doing to
continuer Jewel, make that project and continue with my other tasks that my
position require.

Maybe others could take this opportunity to make this happen

Thanks

Carlos



El mié., 19 sept. 2018 a las 13:58, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Btw. The process is quite automatic, but skipping the version wasn't
> something considered before.
>
> On Wed, Sep 19, 2018, 1:31 PM Piotr Zarzycki 
> wrote:
>
> > Carlos,
> >
> > Unfortunately I'm giving up doing that. I have spent on this too much
> time
> > and money. Someone else can continue from my point.
> >
> > Dev branch is setup to 0.9.4-SNAPSHOT. Even with detailed instruction
> from
> > Alex I don't know what to do next.
> >
> > Details are in previous email.
> >
> > Good Luck!
> > Piotr
> >
> > On Wed, Sep 19, 2018, 1:15 PM Carlos Rovira 
> > wrote:
> >
> >> Hi Piotr,
> >>
> >> I encourage you and Alex to try to refine more the process so we can
> >> release more easily. I think right now the process is very dependent of
> >> many manual tasks, and that impact in all: huge effort to do the
> release,
> >> many time involved, impossible to reproduce in next release,..
> >>
> >> I think this effort you're doing could be maybe the most important right
> >> now in Royale.
> >>
> >> Maybe you could ask for some help to other Apache teams, maybe infra
> >> people?, or maven people?
> >>
> >> Thanks for taking over this
> >>
> >> Carlos
> >>
> >>
> >>
> >>
> >> El mié., 19 sept. 2018 a las 11:16, Olaf Krueger ( >)
> >> escribió:
> >>
> >> > > All of that things are complex because we need to skip one
> version...
> >> >
> >> > Would it be possible to create something like a fake release v0.9.3?
> >> > Just to satisfy all those tools and automatism?
> >> >
> >> > Olaf
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Sent from: http://apache-royale-development.20373.n8.nabble.com/
> >> >
> >>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >
>


-- 
Carlos Rovira
http://about.me/carlosrovira

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

[Piotr Zarzycki]

Btw. The process is quite automatic, but skipping the version wasn't
something considered before.

On Wed, Sep 19, 2018, 1:31 PM Piotr Zarzycki 
wrote:

> Carlos,
>
> Unfortunately I'm giving up doing that. I have spent on this too much time
> and money. Someone else can continue from my point.
>
> Dev branch is setup to 0.9.4-SNAPSHOT. Even with detailed instruction from
> Alex I don't know what to do next.
>
> Details are in previous email.
>
> Good Luck!
> Piotr
>
> On Wed, Sep 19, 2018, 1:15 PM Carlos Rovira 
> wrote:
>
>> Hi Piotr,
>>
>> I encourage you and Alex to try to refine more the process so we can
>> release more easily. I think right now the process is very dependent of
>> many manual tasks, and that impact in all: huge effort to do the release,
>> many time involved, impossible to reproduce in next release,..
>>
>> I think this effort you're doing could be maybe the most important right
>> now in Royale.
>>
>> Maybe you could ask for some help to other Apache teams, maybe infra
>> people?, or maven people?
>>
>> Thanks for taking over this
>>
>> Carlos
>>
>>
>>
>>
>> El mié., 19 sept. 2018 a las 11:16, Olaf Krueger ()
>> escribió:
>>
>> > > All of that things are complex because we need to skip one version...
>> >
>> > Would it be possible to create something like a fake release v0.9.3?
>> > Just to satisfy all those tools and automatism?
>> >
>> > Olaf
>> >
>> >
>> >
>> >
>> > --
>> > Sent from: http://apache-royale-development.20373.n8.nabble.com/
>> >
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>

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

[Piotr Zarzycki]

Carlos,

Unfortunately I'm giving up doing that. I have spent on this too much time
and money. Someone else can continue from my point.

Dev branch is setup to 0.9.4-SNAPSHOT. Even with detailed instruction from
Alex I don't know what to do next.

Details are in previous email.

Good Luck!
Piotr

On Wed, Sep 19, 2018, 1:15 PM Carlos Rovira  wrote:

> Hi Piotr,
>
> I encourage you and Alex to try to refine more the process so we can
> release more easily. I think right now the process is very dependent of
> many manual tasks, and that impact in all: huge effort to do the release,
> many time involved, impossible to reproduce in next release,..
>
> I think this effort you're doing could be maybe the most important right
> now in Royale.
>
> Maybe you could ask for some help to other Apache teams, maybe infra
> people?, or maven people?
>
> Thanks for taking over this
>
> Carlos
>
>
>
>
> El mié., 19 sept. 2018 a las 11:16, Olaf Krueger ()
> escribió:
>
> > > All of that things are complex because we need to skip one version...
> >
> > Would it be possible to create something like a fake release v0.9.3?
> > Just to satisfy all those tools and automatism?
> >
> > Olaf
> >
> >
> >
> >
> > --
> > Sent from: http://apache-royale-development.20373.n8.nabble.com/
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

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

[Carlos Rovira]

Hi Piotr,

I encourage you and Alex to try to refine more the process so we can
release more easily. I think right now the process is very dependent of
many manual tasks, and that impact in all: huge effort to do the release,
many time involved, impossible to reproduce in next release,..

I think this effort you're doing could be maybe the most important right
now in Royale.

Maybe you could ask for some help to other Apache teams, maybe infra
people?, or maven people?

Thanks for taking over this

Carlos




El mié., 19 sept. 2018 a las 11:16, Olaf Krueger ()
escribió:

> > All of that things are complex because we need to skip one version...
>
> Would it be possible to create something like a fake release v0.9.3?
> Just to satisfy all those tools and automatism?
>
> Olaf
>
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>


-- 
Carlos Rovira
http://about.me/carlosrovira

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

[Olaf Krueger]

> All of that things are complex because we need to skip one version...

Would it be possible to create something like a fake release v0.9.3?
Just to satisfy all those tools and automatism?

Olaf




--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

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

[Piotr Zarzycki]

We are releasing from specific commit. The problem is laying out on setup
appropriate values for ANT build and Maven build. This is where all
failing.
All the problem is happening because we need omit one version, cause npm
was updated with 0.9.3 - Not sure why.

Update of version should happen automatically and releasecandidate script
is doing that. I don't know now what to do:

1. Update develop branch from 0.9.4-SNAPSHOT to 0.9.5-SNAPSHOT
2. Update release/0.9.4 to 0.9.4
3. Deploy maven artifacts to staging area

All of that things are complex because we need to skip one version. I'm the
second release manager (after Om) who gave up with whole process.

Piotr

śr., 19 wrz 2018 o 10:59 Carlos Rovira  napisał(a):

> Hi Olaf,
>
> hehe, I think we overlap and mostly said the same ;-)
> for me that's the right way.
> Thanks
>
>
>
> El mié., 19 sept. 2018 a las 10:57, Olaf Krueger ()
> escribió:
>
> > > I think there should be some rules where during release process
> > committing
> > > to develop is stopped.
> >
> > What do you think about creating a "release/v0.9.x" branch which has to
> be
> > merged back to master and dev after the release is done instead of doing
> > the
> > release from dev?
> >
> > Thanks for doing all the hard work, keep it up!!!
> >
> > Olaf
> >
> >
> >
> >
> >
> > --
> > Sent from: http://apache-royale-development.20373.n8.nabble.com/
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

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

[Carlos Rovira]

Hi Olaf,

hehe, I think we overlap and mostly said the same ;-)
for me that's the right way.
Thanks



El mié., 19 sept. 2018 a las 10:57, Olaf Krueger ()
escribió:

> > I think there should be some rules where during release process
> committing
> > to develop is stopped.
>
> What do you think about creating a "release/v0.9.x" branch which has to be
> merged back to master and dev after the release is done instead of doing
> the
> release from dev?
>
> Thanks for doing all the hard work, keep it up!!!
>
> Olaf
>
>
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>


-- 
Carlos Rovira
http://about.me/carlosrovira

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

[Carlos Rovira]

Hi Piotr,

I still doesn't have knowledge of the release process, but hope to be the
next release manager. In the meanwhile, I'm following things, and what I
think, (of course without know to much about the real process and
implications in this concrete project), is that we should do the same as
others do, and that means releasing from a concrete commit in the develop
branch, that should generate the needed branches to manage the release
process and develop should continue its own way. At some point, once
release is done, release branch is merged in develop and master.

At least that's how I see it. In other words, we should not be different in
methodology to what other hundreds or thousands of projects do and in this
field follow the manual.

Thanks

Carlos




El mié., 19 sept. 2018 a las 10:39, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> I think everything is messed up right now. Before I got your response I was
> in a state where I run:
>
> ant -f releasecandidate.xml -Drelease.version=0.9.4 -Drc=1 make_branches
>
> It pushes to the develop 0.9.4-SNAPSHOT
> It pushes release branch called 0.9.4 where there is 0.9.3-SNAPSHOT - Not
> sure why.
>
> I wanted to revert it, but lot's of people commit things to develop, so I
> have no idea how to do that right now.
> I think there should be some rules where during release process committing
> to develop is stopped.
>
> I have tried update.versions on develop:
>
>  ant -f releasecandidate.xml -Drelease.version=0.9.4 -Drc=1 update.versions
> and it asked me on the next version and I typed 0.9.5, but it changes only
> couple of files.
>
> I have no idea how to fix all of that right now.
>
>
>
> pon., 17 wrz 2018 o 18:07 Alex Harui 
> napisał(a):
>
> > Last week, the develop branch was setup to release as 0.9.3 since the
> > prior release was 0.9.2.  The scripts and defaults are not set up to
> skip a
> > version so we discussed ways to skip a version.  It included:
> >
> > 1) Running "ant -f releasecandidate.xml update.versions"
> > 2) Using "ant -f releasecandidate.xml make_branches" twice.
> >
> > The first run would set the poms in the release branch to 0.9.3 and set
> > the develop branch to 0.9.4-SNAPSHOT.
> > The second run would set the poms in the release branch to 0.9.4 and set
> > the develop branch to 0.9.5-SNAPSHOT.
> >
> > The correct state of the branches before executing step 4 in
> >
> https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes#release-steps
> > is that the develop branch is set to 0.9.5-SNAPSHOT, the release branch
> is
> > set to 0.9.4, and other version numbers are set to 0.9.4, such as
> > build.properties in royale-asjs.  That's what update.versions did.  I did
> > that a couple of days ago.
> >
> > So, to answer your questions:
> >
> > 1) No, there shouldn't be any extra Ant targets to run at this time other
> > than maybe running make_branches on some or all of the repos to get us to
> > the desired state.  I think I've taken care of everything that
> > make_branches doesn't take care of.  I did not try to get all of the
> Maven
> > pieces in the 3 repos ready because I thought I saw that royale-typedefs
> > was already ready so I didn't know where you were in the process.  Some
> of
> > the targets in releasecandidate.xml run lots of Maven commands which will
> > update the POMs.  Those targets also patch some other things that Maven
> > needs but were hard to make work via Maven.  Since updating the
> > Maven-related data could not be one simple Maven command, I chose to use
> > Ant to take the RM through all of the steps.   But Ant builds do not use
> > the POM (although I'm still thinking of teaching the compiler to read the
> > POMs) so we have other Ant targets that update things for the Ant build
> of
> > the framework.  This is normally done during the final "release" target
> > after voting is over, but because we are skipping a version, I had to run
> > it once a few days ago.
> >
> > 2)  IMO, the simplest thing to do is update the develop branch so it
> looks
> > like we released a 0.9.3 before creating the final release branch for
> > 0.9.4.  That is why I am suggesting running make_branches until you reach
> > that state.  I think I've already taken care of the Ant properties.
> >
> > When you think you've got the branches for all repos in this state, let
> me
> > know and I will spot check it.
> >
> > HTH,
> > -Alex
> >
> > On 9/17/18, 2:06 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Still don't understand what you did at all. I did make_branches. This
> > is
> > what happened so far:
> >
> > 1) feature/0.9.4 -> branch has been created which contains 0.9.3 in
> > poms
> > 2) develop has been updated to 0.9.4-SNAPSHOT
> >
> > Q 1: Should I run on develop ant command which updating for me some
> > stuff ?
> > - What ANT do ? Does it update pom or something else ?
> > Q 2: Because we would like to jump to one version ahead - Should I
> run
> > that
> > ANT on RC1 b

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

[Olaf Krueger]

> I think there should be some rules where during release process committing 
> to develop is stopped. 

What do you think about creating a "release/v0.9.x" branch which has to be
merged back to master and dev after the release is done instead of doing the
release from dev?

Thanks for doing all the hard work, keep it up!!!

Olaf





--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

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

[Piotr Zarzycki]

I think everything is messed up right now. Before I got your response I was
in a state where I run:

ant -f releasecandidate.xml -Drelease.version=0.9.4 -Drc=1 make_branches

It pushes to the develop 0.9.4-SNAPSHOT
It pushes release branch called 0.9.4 where there is 0.9.3-SNAPSHOT - Not
sure why.

I wanted to revert it, but lot's of people commit things to develop, so I
have no idea how to do that right now.
I think there should be some rules where during release process committing
to develop is stopped.

I have tried update.versions on develop:

 ant -f releasecandidate.xml -Drelease.version=0.9.4 -Drc=1 update.versions
and it asked me on the next version and I typed 0.9.5, but it changes only
couple of files.

I have no idea how to fix all of that right now.



pon., 17 wrz 2018 o 18:07 Alex Harui  napisał(a):

> Last week, the develop branch was setup to release as 0.9.3 since the
> prior release was 0.9.2.  The scripts and defaults are not set up to skip a
> version so we discussed ways to skip a version.  It included:
>
> 1) Running "ant -f releasecandidate.xml update.versions"
> 2) Using "ant -f releasecandidate.xml make_branches" twice.
>
> The first run would set the poms in the release branch to 0.9.3 and set
> the develop branch to 0.9.4-SNAPSHOT.
> The second run would set the poms in the release branch to 0.9.4 and set
> the develop branch to 0.9.5-SNAPSHOT.
>
> The correct state of the branches before executing step 4 in
> https://github.com/apache/royale-asjs/wiki/Release-Manager-Notes#release-steps
> is that the develop branch is set to 0.9.5-SNAPSHOT, the release branch is
> set to 0.9.4, and other version numbers are set to 0.9.4, such as
> build.properties in royale-asjs.  That's what update.versions did.  I did
> that a couple of days ago.
>
> So, to answer your questions:
>
> 1) No, there shouldn't be any extra Ant targets to run at this time other
> than maybe running make_branches on some or all of the repos to get us to
> the desired state.  I think I've taken care of everything that
> make_branches doesn't take care of.  I did not try to get all of the Maven
> pieces in the 3 repos ready because I thought I saw that royale-typedefs
> was already ready so I didn't know where you were in the process.  Some of
> the targets in releasecandidate.xml run lots of Maven commands which will
> update the POMs.  Those targets also patch some other things that Maven
> needs but were hard to make work via Maven.  Since updating the
> Maven-related data could not be one simple Maven command, I chose to use
> Ant to take the RM through all of the steps.   But Ant builds do not use
> the POM (although I'm still thinking of teaching the compiler to read the
> POMs) so we have other Ant targets that update things for the Ant build of
> the framework.  This is normally done during the final "release" target
> after voting is over, but because we are skipping a version, I had to run
> it once a few days ago.
>
> 2)  IMO, the simplest thing to do is update the develop branch so it looks
> like we released a 0.9.3 before creating the final release branch for
> 0.9.4.  That is why I am suggesting running make_branches until you reach
> that state.  I think I've already taken care of the Ant properties.
>
> When you think you've got the branches for all repos in this state, let me
> know and I will spot check it.
>
> HTH,
> -Alex
>
> On 9/17/18, 2:06 AM, "Piotr Zarzycki"  wrote:
>
> Still don't understand what you did at all. I did make_branches. This
> is
> what happened so far:
>
> 1) feature/0.9.4 -> branch has been created which contains 0.9.3 in
> poms
> 2) develop has been updated to 0.9.4-SNAPSHOT
>
> Q 1: Should I run on develop ant command which updating for me some
> stuff ?
> - What ANT do ? Does it update pom or something else ?
> Q 2: Because we would like to jump to one version ahead - Should I run
> that
> ANT on RC1 branch or should I update it manually ?
>
> Thanks,
> Piotr
>
>
> pon., 17 wrz 2018 o 09:53 Alex Harui 
> napisał(a):
>
> > If you have run make_branches, then the branches should be showing
> 0.9.4
> > and the develop branch should be using 0.9.5.
> >
> > I already ran and pushed update.versions.  The Ant build should be
> using
> > 0.9.4.
> >
> > I'm stopping work for tonight.
> >
> > HTH,
> > -Alex
> >
> > On 9/17/18, 12:17 AM, "Piotr Zarzycki" 
> wrote:
> >
> > I think I'm right now on steps 4 and 5 in ->
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fwiki%2FRelease-Manager-Notes%23release-steps&data=02%7C01%7Caharui%40adobe.com%7Cb4f3681be8ee401a9edb08d61c7cd8a8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636727719873623282&sdata=4vj7M8%2BYgVfU6EnGXIPz%2BCyd3XxA4kZvCtlly334rww%3D&reserved=0
> >
> >
> > pon., 17 wrz 2018 o 09:16 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >