Re: [royale-asjs] branch develop updated: basic-imagebutton: fix control nesting img inside a button when there is html input image

[Harbs]

Specifically,  will submit a form while  will not.

This is a breaking change to any ImageButton inside a Form.

> On Jul 12, 2020, at 5:28 PM, Harbs  wrote:
> 
> Why did you switch to input?
> 
> IIRC, there are behavioral differences between button and input.
> 
>> On Jul 12, 2020, at 5:12 PM, carlosrov...@apache.org wrote:
>> 
>> This is an automated email from the ASF dual-hosted git repository.
>> 
>> carlosrovira pushed a commit to branch develop
>> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>> 
>> 
>> The following commit(s) were added to refs/heads/develop by this push:
>>new 4377b0b  basic-imagebutton: fix control nesting  img inside a button 
>> when there is html input image
>> 4377b0b is described below
>> 
>> commit 4377b0b3c4e7521d132a3cb72a18bedcc5aacb6a
>> Author: Carlos Rovira 
>> AuthorDate: Sun Jul 12 16:12:20 2020 +0200
>> 
>>   basic-imagebutton: fix control nesting  img inside a button when there is 
>> html input image
>> ---
>> .../main/royale/org/apache/royale/html/ImageButton.as | 19 
>> +++
>> 1 file changed, 11 insertions(+), 8 deletions(-)
>> 
>> diff --git 
>> a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/ImageButton.as
>>  
>> b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/ImageButton.as
>> index 5b3c2d3..407ceb3 100644
>> --- 
>> a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/ImageButton.as
>> +++ 
>> b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/ImageButton.as
>> @@ -60,8 +60,8 @@ package org.apache.royale.html
>>  COMPILE::JS
>>override protected function createElement():WrappedHTMLElement
>>{
>> -addElementToWrapper(this,'button');
>> -element.setAttribute('type', 'button');
>> +addElementToWrapper(this,'input');
>> +element.setAttribute('type', 'image');
>>return element;
>>}
>> 
>> @@ -94,16 +94,19 @@ package org.apache.royale.html
>>{
>>if(!_imageElement)
>>{
>> -_imageElement = document.createElement("img") as 
>> HTMLImageElement;
>> -element.appendChild(_imageElement);
>> -}
>> -(_imageElement as HTMLImageElement).src = url;
>> +(element as HTMLInputElement).src = url;
>> +_imageElement = (element as HTMLInputElement);
>> +}
>> +if (_imageElement && url)
>> +{
>> +(_imageElement as HTMLInputElement).src = url;
>> +}
>>}
>> 
>>  dispatchEvent(new Event("srcChanged"));
>>}
>> 
>> -COMPILE::JS{
>> +COMPILE::JS
>>private var _imageElement:Element;
>>  /**
>>   *  Element image. HTMLImageElement.
>> @@ -115,10 +118,10 @@ package org.apache.royale.html
>> *  @royaleignorecoercion 
>> org.apache.royale.core.IImageButton#imageElement
>> *  @royaleignorecoercion Element
>> */
>> +COMPILE::JS
>>  public function get imageElement():Element
>>  {
>>  return _imageElement;
>>  }
>> -}
>>  }
>> }
>> 
> 

Re: [royale-asjs] branch develop updated: basic-imagebutton: fix control nesting img inside a button when there is html input image

[Harbs]

Why did you switch to input?

IIRC, there are behavioral differences between button and input.

> On Jul 12, 2020, at 5:12 PM, carlosrov...@apache.org wrote:
> 
> This is an automated email from the ASF dual-hosted git repository.
> 
> carlosrovira pushed a commit to branch develop
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> 
> 
> The following commit(s) were added to refs/heads/develop by this push:
> new 4377b0b  basic-imagebutton: fix control nesting  img inside a button 
> when there is html input image
> 4377b0b is described below
> 
> commit 4377b0b3c4e7521d132a3cb72a18bedcc5aacb6a
> Author: Carlos Rovira 
> AuthorDate: Sun Jul 12 16:12:20 2020 +0200
> 
>basic-imagebutton: fix control nesting  img inside a button when there is 
> html input image
> ---
> .../main/royale/org/apache/royale/html/ImageButton.as | 19 +++
> 1 file changed, 11 insertions(+), 8 deletions(-)
> 
> diff --git 
> a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/ImageButton.as
>  
> b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/ImageButton.as
> index 5b3c2d3..407ceb3 100644
> --- 
> a/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/ImageButton.as
> +++ 
> b/frameworks/projects/Basic/src/main/royale/org/apache/royale/html/ImageButton.as
> @@ -60,8 +60,8 @@ package org.apache.royale.html
>   COMPILE::JS
> override protected function createElement():WrappedHTMLElement
> {
> - addElementToWrapper(this,'button');
> -element.setAttribute('type', 'button');
> + addElementToWrapper(this,'input');
> +element.setAttribute('type', 'image');
> return element;
> }
> 
> @@ -94,16 +94,19 @@ package org.apache.royale.html
> {
> if(!_imageElement)
> {
> -_imageElement = document.createElement("img") as 
> HTMLImageElement;
> -element.appendChild(_imageElement);
> -}
> -(_imageElement as HTMLImageElement).src = url;
> +(element as HTMLInputElement).src = url;
> +_imageElement = (element as HTMLInputElement);
> +}
> +if (_imageElement && url)
> +{
> +(_imageElement as HTMLInputElement).src = url;
> +}
> }
> 
>   dispatchEvent(new Event("srcChanged"));
> }
> 
> - COMPILE::JS{
> + COMPILE::JS
> private var _imageElement:Element;
>   /**
>*  Element image. HTMLImageElement.
> @@ -115,10 +118,10 @@ package org.apache.royale.html
>  *  @royaleignorecoercion 
> org.apache.royale.core.IImageButton#imageElement
>  *  @royaleignorecoercion Element
>  */
> +COMPILE::JS
>   public function get imageElement():Element
>   {
>   return _imageElement;
>   }
> -}
>   }
> }
> 

Re: Apache Royale track at ApacheCon 2020

[Carlos Rovira]

Hi Andrew,

I see the topics perfect. Just a question to help me to understand the big
picture. About timing, how much time we have for all sessions (global and
individual)? That seems to me long play and don't know if is the expected.
I can help with points 2 and 4 as you said. If you want to organize a first
set of points I can work over that.
Let me know.

Thanks

El sáb., 11 jul. 2020 a las 16:00, Andrew Wetmore ()
escribió:

> Hi, friends.
>
> We hope to present a track of presentations about Royale at ApacheCon, an
> online event September 29-October 1. I have created a wiki page [1] to work
> out ideas, but since the deadline is coming soon for submitting
> presentations, I wanted to share with you the current plan and get your
> help.
>
> The current plan is to have five presentations:
>
> 1. "Hello Royale" - high-level view of Apache Royale, including a bit of
> history, how it has evolved, its core of AS3 and MXML, what it inherits
> from Flex and how it differs, where it is going, and what you can do with
> it.
>
> 2. "Royale: Starting from a blank file" - focussing on the "todomvc"
> demonstration of creating a to-do list app.
>
> 3. "Moving from Flex to Royale" - how to migrate an existing Flex/Flash
> app to Royale, now that the end of Flash is upon us. Includes emulation,
> component equivalents, work-arounds, and, I hope a couple of examples of
> successful migrations.
>
> 4. "Royale: Tour de Jewel" - A look behind the scenes at the wide range of
> Royale capabilities on display at the Tour de Jewel [2] site.
>
> 5. "Royale masterclass" - How to get the best out of Royale: strands and
> beads, emulation, CSS use, components, other cool things Royale offers.
>
> ApacheCon 2020 is going to have three presentation periods each day to hit
> convenient times around the world. I propose we offer each presentation
> once as a live event, and then rebroadcast it with a presenter who can
> respond in real-time to comments from audiences in the second and third
> tracks. Or we can present each one live three times.
>
> Is this enough? Or does someone have a good idea for a sixth presentation?
> I am going to submit these five today or tomorrow unless I hear a good
> reason not to.
>
> What happens next: A lot of smart folks need to provide wisdom and,
> ideally, be willing to present. If people want to help with writing the
> slides and script for any of these sessions, I can present them. I have a
> lot of experience as a presenter, but need to have the wisdom from the
> whole Royaleiverse to make our presentations clear, accurate, and enticing.
>
> About a thousand people have signed up for ApacheCon 2020 already, even
> before any advertising has gone out, so this is a great opportunity to show
> what Royale offers.
>
> Carlos Rivera has indicated he can help create the material for talks 2
> and 4. Who else can step up and help make our presentations very good?
>
> Andrew
>
>
>
> [1] https://github.com/apache/royale-asjs/wiki/Royale-at-ApacheCon-2020
>
> [2] https://royale.apache.org/tourdejewel/
>
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>


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

Release Step 001 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands:
git push
git checkout release/0.9.8
git push -u origin release/0.9.8

You will need your Apache/Github username and 2FA token.

Royale_Release_Step_002 - Build # 48 - Failure!

[apacheroyaleci]

Royale_Release_Step_002 - Build # 48 - Failure:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/48/
 to view the results.

Re: Royale_Release_Step_002 - Build # 50 - Still Failing!

[Harbs]

I’m not sure what’s supposed to be happening here. I thought that as part of 
step 1, the release/0.9.8 branch gets the poms sans the -SNAPSHOT, but they 
still say 0.9.8-SNAPSHOT

I tried removing -SNAPSHOT manually, but that didn’t help either.

With -SNAPSHOT, I get an error: 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) on 
project royale-compiler-parent: Can't release project due to non released 
dependencies :
[ERROR] 
org.apache.royale.compiler:compiler-build-tools:maven-plugin:1.2.1-SNAPSHOT:runtime
[ERROR] in project 'Apache Royale: Compiler: Externc' 
(org.apache.royale.compiler:compiler-externc:jar:0.9.8-SNAPSHOT)


Without the -SNAPSHOT, I get an error:
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) on 
project royale-compiler-parent: You don't have a SNAPSHOT project in the 
reactor projects list. -> [Help 1]
Maven is black magic to me… ;-)

Any pointers?

Harbs

> On Jul 12, 2020, at 10:34 PM, apacheroyal...@gmail.com wrote:
> 
> Royale_Release_Step_002 - Build # 50 - Still Failing:
> 
> Check console output at 
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/50/
>  to view the results.

Royale_Release_Step_002 - Build # 49 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_002 - Build # 49 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/49/
 to view the results.

Royale_Release_Step_002 - Build # 50 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_002 - Build # 50 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/50/
 to view the results.

Re: Royale_Release_Step_002 - Build # 50 - Still Failing!

[Harbs]

Or in other words, how does maven-release-plugin work?

> On Jul 12, 2020, at 10:46 PM, Harbs  wrote:
> 
> I’m not sure what’s supposed to be happening here. I thought that as part of 
> step 1, the release/0.9.8 branch gets the poms sans the -SNAPSHOT, but they 
> still say 0.9.8-SNAPSHOT
> 
> I tried removing -SNAPSHOT manually, but that didn’t help either.
> 
> With -SNAPSHOT, I get an error: 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) 
> on project royale-compiler-parent: Can't release project due to non released 
> dependencies :
> [ERROR] 
> org.apache.royale.compiler:compiler-build-tools:maven-plugin:1.2.1-SNAPSHOT:runtime
> [ERROR] in project 'Apache Royale: Compiler: Externc' 
> (org.apache.royale.compiler:compiler-externc:jar:0.9.8-SNAPSHOT)
> 
> 
> Without the -SNAPSHOT, I get an error:
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) 
> on project royale-compiler-parent: You don't have a SNAPSHOT project in the 
> reactor projects list. -> [Help 1]
> Maven is black magic to me… ;-)
> 
> Any pointers?
> 
> Harbs
> 
>> On Jul 12, 2020, at 10:34 PM, apacheroyal...@gmail.com wrote:
>> 
>> Royale_Release_Step_002 - Build # 50 - Still Failing:
>> 
>> Check console output at 
>> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_002/50/
>>  to view the results.
> 

Re: Apache Royale track at ApacheCon 2020

[Andrew Wetmore]

Any thoughts on a short, evocative title for the track? How about "Apache
Royale: Application Builder"?

On Sun, Jul 12, 2020 at 7:28 AM Carlos Rovira 
wrote:

> Hi Andrew,
>
> I see the topics perfect. Just a question to help me to understand the big
> picture. About timing, how much time we have for all sessions (global and
> individual)? That seems to me long play and don't know if is the expected.
> I can help with points 2 and 4 as you said. If you want to organize a
> first set of points I can work over that.
> Let me know.
>
> Thanks
>
> El sáb., 11 jul. 2020 a las 16:00, Andrew Wetmore ()
> escribió:
>
>> Hi, friends.
>>
>> We hope to present a track of presentations about Royale at ApacheCon, an
>> online event September 29-October 1. I have created a wiki page [1] to work
>> out ideas, but since the deadline is coming soon for submitting
>> presentations, I wanted to share with you the current plan and get your
>> help.
>>
>> The current plan is to have five presentations:
>>
>> 1. "Hello Royale" - high-level view of Apache Royale, including a bit of
>> history, how it has evolved, its core of AS3 and MXML, what it inherits
>> from Flex and how it differs, where it is going, and what you can do with
>> it.
>>
>> 2. "Royale: Starting from a blank file" - focussing on the "todomvc"
>> demonstration of creating a to-do list app.
>>
>> 3. "Moving from Flex to Royale" - how to migrate an existing Flex/Flash
>> app to Royale, now that the end of Flash is upon us. Includes emulation,
>> component equivalents, work-arounds, and, I hope a couple of examples of
>> successful migrations.
>>
>> 4. "Royale: Tour de Jewel" - A look behind the scenes at the wide range
>> of Royale capabilities on display at the Tour de Jewel [2] site.
>>
>> 5. "Royale masterclass" - How to get the best out of Royale: strands and
>> beads, emulation, CSS use, components, other cool things Royale offers.
>>
>> ApacheCon 2020 is going to have three presentation periods each day to
>> hit convenient times around the world. I propose we offer each presentation
>> once as a live event, and then rebroadcast it with a presenter who can
>> respond in real-time to comments from audiences in the second and third
>> tracks. Or we can present each one live three times.
>>
>> Is this enough? Or does someone have a good idea for a sixth
>> presentation? I am going to submit these five today or tomorrow unless I
>> hear a good reason not to.
>>
>> What happens next: A lot of smart folks need to provide wisdom and,
>> ideally, be willing to present. If people want to help with writing the
>> slides and script for any of these sessions, I can present them. I have a
>> lot of experience as a presenter, but need to have the wisdom from the
>> whole Royaleiverse to make our presentations clear, accurate, and enticing.
>>
>> About a thousand people have signed up for ApacheCon 2020 already, even
>> before any advertising has gone out, so this is a great opportunity to show
>> what Royale offers.
>>
>> Carlos Rivera has indicated he can help create the material for talks 2
>> and 4. Who else can step up and help make our presentations very good?
>>
>> Andrew
>>
>>
>>
>> [1] https://github.com/apache/royale-asjs/wiki/Royale-at-ApacheCon-2020
>>
>> [2] https://royale.apache.org/tourdejewel/
>>
>>
>>
>> --
>> Andrew Wetmore
>> Technical Writer-Editor
>> Infra
>> *Apache Software Foundation*
>> andr...@apache.org
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: BindingUtils.bindProperty - Issue or I'm doing something wrong ?

[Hugo Ferreira]

Even BindingUtils didn't show off, RemoteObject from mx seems to be there.
The second option is enough.

"We hopefully will separate MX in libraries and will create a "jewel" config
that adds RPC and maybe others that could be needed."
That would be great.

Carlos Rovira  escreveu no dia sexta, 10/07/2020
à(s) 11:20:

> I'm not an expert on asconfic, but I remember I solved it maintaining
> "royale" as config and adding this:
>
> "library-path": [
> "${royalelib}/js/libs/MXRoyaleJS.swc"
> ],
> "js-library-path": [
> "${royalelib}/js/libs/MXRoyaleJS.swc"
> ],
>
> I think maybe just the second was enough...
>
> We hopefully will separate MX in libraries and will create a "jewel" config
> that adds RPC and maybe others that could be needed.
>
> Also remember to remove mx css adding this to additional compiler options:
>
>
> -compiler.exclude-defaults-css-files=MXRoyale-${royale.framework.version}-js.swc:defaults.css;
>
>
>
> El vie., 10 jul. 2020 a las 11:23, Hugo Ferreira ( >)
> escribió:
>
> > Hello,
> >
> > That's a good idea, because I want to avoid MX UI as much as possible,
> > since I decided for Royale, so Royale it is.
> > However I don't see so many problems for non-UI stuff.
> > My issue is that to work with MX, I saw that I need to change my
> > asconfig.json from "config": "royale" to "config": "flex" (ps: I'm using
> > Visual Studio Code) and then I got all sort of namespace conflicts
> between
> > MX and Royale.For what you said, I believe that's a better way to mix MX
> > and Royale without changing so dramatically config file.
> >
> > Carlos Rovira  escreveu no dia sexta,
> 10/07/2020
> > à(s) 09:32:
> >
> > > Hi Hugo,
> > > you can use MXRoyale in "Royale only" (i.e: jewel) apps.
> > > You must to be careful, but code like RPC classes, validators, and
> > probably
> > > BindingUtils can be used.
> > > I think while you don't use "visual" things, that should be ok. It
> maybe
> > > would require you to try it, but at least RPC classes are working for
> > many
> > > others and I used as well some validators time ago.
> > >
> > > El vie., 10 jul. 2020 a las 0:39, Hugo Ferreira (<
> hferreira...@gmail.com
> > >)
> > > escribió:
> > >
> > > > OK.
> > > > I'm using Royale only, so BindingUtils (mx version) is not available
> in
> > > my
> > > > case.
> > > > I will try to workaround in a different way (for sure I have to write
> > > more
> > > > code) but yes, BindingUtils is a short way in a single line to do the
> > > > things (it will be a missing feature).
> > > >
> > > > Greg Dove  escreveu no dia quinta, 9/07/2020
> à(s)
> > > > 23:34:
> > > >
> > > > > When I originally wrote that, it was not intended to be used
> directly
> > > in
> > > > > code, it was intended to support the metadata-driven injected
> > bindings,
> > > > > specifically with Crux. It is quite specific for Crux.
> > > > > It does need BindableChainInfo instances in that last argument
> > instead
> > > of
> > > > > strings. Perhaps the code can be adapted to be more useful other
> than
> > > > with
> > > > > Crux, but would need some time and effort focused on that.
> > > > > Is it not viable to use injection in your case?
> > > > >
> > > > > Since I worked on that, I did also do some work in the mx.binding
> > > inside
> > > > > MXRoyale. Maybe the BindingUtils in there is more like what you
> want?
> > > (It
> > > > > is closer to the original Flex)
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Fri, Jul 10, 2020 at 10:02 AM Hugo Ferreira <
> > hferreira...@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > The following line of code, compiles without any issue:
> > > > > > BindingUtils.bindProperty(header, "minimized", content,
> > ["visible"]);
> > > > > >
> > > > > > However at runtime, I got the following error on Google Chrome
> > > Console:
> > > > > > Uncaught TypeError: Error #1034: Type Coercion failed: cannot
> > convert
> > > > > > visible to org.apache.royale.crux.binding.BindableChainInfo
> > > > > > at Function.org.apache.royale.utils.Language.as
> > > (Language.js:115)
> > > > > > at
> > > > Function.org.apache.royale.crux.binding.BindingUtils.bindProperty
> > > > > > (BindingUtils.js:73)
> > > > > > at
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> pt.solidsoft.gc.view.login.Login.pt.solidsoft.framework.form.Form.addElement
> > > > > > (Form.mxml:32)
> > > > > > at
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> Function.org.apache.royale.utils.MXMLDataInterpreter.initializeStrandBasedObject
> > > > > > (MXMLDataInterpreter.js:241)
> > > > > > at
> > > > > >
> > > Function.org.apache.royale.utils.MXMLDataInterpreter.generateMXMLArray
> > > > > > (MXMLDataInterpreter.js:127)
> > > > > > at
> > > > > >
> > > > >
> > > >
> > >
> >
> Function.org.apache.royale.utils.MXMLDataInterpreter.generateMXMLInstances
> > > > > > (MXMLDataInterpreter.js:271)
> > > > > > at
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> 

Re: Royale_Release_Step_002 - Build # 50 - Still Failing!

[Alex Harui]

You will have to release compiler-build-tools 1.2.1 first.  A change was made 
there to help with reproducible binaries.  Yishay had to release 
compiler-build-tools before 0.9.7.

HTH,
-Alex

On 7/12/20, 12:47 PM, "Harbs"  wrote:

Or in other words, how does maven-release-plugin work?

> On Jul 12, 2020, at 10:46 PM, Harbs  wrote:
> 
> I’m not sure what’s supposed to be happening here. I thought that as part 
of step 1, the release/0.9.8 branch gets the poms sans the -SNAPSHOT, but they 
still say 0.9.8-SNAPSHOT
> 
> I tried removing -SNAPSHOT manually, but that didn’t help either.
> 
> With -SNAPSHOT, I get an error: 
> 
> [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) on 
project royale-compiler-parent: Can't release project due to non released 
dependencies :
> [ERROR] 
org.apache.royale.compiler:compiler-build-tools:maven-plugin:1.2.1-SNAPSHOT:runtime
> [ERROR] in project 'Apache Royale: Compiler: Externc' 
(org.apache.royale.compiler:compiler-externc:jar:0.9.8-SNAPSHOT)
> 
> 
> Without the -SNAPSHOT, I get an error:
> [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) on 
project royale-compiler-parent: You don't have a SNAPSHOT project in the 
reactor projects list. -> [Help 1]
> Maven is black magic to me… ;-)
> 
> Any pointers?
> 
> Harbs
> 
>> On Jul 12, 2020, at 10:34 PM, apacheroyal...@gmail.com wrote:
>> 
>> Royale_Release_Step_002 - Build # 50 - Still Failing:
>> 
>> Check console output at 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Release_Step_002%2F50%2Fdata=02%7C01%7Caharui%40adobe.com%7C734e8269717944eaea3e08d8269c6218%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637301800387377637sdata=Gxu%2FDu0YVBhNB2cvkIPqa3jGJdom4UnMs%2F8m3zovF8I%3Dreserved=0
 to view the results.
> 

Re: Royale_Release_Step_002 - Build # 50 - Still Failing!

[Harbs]

Oh. Thanks. I’ll do that then...

> On Jul 13, 2020, at 7:22 AM, Alex Harui  wrote:
> 
> You will have to release compiler-build-tools 1.2.1 first.  A change was made 
> there to help with reproducible binaries.  Yishay had to release 
> compiler-build-tools before 0.9.7.
> 
> HTH,
> -Alex
> 
> On 7/12/20, 12:47 PM, "Harbs"  > wrote:
> 
>Or in other words, how does maven-release-plugin work?
> 
>> On Jul 12, 2020, at 10:46 PM, Harbs  wrote:
>> 
>> I’m not sure what’s supposed to be happening here. I thought that as part of 
>> step 1, the release/0.9.8 branch gets the poms sans the -SNAPSHOT, but they 
>> still say 0.9.8-SNAPSHOT
>> 
>> I tried removing -SNAPSHOT manually, but that didn’t help either.
>> 
>> With -SNAPSHOT, I get an error: 
>> 
>> [ERROR] Failed to execute goal 
>> org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) 
>> on project royale-compiler-parent: Can't release project due to non released 
>> dependencies :
>> [ERROR] 
>> org.apache.royale.compiler:compiler-build-tools:maven-plugin:1.2.1-SNAPSHOT:runtime
>> [ERROR] in project 'Apache Royale: Compiler: Externc' 
>> (org.apache.royale.compiler:compiler-externc:jar:0.9.8-SNAPSHOT)
>> 
>> 
>> Without the -SNAPSHOT, I get an error:
>> [ERROR] Failed to execute goal 
>> org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) 
>> on project royale-compiler-parent: You don't have a SNAPSHOT project in the 
>> reactor projects list. -> [Help 1]
>> Maven is black magic to me… ;-)
>> 
>> Any pointers?
>> 
>> Harbs
>> 
>>> On Jul 12, 2020, at 10:34 PM, apacheroyal...@gmail.com wrote:
>>> 
>>> Royale_Release_Step_002 - Build # 50 - Still Failing:
>>> 
>>> Check console output at 
>>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FRoyale_Release_Step_002%2F50%2Fdata=02%7C01%7Caharui%40adobe.com%7C734e8269717944eaea3e08d8269c6218%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637301800387377637sdata=Gxu%2FDu0YVBhNB2cvkIPqa3jGJdom4UnMs%2F8m3zovF8I%3Dreserved=0
>>>  
>>> 
>>>  to view the results.

Royale Compiler Build Tools Release Step 001 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Compiler_Build_Tools_Release_Step_001 and run the 
following commands:
git push --set-upstream origin develop
git push origin org.apache.royale.compiler-build-tools-1.2.1-rc1

You will need your Apache/Github username and 2FA token.