Re: Prioritize Release Jobs on CI

[Alex Harui]

Yes, royale-asjs (which is currently building on agent1 and blocking the 
release job).

-Alex

On 4/20/20, 10:53 PM, "OmPrakash Muppirala"  wrote:

Update - royale-asjs_jsonly successfully build on my agent VM.

Right now, we have 3 jobs running on this VM:
1. royale-asjs_jsonly
2. royale-compiler
3. royale-typedefs

Are there any other jobs we need to move to the new agent?

Yishay, can you please confirm that your release jobs are running without
being hindered by CI jobs?

Thanks,
Om

On Mon, Apr 20, 2020 at 12:05 AM OmPrakash Muppirala 
wrote:

>
> On Mon, Apr 20, 2020 at 12:01 AM Alex Harui 
> wrote:
>
>> I see compiler-jx/lib in the Workspace for royale-compiler on my VM.  If
>> you are talking about your VM, you can compare console output from recent
>> successful builds on both VMs.
>>
>>
> I was talking about my VM.
> A rebuild of royale-compiler seems to have fixed that problem.  Now
> royale-typedefs passes as well!
>
> Next up royale-asjs_jsonly...
>
>
>> I'm done for tonight.  Good luck,
>> -Alex
>>
>> On 4/19/20, 11:50 PM, "OmPrakash Muppirala" 
>> wrote:
>>
>> On Sun, Apr 19, 2020 at 11:37 PM Alex Harui > >
>> wrote:
>>
>> > Royale-compiler has to be built first.  This is an example of 
shared
>> > resources that I mentioned upthread.  Royale-typedefs is going to
>> look for
>> > a sibling workspace folder called royale-compiler with a built of
>> > royale-compiler in it.  If royale-compiler fails to create all of
>> its
>> > binaries or is in the process of building them, royale-typedefs
>> will report
>> > an error.
>> >
>>
>> Got it.  I was just looking at the logic here:
>>
>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-typedefs%2Fblob%2F85c74dde104294a0127ce46a8795d7534216e7eb%2Fjs%2Fbuild.xml%23L53data=02%7C01%7Caharui%40adobe.com%7C4ef14652baf546d77e8908d7e5b85c0b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637230452301088702sdata=cejYyk7K6vlgMF0Y7lX%2FCvIIPUU1f74AmDiMqI7gTMg%3Dreserved=0
>>
>> Weird.  The royale-compiler build says it was successful, but I cant
>> find
>> the lib directory under
>> C:\jenkins\workspace\royale-compiler\compiler-jx
>>
>>
>>
>>
>> >
>> > What should probably happen is that royale-typedefs pulls down the
>> > lastsuccessfulartifacts from royale-compiler, but I've never found
>> enough
>> > time and energy to try to make changes like that since most of us
>> do have
>> > all of the folders as siblings.
>> >
>> > HTH,
>> > -Alex
>> >
>> > On 4/19/20, 11:31 PM, "OmPrakash Muppirala" 
>> wrote:
>> >
>> > I am now getting this error on royale-typedefs build:
>> >
>> > BUILD FAILEDc:\jenkins\workspace\royale-typedefs\build.xml:58:
>> The
>> > following error occurred while executing this line:
>> > c:\jenkins\workspace\royale-typedefs\js\build.xml:91: src
>> >
>> >
>> 
'c:\jenkins\workspace\royale-typedefs\js\${ROYALE_TRANSPILER_HOME}\lib\google\closure-compiler\compiler.jar'
>> > doesn't exist.
>> >
>> >
>> > Where does the ROYALE_TRANSPILER_HOME var come from?
>> >
>> > Here is the full console output:
>> >
>> >
>> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fview%2FAgent%25202%2520data=02%7C01%7Caharui%40adobe.com%7C4ef14652baf546d77e8908d7e5b85c0b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637230452301098700sdata=AlDWUpxRr7ZWXevbiDrlfG9DlTCHJ2uVWi8hcx3%2BbBE%3Dreserved=0(Om's%20VM)/job/royale-typedefs/552/console
>> >
>> > On Sun, Apr 19, 2020 at 11:24 PM OmPrakash Muppirala <
>> > bigosma...@gmail.com>
>> > wrote:
>> >
>> > > On Sun, Apr 19, 2020 at 11:08 PM Alex Harui
>> > > >
>> > > wrote:
>> > >
>> > >> Congratulations!  But does that mean that JAVA_HOME is
>> pointing at
>> > a JRE
>> > >> instead of a JDK?  If you have other issues that might be a
>> factor.
>> > >>
>> > >
>> > > Yeah, I messed up initially by getting the JRE instead of
>> JDK.  I
>> > have
>> > > since corrected it.  But for some reason Ant still thinks 
that
>> > JAVA_HOME is
>> > > the jre directory.
>> > > I don't know how to fix this, hence the hack :-|
>> > >
>> > >
>> > >
>> > >
>> > >>
>> > >> 

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

Update - royale-asjs_jsonly successfully build on my agent VM.

Right now, we have 3 jobs running on this VM:
1. royale-asjs_jsonly
2. royale-compiler
3. royale-typedefs

Are there any other jobs we need to move to the new agent?

Yishay, can you please confirm that your release jobs are running without
being hindered by CI jobs?

Thanks,
Om

On Mon, Apr 20, 2020 at 12:05 AM OmPrakash Muppirala 
wrote:

>
> On Mon, Apr 20, 2020 at 12:01 AM Alex Harui 
> wrote:
>
>> I see compiler-jx/lib in the Workspace for royale-compiler on my VM.  If
>> you are talking about your VM, you can compare console output from recent
>> successful builds on both VMs.
>>
>>
> I was talking about my VM.
> A rebuild of royale-compiler seems to have fixed that problem.  Now
> royale-typedefs passes as well!
>
> Next up royale-asjs_jsonly...
>
>
>> I'm done for tonight.  Good luck,
>> -Alex
>>
>> On 4/19/20, 11:50 PM, "OmPrakash Muppirala" 
>> wrote:
>>
>> On Sun, Apr 19, 2020 at 11:37 PM Alex Harui > >
>> wrote:
>>
>> > Royale-compiler has to be built first.  This is an example of shared
>> > resources that I mentioned upthread.  Royale-typedefs is going to
>> look for
>> > a sibling workspace folder called royale-compiler with a built of
>> > royale-compiler in it.  If royale-compiler fails to create all of
>> its
>> > binaries or is in the process of building them, royale-typedefs
>> will report
>> > an error.
>> >
>>
>> Got it.  I was just looking at the logic here:
>>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-typedefs%2Fblob%2F85c74dde104294a0127ce46a8795d7534216e7eb%2Fjs%2Fbuild.xml%23L53data=02%7C01%7Caharui%40adobe.com%7C10c9e091b8054ef206df08d7e4f70e1a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229622064138237sdata=WjJhmdD0PeHDCYfqg%2Bf4mofhnQHdEPnwwj2ti%2FqlmII%3Dreserved=0
>>
>> Weird.  The royale-compiler build says it was successful, but I cant
>> find
>> the lib directory under
>> C:\jenkins\workspace\royale-compiler\compiler-jx
>>
>>
>>
>>
>> >
>> > What should probably happen is that royale-typedefs pulls down the
>> > lastsuccessfulartifacts from royale-compiler, but I've never found
>> enough
>> > time and energy to try to make changes like that since most of us
>> do have
>> > all of the folders as siblings.
>> >
>> > HTH,
>> > -Alex
>> >
>> > On 4/19/20, 11:31 PM, "OmPrakash Muppirala" 
>> wrote:
>> >
>> > I am now getting this error on royale-typedefs build:
>> >
>> > BUILD FAILEDc:\jenkins\workspace\royale-typedefs\build.xml:58:
>> The
>> > following error occurred while executing this line:
>> > c:\jenkins\workspace\royale-typedefs\js\build.xml:91: src
>> >
>> >
>> 'c:\jenkins\workspace\royale-typedefs\js\${ROYALE_TRANSPILER_HOME}\lib\google\closure-compiler\compiler.jar'
>> > doesn't exist.
>> >
>> >
>> > Where does the ROYALE_TRANSPILER_HOME var come from?
>> >
>> > Here is the full console output:
>> >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fview%2FAgent%25202%2520data=02%7C01%7Caharui%40adobe.com%7C10c9e091b8054ef206df08d7e4f70e1a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229622064148235sdata=Rl%2F6kGkOf3Z2pauOtISD6aoqJ23M05iKMMxUV0eweuc%3Dreserved=0(Om's%20VM)/job/royale-typedefs/552/console
>> >
>> > On Sun, Apr 19, 2020 at 11:24 PM OmPrakash Muppirala <
>> > bigosma...@gmail.com>
>> > wrote:
>> >
>> > > On Sun, Apr 19, 2020 at 11:08 PM Alex Harui
>> > > >
>> > > wrote:
>> > >
>> > >> Congratulations!  But does that mean that JAVA_HOME is
>> pointing at
>> > a JRE
>> > >> instead of a JDK?  If you have other issues that might be a
>> factor.
>> > >>
>> > >
>> > > Yeah, I messed up initially by getting the JRE instead of
>> JDK.  I
>> > have
>> > > since corrected it.  But for some reason Ant still thinks that
>> > JAVA_HOME is
>> > > the jre directory.
>> > > I don't know how to fix this, hence the hack :-|
>> > >
>> > >
>> > >
>> > >
>> > >>
>> > >> HTH,
>> > >> -Alex
>> > >>
>> > >> On 4/19/20, 10:50 PM, "OmPrakash Muppirala" <
>> bigosma...@gmail.com>
>> > >> wrote:
>> > >>
>> > >> I copied tools.jar from  jdk/lib to the jre/lib.  That
>> seems to
>> > have
>> > >> fixed
>> > >> the issue.
>> > >> We now have a successful build of the royale-compiler on
>> the
>> > new Agent
>> > >> machine!!
>> > >>
>> > >> On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala <
>> > >> bigosma...@gmail.com>
>> > >> wrote:
>> > >>
>> > >> > Restart dint 

Release Step 010 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands:
git push
git push origin org.apache.royale.framework-0.9.7-rc2

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

Jenkins build is back to normal : royale-asjs_jsonly #1340

[apacheroyaleci]

See 

Build failed in Jenkins: royale-asjs_jsonly #1339

[apacheroyaleci]

See 


Changes:


--
[...truncated 1.71 MB...]

check-air-home:

check-compiler-home:

check-compile-env:
 [echo] OS: Windows Server 2016 / 10.0 / amd64
 [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.251-b08
 [echo] Java: 1.8.0_251
 [echo] Ant: Apache Ant(TM) version 1.9.9 compiled on February 2 2017 Ant 
Java Version: 1.8

prepare:

compile:

flat-ui-icons:
 [java] Error: Unable to access jarfile 

 [java] Java Result: 1

main:

main:

tweak-for-jsonly:
 [copy] Copying 1 file to 

 [copy] Copying 1 file to 


check-royale-config:

fixup-royale-config:

ide:

post-build:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

 [copy] Copying 1 file to 

 [copy] Copying 1 file to 

[touch] Creating 

[touch] Creating 

[touch] Creating 


last-message-if-airsdk:

main:
 [echo] ant main target completed on 04/21/2020 04:16:43 AM

sample-themes:

check-runtime-env:

runtime-setup:

mustella-setup:

load-task:

marmotinni-setup:

prepare:
 [echo] Making lib directory 
:\jenkins\workspace\royale-asjs_jsonly\marmotinni\java/lib
[mkdir] Created dir: 


selenium3-jar-check:

selenium3-jar:
[mkdir] Created dir: 


download-zip:
[mkdir] Created dir: 

  [get] Getting: https://bit.ly/2zm3ZzF
  [get] To: 

  [get] https://bit.ly/2zm3ZzF permanently moved to 
https://selenium-release.storage.googleapis.com/3.141/selenium-java-3.141.59.zip

untar-file:

unzip-file:
[unzip] Expanding: 

 into 


check-sum:

copy-downloaded-jar:
  [get] Getting: http://www.apache.org/licenses/LICENSE-2.0
  [get] To: 

 [copy] Copying 10 files to 


clean:

main:

clean:
   [delete] Deleting: 


check-compiler-home:

check-compiler:

compile:

compile-js:
 [echo] Compiling mustella.swc
 [echo] ROYALE_HOME: 

 [echo] ROYALE_COMPILER_HOME: 

 [java] args:
 [java] 
+royalelib=
 [java] +playerglobal.version=11.7
 [java] +env.PLAYERGLOBAL_HOME=${env.PLAYERGLOBAL_HOME}
 [java] -compiler.strict-xml=true
 [java] -compiler.targets=SWF,JSRoyale
 [java] 

Build failed in Jenkins: royale-asjs_jsonly #1338

[apacheroyaleci]

See 


Changes:


--
[...truncated 1.71 MB...]

check-air-home:

check-compiler-home:

check-compile-env:
 [echo] OS: Windows Server 2016 / 10.0 / amd64
 [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.251-b08
 [echo] Java: 1.8.0_251
 [echo] Ant: Apache Ant(TM) version 1.9.9 compiled on February 2 2017 Ant 
Java Version: 1.8

prepare:

compile:

flat-ui-icons:
 [java] Error: Unable to access jarfile 

 [java] Java Result: 1

main:

main:

tweak-for-jsonly:
 [copy] Copying 1 file to 

 [copy] Copying 1 file to 


check-royale-config:

fixup-royale-config:

ide:

post-build:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

 [copy] Copying 1 file to 

 [copy] Copying 1 file to 

[touch] Creating 

[touch] Creating 

[touch] Creating 


last-message-if-airsdk:

main:
 [echo] ant main target completed on 04/21/2020 02:52:25 AM

sample-themes:

check-runtime-env:

runtime-setup:

mustella-setup:

load-task:

marmotinni-setup:

prepare:
 [echo] Making lib directory 
:\jenkins\workspace\royale-asjs_jsonly\marmotinni\java/lib
[mkdir] Created dir: 


selenium3-jar-check:

selenium3-jar:
[mkdir] Created dir: 


download-zip:
[mkdir] Created dir: 

  [get] Getting: https://bit.ly/2zm3ZzF
  [get] To: 

  [get] https://bit.ly/2zm3ZzF permanently moved to 
https://selenium-release.storage.googleapis.com/3.141/selenium-java-3.141.59.zip

untar-file:

unzip-file:
[unzip] Expanding: 

 into 


check-sum:

copy-downloaded-jar:
  [get] Getting: http://www.apache.org/licenses/LICENSE-2.0
  [get] To: 

 [copy] Copying 10 files to 


clean:

main:

clean:
   [delete] Deleting: 


check-compiler-home:

check-compiler:

compile:

compile-js:
 [echo] Compiling mustella.swc
 [echo] ROYALE_HOME: 

 [echo] ROYALE_COMPILER_HOME: 

 [java] args:
 [java] 
+royalelib=
 [java] +playerglobal.version=11.7
 [java] +env.PLAYERGLOBAL_HOME=${env.PLAYERGLOBAL_HOME}
 [java] -compiler.strict-xml=true
 [java] -compiler.targets=SWF,JSRoyale
 [java] 

Build failed in Jenkins: royale-asjs_jsonly #1337

[apacheroyaleci]

See 


Changes:

[carlosrovira] jewel-listview: some little improvements


--
[...truncated 1.71 MB...]

check-air-home:

check-compiler-home:

check-compile-env:
 [echo] OS: Windows Server 2016 / 10.0 / amd64
 [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.251-b08
 [echo] Java: 1.8.0_251
 [echo] Ant: Apache Ant(TM) version 1.9.9 compiled on February 2 2017 Ant 
Java Version: 1.8

prepare:

compile:

flat-ui-icons:
 [java] Error: Unable to access jarfile 

 [java] Java Result: 1

main:

main:

tweak-for-jsonly:
 [copy] Copying 1 file to 

 [copy] Copying 1 file to 


check-royale-config:

fixup-royale-config:

ide:

post-build:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

 [copy] Copying 1 file to 

 [copy] Copying 1 file to 

[touch] Creating 

[touch] Creating 

[touch] Creating 


last-message-if-airsdk:

main:
 [echo] ant main target completed on 04/20/2020 10:53:05 PM

sample-themes:

check-runtime-env:

runtime-setup:

mustella-setup:

load-task:

marmotinni-setup:

prepare:
 [echo] Making lib directory 
:\jenkins\workspace\royale-asjs_jsonly\marmotinni\java/lib
[mkdir] Created dir: 


selenium3-jar-check:

selenium3-jar:
[mkdir] Created dir: 


download-zip:
[mkdir] Created dir: 

  [get] Getting: https://bit.ly/2zm3ZzF
  [get] To: 

  [get] https://bit.ly/2zm3ZzF permanently moved to 
https://selenium-release.storage.googleapis.com/3.141/selenium-java-3.141.59.zip

untar-file:

unzip-file:
[unzip] Expanding: 

 into 


check-sum:

copy-downloaded-jar:
  [get] Getting: http://www.apache.org/licenses/LICENSE-2.0
  [get] To: 

 [copy] Copying 10 files to 


clean:

main:

clean:
   [delete] Deleting: 


check-compiler-home:

check-compiler:

compile:

compile-js:
 [echo] Compiling mustella.swc
 [echo] ROYALE_HOME: 

 [echo] ROYALE_COMPILER_HOME: 

 [java] args:
 [java] 
+royalelib=
 [java] +playerglobal.version=11.7
 [java] +env.PLAYERGLOBAL_HOME=${env.PLAYERGLOBAL_HOME}
 [java] -compiler.strict-xml=true
 [java] -compiler.targets=SWF,JSRoyale
 [java] 

Re: Separate mailing list for Jenkins notifications

[Alex Harui]

I already asked.  See: INFRA-15722


On 4/20/20, 2:45 PM, "Piotr Zarzycki"  wrote:

To me argument of having info that server failed vs have cleaned inbox
finally - I'm choosing to have inbox cleaned.

If Apache rejected email from Jenkins on commits@ I can ask infra what can
be done.

On Mon, Apr 20, 2020, 10:43 PM Alex Harui  wrote:

> I've been unable to get the CI server to send to commits@.  Apache blocks
> it.
>
> Maybe issues@, but these aren't about issues.
>
> IMO, the point of these Jenkins emails is so that all committers know the
> current state of the builds and help fix issues when possible.  My concern
> is that when committers start filtering CI emails they will miss when one
> of their commits breaks the build.  So, the only reason to split CI emails
> off this list is to reduce traffic to the non-committers.
>
> My 2 cents,
> -Alex
>
> On 4/20/20, 1:17 PM, "OmPrakash Muppirala"  wrote:
>
> We already have issues@ and commits@.  Can we redirect the emails to
> one of
> the lists?
>
> On Mon, Apr 20, 2020 at 11:54 AM Alex Harui 
> wrote:
>
> > IMO, if we do create a new list, all committers must be subscribed.
> >
> > My 2 cents,
> > -Alex
> >
> > On 4/20/20, 1:53 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Hi Guys,
> >
> > In the last year or so all notifications from Jenkins build are
> going
> > to
> > development mailing list. It becomes very messy I see every day
> 40-50
> > emails where 80% of that is notification from Jenkins.
> >
> > I would like to propose create separate mailing list to have 
such
> > notifications there.
> >
> > Is it possible?
> >
> > Please share your thoughts on that subject.
> >
> > Thanks,
> > --
> >
> > Piotr Zarzycki
> >
> >
> >
>
>
>

Re: Some of the Clipboard class method is not visible in Maven distribution build

[Josh Tynjala]

I'm guessing that org.apache.royale.textLayout.edit.Clipboard is missing,
for some reason. In that case, it would fall back to the global Clipboard,
since that class doesn't need to be imported.

As for why it is missing, I would guess that it's one of these two possible
reasons...

1) You forgot to add the SWC that contains
org.apache.royale.textLayout.edit.Clipboard to your pom.xml
2) You have the correct SWC, but for some reason, it compiled without
including org.apache.royale.textLayout.edit.Clipboard.


--
Josh Tynjala
Bowler Hat LLC 


On Mon, Apr 20, 2020 at 3:13 PM Piotr Zarzycki 
wrote:

> Ok but why it has happened? I will check tomorrow if I have correct import,
> but I think I have.
> Why it is working with SDK from Jenkins, but doesn't with Maven
> distribution
>
> On Mon, Apr 20, 2020, 6:07 PM Josh Tynjala 
> wrote:
>
> > I think that you are trying to use the wrong Clipboard class. It looks
> like
> > you're using the JS global Clipboard, rather than
> > org.apache.royale.textLayout.edit.Clipboard.
> >
> > org.apache.royale.textLayout.edit.Clipboard doesn't have writeText() and
> > readText() methods.
> >
> > https://developer.mozilla.org/en-US/docs/Web/API/Clipboard
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Mon, Apr 20, 2020 at 8:13 AM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > I build SDK using distribution option by Maven. When I have tried build
> > > application using distribution I'm getting following error:
> > >
> > > Error: Access of possibly undefined property generalClipboard through a
> > > reference with static type Clipboard.
> > >
> > > It looks like this method [1] wasn't generated in distribution output.
> > When
> > > I look into class signature in SWC I see following only [2]
> > >
> > > [1]
> > >
> > >
> >
> https://github.com/apache/royale-asjs/blob/bdaa1b0bc5f54423aac7bafda363f512236977a1/frameworks/projects/TLF/src/main/royale/org/apache/royale/textLayout/edit/Clipboard.as#L156
> > > [2] https://ibb.co/GWdj86b
> > >
> > > Thanks,
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > *
> > >
> >
>

Re: Some of the Clipboard class method is not visible in Maven distribution build

[Piotr Zarzycki]

Ok but why it has happened? I will check tomorrow if I have correct import,
but I think I have.
Why it is working with SDK from Jenkins, but doesn't with Maven
distribution

On Mon, Apr 20, 2020, 6:07 PM Josh Tynjala 
wrote:

> I think that you are trying to use the wrong Clipboard class. It looks like
> you're using the JS global Clipboard, rather than
> org.apache.royale.textLayout.edit.Clipboard.
>
> org.apache.royale.textLayout.edit.Clipboard doesn't have writeText() and
> readText() methods.
>
> https://developer.mozilla.org/en-US/docs/Web/API/Clipboard
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Mon, Apr 20, 2020 at 8:13 AM Piotr Zarzycki 
> wrote:
>
> > Hi,
> >
> > I build SDK using distribution option by Maven. When I have tried build
> > application using distribution I'm getting following error:
> >
> > Error: Access of possibly undefined property generalClipboard through a
> > reference with static type Clipboard.
> >
> > It looks like this method [1] wasn't generated in distribution output.
> When
> > I look into class signature in SWC I see following only [2]
> >
> > [1]
> >
> >
> https://github.com/apache/royale-asjs/blob/bdaa1b0bc5f54423aac7bafda363f512236977a1/frameworks/projects/TLF/src/main/royale/org/apache/royale/textLayout/edit/Clipboard.as#L156
> > [2] https://ibb.co/GWdj86b
> >
> > Thanks,
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
> >
>

Re: Separate mailing list for Jenkins notifications

[Piotr Zarzycki]

To me argument of having info that server failed vs have cleaned inbox
finally - I'm choosing to have inbox cleaned.

If Apache rejected email from Jenkins on commits@ I can ask infra what can
be done.

On Mon, Apr 20, 2020, 10:43 PM Alex Harui  wrote:

> I've been unable to get the CI server to send to commits@.  Apache blocks
> it.
>
> Maybe issues@, but these aren't about issues.
>
> IMO, the point of these Jenkins emails is so that all committers know the
> current state of the builds and help fix issues when possible.  My concern
> is that when committers start filtering CI emails they will miss when one
> of their commits breaks the build.  So, the only reason to split CI emails
> off this list is to reduce traffic to the non-committers.
>
> My 2 cents,
> -Alex
>
> On 4/20/20, 1:17 PM, "OmPrakash Muppirala"  wrote:
>
> We already have issues@ and commits@.  Can we redirect the emails to
> one of
> the lists?
>
> On Mon, Apr 20, 2020 at 11:54 AM Alex Harui 
> wrote:
>
> > IMO, if we do create a new list, all committers must be subscribed.
> >
> > My 2 cents,
> > -Alex
> >
> > On 4/20/20, 1:53 AM, "Piotr Zarzycki" 
> wrote:
> >
> > Hi Guys,
> >
> > In the last year or so all notifications from Jenkins build are
> going
> > to
> > development mailing list. It becomes very messy I see every day
> 40-50
> > emails where 80% of that is notification from Jenkins.
> >
> > I would like to propose create separate mailing list to have such
> > notifications there.
> >
> > Is it possible?
> >
> > Please share your thoughts on that subject.
> >
> > Thanks,
> > --
> >
> > Piotr Zarzycki
> >
> >
> >
>
>
>

Re: Separate mailing list for Jenkins notifications

[Alex Harui]

I've been unable to get the CI server to send to commits@.  Apache blocks it.

Maybe issues@, but these aren't about issues.  

IMO, the point of these Jenkins emails is so that all committers know the 
current state of the builds and help fix issues when possible.  My concern is 
that when committers start filtering CI emails they will miss when one of their 
commits breaks the build.  So, the only reason to split CI emails off this list 
is to reduce traffic to the non-committers.

My 2 cents,
-Alex

On 4/20/20, 1:17 PM, "OmPrakash Muppirala"  wrote:

We already have issues@ and commits@.  Can we redirect the emails to one of
the lists?

On Mon, Apr 20, 2020 at 11:54 AM Alex Harui 
wrote:

> IMO, if we do create a new list, all committers must be subscribed.
>
> My 2 cents,
> -Alex
>
> On 4/20/20, 1:53 AM, "Piotr Zarzycki"  wrote:
>
> Hi Guys,
>
> In the last year or so all notifications from Jenkins build are going
> to
> development mailing list. It becomes very messy I see every day 40-50
> emails where 80% of that is notification from Jenkins.
>
> I would like to propose create separate mailing list to have such
> notifications there.
>
> Is it possible?
>
> Please share your thoughts on that subject.
>
> Thanks,
> --
>
> Piotr Zarzycki
>
>
>

Re: Separate mailing list for Jenkins notifications

[OmPrakash Muppirala]

We already have issues@ and commits@.  Can we redirect the emails to one of
the lists?

On Mon, Apr 20, 2020 at 11:54 AM Alex Harui 
wrote:

> IMO, if we do create a new list, all committers must be subscribed.
>
> My 2 cents,
> -Alex
>
> On 4/20/20, 1:53 AM, "Piotr Zarzycki"  wrote:
>
> Hi Guys,
>
> In the last year or so all notifications from Jenkins build are going
> to
> development mailing list. It becomes very messy I see every day 40-50
> emails where 80% of that is notification from Jenkins.
>
> I would like to propose create separate mailing list to have such
> notifications there.
>
> Is it possible?
>
> Please share your thoughts on that subject.
>
> Thanks,
> --
>
> Piotr Zarzycki
>
>
>

Re: 0.9.7 release notes updates - quick check

[Alex Harui]

The rest of this thread is about having folks make release notes changes to the 
release branch.

It is totally fine and encouraged to ask the RM before committing as Greg did 
at the start of the thread.  Cherry picking still can lead to merge issues 
later.  Best if a commit goes in the right branch.

-Alex

On 4/20/20, 12:17 PM, "Josh Tynjala"  wrote:

I'd rather not commit to a release branch unless the RM explicitly tells me
to, so I just thought I'd mention what I did.

--
Josh Tynjala
Bowler Hat LLC 



On Mon, Apr 20, 2020 at 11:57 AM Alex Harui 
wrote:

> Dev branch is at 0.9.8, so that's when your changes will go out,.
>
> -Alex
>
> On 4/20/20, 9:47 AM, "Josh Tynjala"  wrote:
>
> I added some 0.9.7 release notes for both royale-compiler and
> royale-asjs.
> I committed them to develop, though, so feel free to cherry-pick or
> whatever.
>
> --
> Josh Tynjala
> Bowler Hat LLC <
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.dev%2Fdata=02%7C01%7Caharui%40adobe.com%7C8c0bbd636f1948da818f08d7e55f7033%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637230070384701851sdata=Fjf63iEAgXuXc3j3p9C0K8IacWpHIITeb7RAKWHwCLE%3Dreserved=0
> >
>
>
> On Sun, Apr 19, 2020 at 6:21 AM Carlos Rovira  >
> wrote:
>
> > Hi Greg
> >
> > for compiler: just added improvements to maven by Chris Dutz and
> Maven
> > Distribution (that's now working) to create SDK with Maven
> > I think in compiler Josh should add many of his improvements
> >
> > Going to check framework
> >
> > thanks
> >
> > Carlos
> >
> >
> >
> > El dom., 19 abr. 2020 a las 2:02, Greg Dove ()
> > escribió:
> >
> > > I pushed some changes to both compiler and asjs release notes in
> branch
> > > release/0.9.7
> > >
> > > I'd like to suggest that others review this and add more as needed
> (as
> > > opposed to waiting until late in the process to do it).
> > >
> > >
> > > On Sat, Apr 18, 2020 at 11:25 AM Greg Dove 
> wrote:
> > >
> > > > Ok, thanks for clarifying Alex. I will do that later today.
> > > >
> > > >
> > > > On Sat, Apr 18, 2020 at 11:03 AM Alex Harui
> 
> > > > wrote:
> > > >
> > > >> IMO, there is no perfect solution.  There will be times where
> the
> > > release
> > > >> branch is so broken that it will be tossed and re-cut from
> develop.
> > But
> > > >> this time around we are trying to keep the release branches
> around, so
> > > make
> > > >> changes to the release branch and make sure the RM knows so
> they RM
> > > knows
> > > >> to merge changes back in case we get to the toss-and-re-cut
> point.
> > > >>
> > > >> Thanks,
> > > >> -Alex
> > > >>
> > > >> On 4/17/20, 3:20 PM, "Greg Dove"  wrote:
> > > >>
> > > >> I am not sure whether the current work on 0.9.7 release is
> a dry
> > run
> > > >> or a
> > > >> full effort (I have not been reading all details recently,
> > sorry). I
> > > >> assume
> > > >> it is a full release effort.
> > > >>
> > > >> For 0.9.6 release we had a collective rush to add things to
> > RELEASE
> > > >> NOTES
> > > >> before release.
> > > >>
> > > >> I have a few things I want to add to RELEASE NOTES. But I
> would
> > also
> > > >> like
> > > >> to make sure I apply our collective learning from last 
time.
> > > >>
> > > >> The issue last time (iirc) was that we pushed updates into
> develop
> > > >> branch
> > > >> which I think then were being cherry picked into release
> branch.
> > > This
> > > >> I
> > > >> believe contributed to some merge conflicts at some point.
> > > >> Can I get a definitive answer for where I should add
> updates to
> > > >> RELEASE
> > > >> NOTES at this point if it is not too late? I think it is
> probably
> > > >> supposed
> > > >> to be directly into release branch which then gets merged
> later
> > back
> > > >> into
> > > >> develop, but I'd like a confirmation of that if 

Re: 0.9.7 release notes updates - quick check

[Josh Tynjala]

I'd rather not commit to a release branch unless the RM explicitly tells me
to, so I just thought I'd mention what I did.

--
Josh Tynjala
Bowler Hat LLC 


On Mon, Apr 20, 2020 at 11:57 AM Alex Harui 
wrote:

> Dev branch is at 0.9.8, so that's when your changes will go out,.
>
> -Alex
>
> On 4/20/20, 9:47 AM, "Josh Tynjala"  wrote:
>
> I added some 0.9.7 release notes for both royale-compiler and
> royale-asjs.
> I committed them to develop, though, so feel free to cherry-pick or
> whatever.
>
> --
> Josh Tynjala
> Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.dev%2Fdata=02%7C01%7Caharui%40adobe.com%7Cf5610011ed24409e3ff808d7e54a8468%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229980521581300sdata=ggjch7VMFRMksgV5hRF60Ir9s%2FOFqWcFq07EormYcUs%3Dreserved=0
> >
>
>
> On Sun, Apr 19, 2020 at 6:21 AM Carlos Rovira  >
> wrote:
>
> > Hi Greg
> >
> > for compiler: just added improvements to maven by Chris Dutz and
> Maven
> > Distribution (that's now working) to create SDK with Maven
> > I think in compiler Josh should add many of his improvements
> >
> > Going to check framework
> >
> > thanks
> >
> > Carlos
> >
> >
> >
> > El dom., 19 abr. 2020 a las 2:02, Greg Dove ()
> > escribió:
> >
> > > I pushed some changes to both compiler and asjs release notes in
> branch
> > > release/0.9.7
> > >
> > > I'd like to suggest that others review this and add more as needed
> (as
> > > opposed to waiting until late in the process to do it).
> > >
> > >
> > > On Sat, Apr 18, 2020 at 11:25 AM Greg Dove 
> wrote:
> > >
> > > > Ok, thanks for clarifying Alex. I will do that later today.
> > > >
> > > >
> > > > On Sat, Apr 18, 2020 at 11:03 AM Alex Harui
> 
> > > > wrote:
> > > >
> > > >> IMO, there is no perfect solution.  There will be times where
> the
> > > release
> > > >> branch is so broken that it will be tossed and re-cut from
> develop.
> > But
> > > >> this time around we are trying to keep the release branches
> around, so
> > > make
> > > >> changes to the release branch and make sure the RM knows so
> they RM
> > > knows
> > > >> to merge changes back in case we get to the toss-and-re-cut
> point.
> > > >>
> > > >> Thanks,
> > > >> -Alex
> > > >>
> > > >> On 4/17/20, 3:20 PM, "Greg Dove"  wrote:
> > > >>
> > > >> I am not sure whether the current work on 0.9.7 release is
> a dry
> > run
> > > >> or a
> > > >> full effort (I have not been reading all details recently,
> > sorry). I
> > > >> assume
> > > >> it is a full release effort.
> > > >>
> > > >> For 0.9.6 release we had a collective rush to add things to
> > RELEASE
> > > >> NOTES
> > > >> before release.
> > > >>
> > > >> I have a few things I want to add to RELEASE NOTES. But I
> would
> > also
> > > >> like
> > > >> to make sure I apply our collective learning from last time.
> > > >>
> > > >> The issue last time (iirc) was that we pushed updates into
> develop
> > > >> branch
> > > >> which I think then were being cherry picked into release
> branch.
> > > This
> > > >> I
> > > >> believe contributed to some merge conflicts at some point.
> > > >> Can I get a definitive answer for where I should add
> updates to
> > > >> RELEASE
> > > >> NOTES at this point if it is not too late? I think it is
> probably
> > > >> supposed
> > > >> to be directly into release branch which then gets merged
> later
> > back
> > > >> into
> > > >> develop, but I'd like a confirmation of that if it is
> correct (and
> > > >> not too
> > > >> late), please.
> > > >>
> > > >>
> > > >>
> > >
> >
> >
> > --
> > Carlos Rovira
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cf5610011ed24409e3ff808d7e54a8468%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229980521581300sdata=bYVSf9Zg5R9DzuwNQIYgZ0o12s4kImSrVtBvTkCFU6U%3Dreserved=0
> >
>
>
>

Re: 0.9.7 release notes updates - quick check

[Alex Harui]

Dev branch is at 0.9.8, so that's when your changes will go out,.

-Alex

On 4/20/20, 9:47 AM, "Josh Tynjala"  wrote:

I added some 0.9.7 release notes for both royale-compiler and royale-asjs.
I committed them to develop, though, so feel free to cherry-pick or
whatever.

--
Josh Tynjala
Bowler Hat LLC 



On Sun, Apr 19, 2020 at 6:21 AM Carlos Rovira 
wrote:

> Hi Greg
>
> for compiler: just added improvements to maven by Chris Dutz and Maven
> Distribution (that's now working) to create SDK with Maven
> I think in compiler Josh should add many of his improvements
>
> Going to check framework
>
> thanks
>
> Carlos
>
>
>
> El dom., 19 abr. 2020 a las 2:02, Greg Dove ()
> escribió:
>
> > I pushed some changes to both compiler and asjs release notes in branch
> > release/0.9.7
> >
> > I'd like to suggest that others review this and add more as needed (as
> > opposed to waiting until late in the process to do it).
> >
> >
> > On Sat, Apr 18, 2020 at 11:25 AM Greg Dove  wrote:
> >
> > > Ok, thanks for clarifying Alex. I will do that later today.
> > >
> > >
> > > On Sat, Apr 18, 2020 at 11:03 AM Alex Harui 
> > > wrote:
> > >
> > >> IMO, there is no perfect solution.  There will be times where the
> > release
> > >> branch is so broken that it will be tossed and re-cut from develop.
> But
> > >> this time around we are trying to keep the release branches around, 
so
> > make
> > >> changes to the release branch and make sure the RM knows so they RM
> > knows
> > >> to merge changes back in case we get to the toss-and-re-cut point.
> > >>
> > >> Thanks,
> > >> -Alex
> > >>
> > >> On 4/17/20, 3:20 PM, "Greg Dove"  wrote:
> > >>
> > >> I am not sure whether the current work on 0.9.7 release is a dry
> run
> > >> or a
> > >> full effort (I have not been reading all details recently,
> sorry). I
> > >> assume
> > >> it is a full release effort.
> > >>
> > >> For 0.9.6 release we had a collective rush to add things to
> RELEASE
> > >> NOTES
> > >> before release.
> > >>
> > >> I have a few things I want to add to RELEASE NOTES. But I would
> also
> > >> like
> > >> to make sure I apply our collective learning from last time.
> > >>
> > >> The issue last time (iirc) was that we pushed updates into 
develop
> > >> branch
> > >> which I think then were being cherry picked into release branch.
> > This
> > >> I
> > >> believe contributed to some merge conflicts at some point.
> > >> Can I get a definitive answer for where I should add updates to
> > >> RELEASE
> > >> NOTES at this point if it is not too late? I think it is probably
> > >> supposed
> > >> to be directly into release branch which then gets merged later
> back
> > >> into
> > >> develop, but I'd like a confirmation of that if it is correct 
(and
> > >> not too
> > >> late), please.
> > >>
> > >>
> > >>
> >
>
>
> --
> Carlos Rovira
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7Cf5610011ed24409e3ff808d7e54a8468%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229980521581300sdata=bYVSf9Zg5R9DzuwNQIYgZ0o12s4kImSrVtBvTkCFU6U%3Dreserved=0
>

Re: Separate mailing list for Jenkins notifications

[Alex Harui]

IMO, if we do create a new list, all committers must be subscribed.

My 2 cents,
-Alex

On 4/20/20, 1:53 AM, "Piotr Zarzycki"  wrote:

Hi Guys,

In the last year or so all notifications from Jenkins build are going to
development mailing list. It becomes very messy I see every day 40-50
emails where 80% of that is notification from Jenkins.

I would like to propose create separate mailing list to have such
notifications there.

Is it possible?

Please share your thoughts on that subject.

Thanks,
-- 

Piotr Zarzycki

Re: Maven Plugin Problems

[Christofer Dutz]

Hi Yishay,

Well If you built the release of compiler on the ci server and did the 
verification on your local one, then the artifacts should exit on both.
On a machine with clean maven local repo or one where you haven't built 
compiler yet, the artifacts don’t exist.
So I would suggest you take the RC for compiler unpack it on your machine and 
run a "mvn install" on it.

Chris

Am 20.04.20, 19:17 schrieb "Yishay Weiss" :

I’m having trouble building royale-asjs with mvn, both on my machine and on 
Jenkins.

On my machine [1] it looks like royale-maven-plugin:0.9.7 can’t be found. 
When was it supposed to be created and stored?

On Jenkins [2] I’m getting


  1.   [exec] [ERROR] Failed to execute goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute (prerequisite-check) on
  2.  project royale-framework-parent: Execution prerequisite-check of goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:exe
  3.  cute failed: Not all conditions met, see log for details. -> [Help 1]

Any pointers?

Thanks.

[1] https://paste.apache.org/7dwe9
[2] https://paste.apache.org/z7nq0

Build failed in Jenkins: royale-asjs_jsonly #1336

[apacheroyaleci]

See 


Changes:

[joshtynjala] update RELEASE_NOTES for 0.9.7


--
[...truncated 1.71 MB...]

check-air-home:

check-compiler-home:

check-compile-env:
 [echo] OS: Windows Server 2016 / 10.0 / amd64
 [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.251-b08
 [echo] Java: 1.8.0_251
 [echo] Ant: Apache Ant(TM) version 1.9.9 compiled on February 2 2017 Ant 
Java Version: 1.8

prepare:

compile:

flat-ui-icons:
 [java] Error: Unable to access jarfile 

 [java] Java Result: 1

main:

main:

tweak-for-jsonly:
 [copy] Copying 1 file to 

 [copy] Copying 1 file to 


check-royale-config:

fixup-royale-config:

ide:

post-build:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

 [copy] Copying 1 file to 

 [copy] Copying 1 file to 

[touch] Creating 

[touch] Creating 

[touch] Creating 


last-message-if-airsdk:

main:
 [echo] ant main target completed on 04/20/2020 05:24:24 PM

sample-themes:

check-runtime-env:

runtime-setup:

mustella-setup:

load-task:

marmotinni-setup:

prepare:
 [echo] Making lib directory 
:\jenkins\workspace\royale-asjs_jsonly\marmotinni\java/lib
[mkdir] Created dir: 


selenium3-jar-check:

selenium3-jar:
[mkdir] Created dir: 


download-zip:
[mkdir] Created dir: 

  [get] Getting: https://bit.ly/2zm3ZzF
  [get] To: 

  [get] https://bit.ly/2zm3ZzF permanently moved to 
https://selenium-release.storage.googleapis.com/3.141/selenium-java-3.141.59.zip

untar-file:

unzip-file:
[unzip] Expanding: 

 into 


check-sum:

copy-downloaded-jar:
  [get] Getting: http://www.apache.org/licenses/LICENSE-2.0
  [get] To: 

 [copy] Copying 10 files to 


clean:

main:

clean:
   [delete] Deleting: 


check-compiler-home:

check-compiler:

compile:

compile-js:
 [echo] Compiling mustella.swc
 [echo] ROYALE_HOME: 

 [echo] ROYALE_COMPILER_HOME: 

 [java] args:
 [java] 
+royalelib=
 [java] +playerglobal.version=11.7
 [java] +env.PLAYERGLOBAL_HOME=${env.PLAYERGLOBAL_HOME}
 [java] -compiler.strict-xml=true
 [java] -compiler.targets=SWF,JSRoyale
 [java] 

Maven Plugin Problems

[Yishay Weiss]

I’m having trouble building royale-asjs with mvn, both on my machine and on 
Jenkins.

On my machine [1] it looks like royale-maven-plugin:0.9.7 can’t be found. When 
was it supposed to be created and stored?

On Jenkins [2] I’m getting


  1.   [exec] [ERROR] Failed to execute goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute (prerequisite-check) on
  2.  project royale-framework-parent: Execution prerequisite-check of goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:exe
  3.  cute failed: Not all conditions met, see log for details. -> [Help 1]

Any pointers?

Thanks.

[1] https://paste.apache.org/7dwe9
[2] https://paste.apache.org/z7nq0

Re: Maven Plugin Problems

[Christofer Dutz]

Hi Yishay,

well you only have 0.9.7 if you manually built the release version yourself ... 
I think Apache only knows about 0.9.6, 0.9.7-SNAPSHOT and 0.9.8-SNAPSHOT.

Chris


Am 20.04.20, 19:03 schrieb "Yishay Weiss" :




From: Yishay Weiss
Sent: Monday, April 20, 2020 7:23:10 PM
To: dev@royale.apache.org 
Subject: Maven Plugin Problems


I’m having trouble building royale-asjs with mvn, both on my machine and on 
Jenkins.



On my machine [1] it looks like royale-maven-plugin:0.9.7 can’t be found. 
When was it supposed to be created and stored?



On Jenkins [2] I’m getting



  1.   [exec] [ERROR] Failed to execute goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute (prerequisite-check) on
  2.  project royale-framework-parent: Execution prerequisite-check of goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:exe
  3.  cute failed: Not all conditions met, see log for details. -> [Help 1]



Any pointers?



Thanks.



[1] https://paste.apache.org/7dwe9

[2] https://paste.apache.org/z7nq0

RE: Maven Plugin Problems

[Yishay Weiss]

From: Yishay Weiss
Sent: Monday, April 20, 2020 7:23:10 PM
To: dev@royale.apache.org 
Subject: Maven Plugin Problems


I’m having trouble building royale-asjs with mvn, both on my machine and on 
Jenkins.



On my machine [1] it looks like royale-maven-plugin:0.9.7 can’t be found. When 
was it supposed to be created and stored?



On Jenkins [2] I’m getting



  1.   [exec] [ERROR] Failed to execute goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:execute (prerequisite-check) on
  2.  project royale-framework-parent: Execution prerequisite-check of goal 
org.codehaus.gmaven:groovy-maven-plugin:2.1.1:exe
  3.  cute failed: Not all conditions met, see log for details. -> [Help 1]



Any pointers?



Thanks.



[1] https://paste.apache.org/7dwe9

[2] https://paste.apache.org/z7nq0

Re: 0.9.7 release notes updates - quick check

[Josh Tynjala]

I added some 0.9.7 release notes for both royale-compiler and royale-asjs.
I committed them to develop, though, so feel free to cherry-pick or
whatever.

--
Josh Tynjala
Bowler Hat LLC 


On Sun, Apr 19, 2020 at 6:21 AM Carlos Rovira 
wrote:

> Hi Greg
>
> for compiler: just added improvements to maven by Chris Dutz and Maven
> Distribution (that's now working) to create SDK with Maven
> I think in compiler Josh should add many of his improvements
>
> Going to check framework
>
> thanks
>
> Carlos
>
>
>
> El dom., 19 abr. 2020 a las 2:02, Greg Dove ()
> escribió:
>
> > I pushed some changes to both compiler and asjs release notes in branch
> > release/0.9.7
> >
> > I'd like to suggest that others review this and add more as needed (as
> > opposed to waiting until late in the process to do it).
> >
> >
> > On Sat, Apr 18, 2020 at 11:25 AM Greg Dove  wrote:
> >
> > > Ok, thanks for clarifying Alex. I will do that later today.
> > >
> > >
> > > On Sat, Apr 18, 2020 at 11:03 AM Alex Harui 
> > > wrote:
> > >
> > >> IMO, there is no perfect solution.  There will be times where the
> > release
> > >> branch is so broken that it will be tossed and re-cut from develop.
> But
> > >> this time around we are trying to keep the release branches around, so
> > make
> > >> changes to the release branch and make sure the RM knows so they RM
> > knows
> > >> to merge changes back in case we get to the toss-and-re-cut point.
> > >>
> > >> Thanks,
> > >> -Alex
> > >>
> > >> On 4/17/20, 3:20 PM, "Greg Dove"  wrote:
> > >>
> > >> I am not sure whether the current work on 0.9.7 release is a dry
> run
> > >> or a
> > >> full effort (I have not been reading all details recently,
> sorry). I
> > >> assume
> > >> it is a full release effort.
> > >>
> > >> For 0.9.6 release we had a collective rush to add things to
> RELEASE
> > >> NOTES
> > >> before release.
> > >>
> > >> I have a few things I want to add to RELEASE NOTES. But I would
> also
> > >> like
> > >> to make sure I apply our collective learning from last time.
> > >>
> > >> The issue last time (iirc) was that we pushed updates into develop
> > >> branch
> > >> which I think then were being cherry picked into release branch.
> > This
> > >> I
> > >> believe contributed to some merge conflicts at some point.
> > >> Can I get a definitive answer for where I should add updates to
> > >> RELEASE
> > >> NOTES at this point if it is not too late? I think it is probably
> > >> supposed
> > >> to be directly into release branch which then gets merged later
> back
> > >> into
> > >> develop, but I'd like a confirmation of that if it is correct (and
> > >> not too
> > >> late), please.
> > >>
> > >>
> > >>
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

Re: Some of the Clipboard class method is not visible in Maven distribution build

[Josh Tynjala]

I think that you are trying to use the wrong Clipboard class. It looks like
you're using the JS global Clipboard, rather than
org.apache.royale.textLayout.edit.Clipboard.

org.apache.royale.textLayout.edit.Clipboard doesn't have writeText() and
readText() methods.

https://developer.mozilla.org/en-US/docs/Web/API/Clipboard

--
Josh Tynjala
Bowler Hat LLC 


On Mon, Apr 20, 2020 at 8:13 AM Piotr Zarzycki 
wrote:

> Hi,
>
> I build SDK using distribution option by Maven. When I have tried build
> application using distribution I'm getting following error:
>
> Error: Access of possibly undefined property generalClipboard through a
> reference with static type Clipboard.
>
> It looks like this method [1] wasn't generated in distribution output. When
> I look into class signature in SWC I see following only [2]
>
> [1]
>
> https://github.com/apache/royale-asjs/blob/bdaa1b0bc5f54423aac7bafda363f512236977a1/frameworks/projects/TLF/src/main/royale/org/apache/royale/textLayout/edit/Clipboard.as#L156
> [2] https://ibb.co/GWdj86b
>
> Thanks,
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Got it. It's working I'm able to get params. We will see what I can do
more. :)

Thank you!

pon., 20 kwi 2020 o 17:51 Harbs  napisał(a):

> Exactly like lines 99 through 102 here:
>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> <
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
>
> RouteToParameters will parse the parameters and use the ParameterRoutes to
> “do the right thing”.
>
> > On Apr 20, 2020, at 6:35 PM, Piotr Zarzycki 
> wrote:
> >
> > Yeah I just realized that I didn't express myself clearly. I would ask
> > differently cause you are saying about beads. What bead would parse for
> me
> > those parameters ?
> >
> > https://myrul.com/test?target=somevalue=
> > <
> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard=A55XXX
> >
> > somevalue
> >
> > I'm assuming this is not ready for BroswerRouter yet ?
> >
> >
> > pon., 20 kwi 2020 o 17:31 Harbs  napisał(a):
> >
> >> Huh? Not sure what you’re asking.
> >>
> >> The parsing of the URLs are all done via beads.
> >>
> >>> On Apr 20, 2020, at 5:51 PM, Piotr Zarzycki  >
> >> wrote:
> >>>
> >>> I will check your changes, but looking into the code you didn't touch
> >>> parameter parsing. It probably will be the same story for BrowserRouter
> >> and
> >>> HasRouter - Maybe it's worth to place it in  RouteToParameters ?
> >>>
> >>> pon., 20 kwi 2020 o 16:38 Harbs  napisał(a):
> >>>
>  I just pushed something. It builds, but I don’t have a setup to be
> able
> >> to
>  test it properly.
> 
>  Calling setState() and renderState() should work, but I still haven’t
>  finished beads to intercept links.
> 
>  Let me know how it goes…
> 
>  Harbs
> 
> > On Apr 20, 2020, at 4:45 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com
> >>>
>  wrote:
> >
> > Harbs,
> >
> > Do you think you will have something pushed today/tomorrow or is it
>  rather
> > something for the next week or so ?
> >
> > pon., 20 kwi 2020 o 11:56 Piotr Zarzycki 
> > napisał(a):
> >
> >> Ok. Thanks I look forward to your update.
> >>
> >> pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):
> >>
> >>> I’m deprecating Router and replacing it with HashRouter and
>  BrowserRouter.
> >>>
> >>> I’m going to try and keep the same beads working with either
> router.
> >>>
>  On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki <
>  piotrzarzyck...@gmail.com>
> >>> wrote:
> 
>  Harbs,
> 
>  What please describe what are you going to change exactly. Since I
>  need
> >>> to
>  move forward with my feature in application I will probably
> >> implement
>  adhoc solution with Router in app only, but I would like to avoid
> >> some
> >>> big
>  changes when you commit your code.
> 
>  Thanks,
>  Piotr
> 
>  pon., 20 kwi 2020 o 09:52 Harbs  >>> harbs.li...@gmail.com>> napisał(a):
> 
> > There are beads which handle the following:
> >
> > 1. Paths — in a hash router, this would be the part of the url
>  between
> >>> the
> > hash and the question mark or a second hash. In a “browser
> router”
>  this
> > would be the section between the base and and the question mark
> or
> >> a
> >>> hash
> > 2. Parameters — handles between the question mark and subsequent
>  hash.
> > (yes RouteToParameter works)
> > 3. I started work on dealing with trailing hash links for
> scrolling
>  to
> > anchor (or rather id) behavior, but that’s not yet done.
> (Something
> >>> like
> > this:
> >
>  https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> >>> <
> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior>
>  <
> >
>  https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> >>> <
> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> >> )
> >
> > Ideally all of these beads should work in either kind of router.
> >> This
> >>> is
> > already PAYG, but it’s going to take some work to get this
> working
>  and
> >>> PAYG
> > for both kinds of routers.
> >
> > I’ll try to work on this today…
> >
> > Harbs
> >
> >> On Apr 20, 2020, at 10:01 AM, Carlos Rovira <
>  carlosrov...@apache.org>
> > wrote:
> >>
> >> Hi Piotr,
> >>
> >> I used hashes with params, so that's completely fine and we
> should
> >>> have
> > it.
> >> In fact, I think we already should have it since I'm seeing
> >> "RoutToParameter" class right? Maybe Harbs should confirm this
> >> since
> >>> 

Re: Routing (was Re: Spectrum Components)

[Harbs]

Exactly like lines 99 through 102 here:
https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
 


RouteToParameters will parse the parameters and use the ParameterRoutes to “do 
the right thing”.

> On Apr 20, 2020, at 6:35 PM, Piotr Zarzycki  wrote:
> 
> Yeah I just realized that I didn't express myself clearly. I would ask
> differently cause you are saying about beads. What bead would parse for me
> those parameters ?
> 
> https://myrul.com/test?target=somevalue=
> 
> somevalue
> 
> I'm assuming this is not ready for BroswerRouter yet ?
> 
> 
> pon., 20 kwi 2020 o 17:31 Harbs  napisał(a):
> 
>> Huh? Not sure what you’re asking.
>> 
>> The parsing of the URLs are all done via beads.
>> 
>>> On Apr 20, 2020, at 5:51 PM, Piotr Zarzycki 
>> wrote:
>>> 
>>> I will check your changes, but looking into the code you didn't touch
>>> parameter parsing. It probably will be the same story for BrowserRouter
>> and
>>> HasRouter - Maybe it's worth to place it in  RouteToParameters ?
>>> 
>>> pon., 20 kwi 2020 o 16:38 Harbs  napisał(a):
>>> 
 I just pushed something. It builds, but I don’t have a setup to be able
>> to
 test it properly.
 
 Calling setState() and renderState() should work, but I still haven’t
 finished beads to intercept links.
 
 Let me know how it goes…
 
 Harbs
 
> On Apr 20, 2020, at 4:45 PM, Piotr Zarzycki >> 
 wrote:
> 
> Harbs,
> 
> Do you think you will have something pushed today/tomorrow or is it
 rather
> something for the next week or so ?
> 
> pon., 20 kwi 2020 o 11:56 Piotr Zarzycki 
> napisał(a):
> 
>> Ok. Thanks I look forward to your update.
>> 
>> pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):
>> 
>>> I’m deprecating Router and replacing it with HashRouter and
 BrowserRouter.
>>> 
>>> I’m going to try and keep the same beads working with either router.
>>> 
 On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki <
 piotrzarzyck...@gmail.com>
>>> wrote:
 
 Harbs,
 
 What please describe what are you going to change exactly. Since I
 need
>>> to
 move forward with my feature in application I will probably
>> implement
 adhoc solution with Router in app only, but I would like to avoid
>> some
>>> big
 changes when you commit your code.
 
 Thanks,
 Piotr
 
 pon., 20 kwi 2020 o 09:52 Harbs >> harbs.li...@gmail.com>> napisał(a):
 
> There are beads which handle the following:
> 
> 1. Paths — in a hash router, this would be the part of the url
 between
>>> the
> hash and the question mark or a second hash. In a “browser router”
 this
> would be the section between the base and and the question mark or
>> a
>>> hash
> 2. Parameters — handles between the question mark and subsequent
 hash.
> (yes RouteToParameter works)
> 3. I started work on dealing with trailing hash links for scrolling
 to
> anchor (or rather id) behavior, but that’s not yet done. (Something
>>> like
> this:
> 
 https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>>> <
>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior>
 <
> 
 https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>>> <
>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>> )
> 
> Ideally all of these beads should work in either kind of router.
>> This
>>> is
> already PAYG, but it’s going to take some work to get this working
 and
>>> PAYG
> for both kinds of routers.
> 
> I’ll try to work on this today…
> 
> Harbs
> 
>> On Apr 20, 2020, at 10:01 AM, Carlos Rovira <
 carlosrov...@apache.org>
> wrote:
>> 
>> Hi Piotr,
>> 
>> I used hashes with params, so that's completely fine and we should
>>> have
> it.
>> In fact, I think we already should have it since I'm seeing
>> "RoutToParameter" class right? Maybe Harbs should confirm this
>> since
>>> he
>> implemented, and I just saw the class but still not use it.
>> 
>> 
>> El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>) escribió:
>> 
>>> Harbs,
>>> 
>>> Agreed with that. We can rename them, but even in case of
 HashRouter
>>> -
> does
>>> exclude it ability to have parameters ? Does those parameters not
> 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Yeah I just realized that I didn't express myself clearly. I would ask
differently cause you are saying about beads. What bead would parse for me
those parameters ?

https://myrul.com/test?target=somevalue=

somevalue

I'm assuming this is not ready for BroswerRouter yet ?


pon., 20 kwi 2020 o 17:31 Harbs  napisał(a):

> Huh? Not sure what you’re asking.
>
> The parsing of the URLs are all done via beads.
>
> > On Apr 20, 2020, at 5:51 PM, Piotr Zarzycki 
> wrote:
> >
> > I will check your changes, but looking into the code you didn't touch
> > parameter parsing. It probably will be the same story for BrowserRouter
> and
> > HasRouter - Maybe it's worth to place it in  RouteToParameters ?
> >
> > pon., 20 kwi 2020 o 16:38 Harbs  napisał(a):
> >
> >> I just pushed something. It builds, but I don’t have a setup to be able
> to
> >> test it properly.
> >>
> >> Calling setState() and renderState() should work, but I still haven’t
> >> finished beads to intercept links.
> >>
> >> Let me know how it goes…
> >>
> >> Harbs
> >>
> >>> On Apr 20, 2020, at 4:45 PM, Piotr Zarzycki  >
> >> wrote:
> >>>
> >>> Harbs,
> >>>
> >>> Do you think you will have something pushed today/tomorrow or is it
> >> rather
> >>> something for the next week or so ?
> >>>
> >>> pon., 20 kwi 2020 o 11:56 Piotr Zarzycki 
> >>> napisał(a):
> >>>
>  Ok. Thanks I look forward to your update.
> 
>  pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):
> 
> > I’m deprecating Router and replacing it with HashRouter and
> >> BrowserRouter.
> >
> > I’m going to try and keep the same beads working with either router.
> >
> >> On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com>
> > wrote:
> >>
> >> Harbs,
> >>
> >> What please describe what are you going to change exactly. Since I
> >> need
> > to
> >> move forward with my feature in application I will probably
> implement
> >> adhoc solution with Router in app only, but I would like to avoid
> some
> > big
> >> changes when you commit your code.
> >>
> >> Thanks,
> >> Piotr
> >>
> >> pon., 20 kwi 2020 o 09:52 Harbs  > harbs.li...@gmail.com>> napisał(a):
> >>
> >>> There are beads which handle the following:
> >>>
> >>> 1. Paths — in a hash router, this would be the part of the url
> >> between
> > the
> >>> hash and the question mark or a second hash. In a “browser router”
> >> this
> >>> would be the section between the base and and the question mark or
> a
> > hash
> >>> 2. Parameters — handles between the question mark and subsequent
> >> hash.
> >>> (yes RouteToParameter works)
> >>> 3. I started work on dealing with trailing hash links for scrolling
> >> to
> >>> anchor (or rather id) behavior, but that’s not yet done. (Something
> > like
> >>> this:
> >>>
> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> > <
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior>
> >> <
> >>>
> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> > <
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>  )
> >>>
> >>> Ideally all of these beads should work in either kind of router.
> This
> > is
> >>> already PAYG, but it’s going to take some work to get this working
> >> and
> > PAYG
> >>> for both kinds of routers.
> >>>
> >>> I’ll try to work on this today…
> >>>
> >>> Harbs
> >>>
>  On Apr 20, 2020, at 10:01 AM, Carlos Rovira <
> >> carlosrov...@apache.org>
> >>> wrote:
> 
>  Hi Piotr,
> 
>  I used hashes with params, so that's completely fine and we should
> > have
> >>> it.
>  In fact, I think we already should have it since I'm seeing
>  "RoutToParameter" class right? Maybe Harbs should confirm this
> since
> > he
>  implemented, and I just saw the class but still not use it.
> 
> 
>  El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
>  piotrzarzyck...@gmail.com>) escribió:
> 
> > Harbs,
> >
> > Agreed with that. We can rename them, but even in case of
> >> HashRouter
> > -
> >>> does
> > exclude it ability to have parameters ? Does those parameters not
> >>> exists in
> > HasRouter as well. Is it not a common stuff no matter what kind
> of
> > url
> >>> it
> > is ?
> >
> > niedz., 19 kwi 2020 o 15:52 Harbs 
> > napisał(a):
> >
> >> After thinking about this some more, I’m thinking that Router
> > should be
> >> named and we should add another type of router for standard path
> >>> routing.
> >>
> >> React calls them HashRouter and 

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

[Josh Tynjala]

RoyaleUnit seems to default to port 1024. That was probably the default for
FlexUnit too.

--
Josh Tynjala
Bowler Hat LLC 


On Sun, Apr 19, 2020 at 9:50 PM Alex Harui  wrote:

> Hmm.  We enabled SSH.  I wonder if that changed security on sockets
> somehow.  Is RoyaleUnit using a known socket port number?
>
> Or maybe it is time to reboot the server.
>
> -Alex
>
> On 4/19/20, 12:03 AM, "Greg Dove"  wrote:
>
> Did RoyaleUnits use of sockets change  How were tests running in the
> past
> months?
>
> AFAIK nothing changed in terms of how the tests are run by RoyaleUnit -
> they launch the browser (chrome) and use websocket connection back to
> royaleunit for js - same as they have been doing for many months now
> since
> Josh set it up. I did make a change not so long ago to launch release
> builds instead of debug builds, but I don't understand why that would
> suddenly cause anything to stop working after it had been working
> without
> issue for 2 weeks. Everything seemed to be working ok until CI build
> #1090,
> and they also worked as normal for me locally this morning with up to
> date
> code for a full build as well. Maybe something else changed on the
> server?
>
>
>
> On Sun, Apr 19, 2020 at 5:13 PM Alex Harui 
> wrote:
>
> > Did RoyaleUnits use of sockets change  How were tests running in the
> past
> > months?
> >
> > -Alex
> >
> > On 4/18/20, 1:57 PM, "Greg Dove"  wrote:
> >
> > I am not sure what the actual issue on the server here is. It is
> saying
> > there is a socket timeout issue from the browser launch.
> > But this does provide an opportunity for a quick example of the
> > information
> > I shared recently about the changes to tests for JS, and it
> might be
> > helpful for you to see that with a 'live' example.
> >
> > For the part of the output:
> >
> > [royaleunit] Executing 'C:\Program Files
> > (x86)\Google\Chrome\Application\chrome.exe' with arguments:
> > [royaleunit] '<
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2Fws%2Fframeworks%2Fjs%2Fprojects%2FBasicJS%2Fsrc%2Ftest%2Froyale%2Ftarget%2Fbin%2Fjs-release%2Findex.htmldata=02%7C01%7Caharui%40adobe.com%7C8321911e6d794c46cbeb08d7e42fb50b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637228765870436810sdata=L8Bad6RMwPW1SOB8eAw0JvOjYGjvjTAr0B%2BqQOIcPpQ%3Dreserved=0
> > '>
> >
> > If you simply launch that link in a browser you will see the
> normal
> > launch
> > of the royaleunit BasicJS tests (it is a blank white page - not
> > particularly interesting in itself). If you look in the dev tools
> > console for that page, you can see that it also did not find a
> socket
> > server to connect to to report back the test results (which is
> > definitely
> > expected when you launch it like this, because there is of
> course none
> > available).
> > But you also will also see this in the console:
> > For javascript you can run this locally with console output for
> > debugging
> > purposes, using "?local" appended to the url.
> > It may not work for all browsers with file:// protocol (works
> with
> > Chrome),
> > in which case you need a local http server
> >
> > So if you append
> > ?local
> > to the url by simply typing that at the end of the original url
> in the
> > browser and reload, you will see the following in the console:
> >
> > [JS] flexUnitTests::DataGridColumnTest.testLabelProperty .
> > [JS] Time: 0.038
> > [JS] OK (1 test)
> >
> > ...which means the tests themselves are not the problem here.
> There
> > was no
> > suggestion that they were...this was just to illustrate how you
> can
> > toggle
> > between CI style tests and console output of test results.
> > The build error may indicate some issue with the chrome launch
> itself
> > I am
> > guessing (not sure).
> > Aside: The css is not being served as the correct MIME type, so
> you
> > may see
> > console errors for that as well, but I think that has always
> been the
> > case
> > on the CI server (not sure).
> >
> >
> >
> > On Sun, Apr 19, 2020 at 8:19 AM 
> wrote:
> >
> > > See <
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2F1097%2Fdisplay%2Fredirect%3Fpage%3Dchangesdata=02%7C01%7Caharui%40adobe.com%7C8321911e6d794c46cbeb08d7e42fb50b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637228765870436810sdata=k3G5W%2BLxSp%2Fp%2BHJtExsKhOM9dLu3xfSBffOXt6CZ4kU%3Dreserved=0

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

[Piotr Zarzycki]

Hi Om,

Thanks for update. Sorry I missed the thread! :)

pon., 20 kwi 2020 o 17:38 OmPrakash Muppirala 
napisał(a):

> This is on the Agent2 virtual machine I am in the process of setting up.  I
> will fix this soon.  Please check the `Prioritize Release Jobs on CI`
> thread where I am posting details on my progress with this.
>
> Thanks,
> Om
>
> On Mon, Apr 20, 2020 at 7:57 AM Piotr Zarzycki 
> wrote:
>
> > Maybe it's just some hand on machine. Can someone look into that ? I
> cannot
> > login into Remote Machine for some reason.
> >
> > pon., 20 kwi 2020 o 16:53  napisał(a):
> >
> > > See <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/1335/display/redirect?page=changes
> > > >
> > >
> > > Changes:
> > >
> > > [harbs] HashRouter and BrowserRouter
> > >
> > >
> > > --
> > > [...truncated 1.71 MB...]
> > >
> > > check-air-home:
> > >
> > > check-compiler-home:
> > >
> > > check-compile-env:
> > >  [echo] OS: Windows Server 2016 / 10.0 / amd64
> > >  [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.251-b08
> > >  [echo] Java: 1.8.0_251
> > >  [echo] Ant: Apache Ant(TM) version 1.9.9 compiled on February 2
> 2017
> > > Ant Java Version: 1.8
> > >
> > > prepare:
> > >
> > > compile:
> > >
> > > flat-ui-icons:
> > >  [java] Error: Unable to access jarfile <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/fontsrc/${env.ROYALE_HOME}/lib/mxmlc.jar
> > > >
> > >  [java] Java Result: 1
> > >
> > > main:
> > >
> > > main:
> > >
> > > tweak-for-jsonly:
> > >  [copy] Copying 1 file to <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/libs
> > > >
> > >  [copy] Copying 1 file to <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/temp
> > > >
> > >
> > > check-royale-config:
> > >
> > > fixup-royale-config:
> > >
> > > ide:
> > >
> > > post-build:
> > > [mkdir] Created dir: <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/locale
> > > >
> > > [mkdir] Created dir: <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/mx
> > > >
> > > [mkdir] Created dir: <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/rsls
> > > >
> > > [mkdir] Created dir: <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/themes/Halo
> > > >
> > >  [copy] Copying 1 file to <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/themes/Halo
> > > >
> > >  [copy] Copying 1 file to <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks
> > > >
> > > [touch] Creating <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/macfonts.ser
> > > >
> > > [touch] Creating <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/winfonts.ser
> > > >
> > > [touch] Creating <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/localfonts.ser
> > > >
> > >
> > > last-message-if-airsdk:
> > >
> > > main:
> > >  [echo] ant main target completed on 04/20/2020 02:52:27 PM
> > >
> > > sample-themes:
> > >
> > > check-runtime-env:
> > >
> > > runtime-setup:
> > >
> > > mustella-setup:
> > >
> > > load-task:
> > >
> > > marmotinni-setup:
> > >
> > > prepare:
> > >  [echo] Making lib directory <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/c
> > > >:\jenkins\workspace\royale-asjs_jsonly\marmotinni\java/lib
> > > [mkdir] Created dir: <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/lib
> > > >
> > >
> > > selenium3-jar-check:
> > >
> > > selenium3-jar:
> > > [mkdir] Created dir: <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/lib/selenium
> > > >
> > >
> > > download-zip:
> > > [mkdir] Created dir: <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/in
> > > >
> > >   [get] Getting: https://bit.ly/2zm3ZzF
> > >   [get] To: <
> > >
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/in/client-combined-3.141.59.zip
> > > >
> > >   [get] https://bit.ly/2zm3ZzF permanently moved to
> > >
> >
> https://selenium-release.storage.googleapis.com/3.141/selenium-java-3.141.59.zip
> > >
> > > untar-file:
> > >
> > > unzip-file:
> > > [unzip] Expanding: <
> > >
> >
> 

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

[OmPrakash Muppirala]

This is on the Agent2 virtual machine I am in the process of setting up.  I
will fix this soon.  Please check the `Prioritize Release Jobs on CI`
thread where I am posting details on my progress with this.

Thanks,
Om

On Mon, Apr 20, 2020 at 7:57 AM Piotr Zarzycki 
wrote:

> Maybe it's just some hand on machine. Can someone look into that ? I cannot
> login into Remote Machine for some reason.
>
> pon., 20 kwi 2020 o 16:53  napisał(a):
>
> > See <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/1335/display/redirect?page=changes
> > >
> >
> > Changes:
> >
> > [harbs] HashRouter and BrowserRouter
> >
> >
> > --
> > [...truncated 1.71 MB...]
> >
> > check-air-home:
> >
> > check-compiler-home:
> >
> > check-compile-env:
> >  [echo] OS: Windows Server 2016 / 10.0 / amd64
> >  [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.251-b08
> >  [echo] Java: 1.8.0_251
> >  [echo] Ant: Apache Ant(TM) version 1.9.9 compiled on February 2 2017
> > Ant Java Version: 1.8
> >
> > prepare:
> >
> > compile:
> >
> > flat-ui-icons:
> >  [java] Error: Unable to access jarfile <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/fontsrc/${env.ROYALE_HOME}/lib/mxmlc.jar
> > >
> >  [java] Java Result: 1
> >
> > main:
> >
> > main:
> >
> > tweak-for-jsonly:
> >  [copy] Copying 1 file to <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/libs
> > >
> >  [copy] Copying 1 file to <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/temp
> > >
> >
> > check-royale-config:
> >
> > fixup-royale-config:
> >
> > ide:
> >
> > post-build:
> > [mkdir] Created dir: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/locale
> > >
> > [mkdir] Created dir: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/mx
> > >
> > [mkdir] Created dir: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/rsls
> > >
> > [mkdir] Created dir: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/themes/Halo
> > >
> >  [copy] Copying 1 file to <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/themes/Halo
> > >
> >  [copy] Copying 1 file to <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks
> > >
> > [touch] Creating <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/macfonts.ser
> > >
> > [touch] Creating <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/winfonts.ser
> > >
> > [touch] Creating <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/localfonts.ser
> > >
> >
> > last-message-if-airsdk:
> >
> > main:
> >  [echo] ant main target completed on 04/20/2020 02:52:27 PM
> >
> > sample-themes:
> >
> > check-runtime-env:
> >
> > runtime-setup:
> >
> > mustella-setup:
> >
> > load-task:
> >
> > marmotinni-setup:
> >
> > prepare:
> >  [echo] Making lib directory <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/c
> > >:\jenkins\workspace\royale-asjs_jsonly\marmotinni\java/lib
> > [mkdir] Created dir: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/lib
> > >
> >
> > selenium3-jar-check:
> >
> > selenium3-jar:
> > [mkdir] Created dir: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/lib/selenium
> > >
> >
> > download-zip:
> > [mkdir] Created dir: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/in
> > >
> >   [get] Getting: https://bit.ly/2zm3ZzF
> >   [get] To: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/in/client-combined-3.141.59.zip
> > >
> >   [get] https://bit.ly/2zm3ZzF permanently moved to
> >
> https://selenium-release.storage.googleapis.com/3.141/selenium-java-3.141.59.zip
> >
> > untar-file:
> >
> > unzip-file:
> > [unzip] Expanding: <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/in/client-combined-3.141.59.zip
> >
> > into <
> >
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/in/temp
> > >
> >
> > check-sum:
> >
> > copy-downloaded-jar:
> >   [get] Getting: http://www.apache.org/licenses/LICENSE-2.0
> >   [get] To: <
> >
> 

Re: [royale-compiler] branch release/0.9.7 updated: Update compiler build tools version

[Alex Harui]

IMO, dev branch should not have been updated as it did not need the code change 
in 1.2.0.  Cherry picking can also cause merge conflicts.

But you can't eliminate the risks of merge conflicts.  So just keep on going 
with what is committed currently.

-Alex

On 4/20/20, 4:40 AM, "Yishay Weiss"  wrote:

Carlos, are you sure your commit belongs in dev at this stage? If we are 
going to merge release into dev anyway, maybe it’s best to wait until then to 
avoid this conflict. Also, I’m not a Git expert, but wouldn’t the merge 
algorithm detect the identity in content anyway and avoid conflict?

From: Piotr Zarzycki
Sent: Monday, April 20, 2020 2:30 PM
To: Apache Royale Development
Subject: Re: [royale-compiler] branch release/0.9.7 updated: Update 
compiler build tools version

Agree with Carlos - It may end up with problems. Actually after release
branch should be probably just merged to develop and probably master (not
sure here) without changes.

pon., 20 kwi 2020 o 13:27 Carlos Rovira 
napisał(a):

> Hi Yishay,
>
> since I did the same in develop, will not be better to just cherry pick my
> commit on release branch?
> I think doing this way will make the merge to develop from release
> problematic since will find different changes (although are the same) and
> you'll need to resolve the merge manually.
>
> maybe I'm wrong
>
> Thanks
>
>
> El lun., 20 abr. 2020 a las 12:58,  escribió:
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > yishayw pushed a commit to branch release/0.9.7
> > in repository 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitbox.apache.org%2Frepos%2Fasf%2Froyale-compiler.gitdata=02%7C01%7Caharui%40adobe.com%7C0126494d6a6e42a426a708d7e51fab8e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229796541721500sdata=q6T8B558JaACJJ7qSzbhsV1c4eBL774lU8%2FSuUmegu4%3Dreserved=0
> >
> >
> > The following commit(s) were added to refs/heads/release/0.9.7 by this
> > push:
> >  new 1b8f24a  Update compiler build tools version
> > 1b8f24a is described below
> >
> > commit 1b8f24aee6bf21d25ae75b039b88c00a596c46bb
> > Author: DESKTOP-RH4S838\Yishay 
> > AuthorDate: Mon Apr 20 13:58:20 2020 +0300
> >
> > Update compiler build tools version
> > ---
> >  pom.xml | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/pom.xml b/pom.xml
> > index 3fea91d..1ee3dd9 100644
> > --- a/pom.xml
> > +++ b/pom.xml
> > @@ -47,7 +47,7 @@
> >
> >
> UTF-8
> >  3.3.1
> >
> > -1.1.0
> > +1.2.0
> >  1.1.0
> >
> >  4.15.0
> >
> >
>
> --
> Carlos Rovira
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C0126494d6a6e42a426a708d7e51fab8e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229796541731496sdata=oGWnWGINE4gGtezx2MeuZvo3cqc5CSvcx7AdrYJeWV8%3Dreserved=0
>


--

Piotr Zarzycki

Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C0126494d6a6e42a426a708d7e51fab8e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229796541731496sdata=C79G11fhsKtkw5%2BaffnMEjyUn0vBSQol%2B0b7UJjvatw%3Dreserved=0

*

Re: Routing (was Re: Spectrum Components)

[Harbs]

Huh? Not sure what you’re asking.

The parsing of the URLs are all done via beads.

> On Apr 20, 2020, at 5:51 PM, Piotr Zarzycki  wrote:
> 
> I will check your changes, but looking into the code you didn't touch
> parameter parsing. It probably will be the same story for BrowserRouter and
> HasRouter - Maybe it's worth to place it in  RouteToParameters ?
> 
> pon., 20 kwi 2020 o 16:38 Harbs  napisał(a):
> 
>> I just pushed something. It builds, but I don’t have a setup to be able to
>> test it properly.
>> 
>> Calling setState() and renderState() should work, but I still haven’t
>> finished beads to intercept links.
>> 
>> Let me know how it goes…
>> 
>> Harbs
>> 
>>> On Apr 20, 2020, at 4:45 PM, Piotr Zarzycki 
>> wrote:
>>> 
>>> Harbs,
>>> 
>>> Do you think you will have something pushed today/tomorrow or is it
>> rather
>>> something for the next week or so ?
>>> 
>>> pon., 20 kwi 2020 o 11:56 Piotr Zarzycki 
>>> napisał(a):
>>> 
 Ok. Thanks I look forward to your update.
 
 pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):
 
> I’m deprecating Router and replacing it with HashRouter and
>> BrowserRouter.
> 
> I’m going to try and keep the same beads working with either router.
> 
>> On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
> wrote:
>> 
>> Harbs,
>> 
>> What please describe what are you going to change exactly. Since I
>> need
> to
>> move forward with my feature in application I will probably implement
>> adhoc solution with Router in app only, but I would like to avoid some
> big
>> changes when you commit your code.
>> 
>> Thanks,
>> Piotr
>> 
>> pon., 20 kwi 2020 o 09:52 Harbs  harbs.li...@gmail.com>> napisał(a):
>> 
>>> There are beads which handle the following:
>>> 
>>> 1. Paths — in a hash router, this would be the part of the url
>> between
> the
>>> hash and the question mark or a second hash. In a “browser router”
>> this
>>> would be the section between the base and and the question mark or a
> hash
>>> 2. Parameters — handles between the question mark and subsequent
>> hash.
>>> (yes RouteToParameter works)
>>> 3. I started work on dealing with trailing hash links for scrolling
>> to
>>> anchor (or rather id) behavior, but that’s not yet done. (Something
> like
>>> this:
>>> 
>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> 
>> <
>>> 
>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> >> 
>>> Ideally all of these beads should work in either kind of router. This
> is
>>> already PAYG, but it’s going to take some work to get this working
>> and
> PAYG
>>> for both kinds of routers.
>>> 
>>> I’ll try to work on this today…
>>> 
>>> Harbs
>>> 
 On Apr 20, 2020, at 10:01 AM, Carlos Rovira <
>> carlosrov...@apache.org>
>>> wrote:
 
 Hi Piotr,
 
 I used hashes with params, so that's completely fine and we should
> have
>>> it.
 In fact, I think we already should have it since I'm seeing
 "RoutToParameter" class right? Maybe Harbs should confirm this since
> he
 implemented, and I just saw the class but still not use it.
 
 
 El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
 piotrzarzyck...@gmail.com>) escribió:
 
> Harbs,
> 
> Agreed with that. We can rename them, but even in case of
>> HashRouter
> -
>>> does
> exclude it ability to have parameters ? Does those parameters not
>>> exists in
> HasRouter as well. Is it not a common stuff no matter what kind of
> url
>>> it
> is ?
> 
> niedz., 19 kwi 2020 o 15:52 Harbs 
> napisał(a):
> 
>> After thinking about this some more, I’m thinking that Router
> should be
>> named and we should add another type of router for standard path
>>> routing.
>> 
>> React calls them HashRouter and BrowserRouter. Maybe we should use
> the
>> same names…
>> 
>> 
>>> 
> 
>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> <
>> 
>>> 
> 
>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
>> 
>> 
>>> On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com
>> 
>> wrote:
>>> 
>>> Hi Harbs,
>>> 
>>> It sounds like you are asking me to check in onInit whether
>>> if(location.hash) exists then do something, but if doesn't exists
>>> check
>> url
>>> 

Some of the Clipboard class method is not visible in Maven distribution build

[Piotr Zarzycki]

Hi,

I build SDK using distribution option by Maven. When I have tried build
application using distribution I'm getting following error:

Error: Access of possibly undefined property generalClipboard through a
reference with static type Clipboard.

It looks like this method [1] wasn't generated in distribution output. When
I look into class signature in SWC I see following only [2]

[1]
https://github.com/apache/royale-asjs/blob/bdaa1b0bc5f54423aac7bafda363f512236977a1/frameworks/projects/TLF/src/main/royale/org/apache/royale/textLayout/edit/Clipboard.as#L156
[2] https://ibb.co/GWdj86b

Thanks,
-- 

Piotr Zarzycki

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

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

[Piotr Zarzycki]

Maybe it's just some hand on machine. Can someone look into that ? I cannot
login into Remote Machine for some reason.

pon., 20 kwi 2020 o 16:53  napisał(a):

> See <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/1335/display/redirect?page=changes
> >
>
> Changes:
>
> [harbs] HashRouter and BrowserRouter
>
>
> --
> [...truncated 1.71 MB...]
>
> check-air-home:
>
> check-compiler-home:
>
> check-compile-env:
>  [echo] OS: Windows Server 2016 / 10.0 / amd64
>  [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.251-b08
>  [echo] Java: 1.8.0_251
>  [echo] Ant: Apache Ant(TM) version 1.9.9 compiled on February 2 2017
> Ant Java Version: 1.8
>
> prepare:
>
> compile:
>
> flat-ui-icons:
>  [java] Error: Unable to access jarfile <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/fontsrc/${env.ROYALE_HOME}/lib/mxmlc.jar
> >
>  [java] Java Result: 1
>
> main:
>
> main:
>
> tweak-for-jsonly:
>  [copy] Copying 1 file to <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/libs
> >
>  [copy] Copying 1 file to <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/temp
> >
>
> check-royale-config:
>
> fixup-royale-config:
>
> ide:
>
> post-build:
> [mkdir] Created dir: <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/locale
> >
> [mkdir] Created dir: <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/mx
> >
> [mkdir] Created dir: <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/rsls
> >
> [mkdir] Created dir: <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/themes/Halo
> >
>  [copy] Copying 1 file to <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/themes/Halo
> >
>  [copy] Copying 1 file to <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks
> >
> [touch] Creating <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/macfonts.ser
> >
> [touch] Creating <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/winfonts.ser
> >
> [touch] Creating <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/localfonts.ser
> >
>
> last-message-if-airsdk:
>
> main:
>  [echo] ant main target completed on 04/20/2020 02:52:27 PM
>
> sample-themes:
>
> check-runtime-env:
>
> runtime-setup:
>
> mustella-setup:
>
> load-task:
>
> marmotinni-setup:
>
> prepare:
>  [echo] Making lib directory <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/c
> >:\jenkins\workspace\royale-asjs_jsonly\marmotinni\java/lib
> [mkdir] Created dir: <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/lib
> >
>
> selenium3-jar-check:
>
> selenium3-jar:
> [mkdir] Created dir: <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/lib/selenium
> >
>
> download-zip:
> [mkdir] Created dir: <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/in
> >
>   [get] Getting: https://bit.ly/2zm3ZzF
>   [get] To: <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/in/client-combined-3.141.59.zip
> >
>   [get] https://bit.ly/2zm3ZzF permanently moved to
> https://selenium-release.storage.googleapis.com/3.141/selenium-java-3.141.59.zip
>
> untar-file:
>
> unzip-file:
> [unzip] Expanding: <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/in/client-combined-3.141.59.zip>
> into <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/in/temp
> >
>
> check-sum:
>
> copy-downloaded-jar:
>   [get] Getting: http://www.apache.org/licenses/LICENSE-2.0
>   [get] To: <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/lib/selenium/selenium-LICENSE.txt
> >
>  [copy] Copying 10 files to <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/marmotinni/java/lib/selenium
> >
>
> clean:
>
> main:
>
> clean:
>[delete] Deleting: <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/mustella/mustella.swc
> >
>
> check-compiler-home:
>
> check-compiler:
>
> compile:
>
> compile-js:
>  [echo] Compiling mustella.swc
>  [echo] ROYALE_HOME: <
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/
> >
>  [echo] 

Build failed in Jenkins: royale-asjs_jsonly #1335

[apacheroyaleci]

See 


Changes:

[harbs] HashRouter and BrowserRouter


--
[...truncated 1.71 MB...]

check-air-home:

check-compiler-home:

check-compile-env:
 [echo] OS: Windows Server 2016 / 10.0 / amd64
 [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.251-b08
 [echo] Java: 1.8.0_251
 [echo] Ant: Apache Ant(TM) version 1.9.9 compiled on February 2 2017 Ant 
Java Version: 1.8

prepare:

compile:

flat-ui-icons:
 [java] Error: Unable to access jarfile 

 [java] Java Result: 1

main:

main:

tweak-for-jsonly:
 [copy] Copying 1 file to 

 [copy] Copying 1 file to 


check-royale-config:

fixup-royale-config:

ide:

post-build:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

 [copy] Copying 1 file to 

 [copy] Copying 1 file to 

[touch] Creating 

[touch] Creating 

[touch] Creating 


last-message-if-airsdk:

main:
 [echo] ant main target completed on 04/20/2020 02:52:27 PM

sample-themes:

check-runtime-env:

runtime-setup:

mustella-setup:

load-task:

marmotinni-setup:

prepare:
 [echo] Making lib directory 
:\jenkins\workspace\royale-asjs_jsonly\marmotinni\java/lib
[mkdir] Created dir: 


selenium3-jar-check:

selenium3-jar:
[mkdir] Created dir: 


download-zip:
[mkdir] Created dir: 

  [get] Getting: https://bit.ly/2zm3ZzF
  [get] To: 

  [get] https://bit.ly/2zm3ZzF permanently moved to 
https://selenium-release.storage.googleapis.com/3.141/selenium-java-3.141.59.zip

untar-file:

unzip-file:
[unzip] Expanding: 

 into 


check-sum:

copy-downloaded-jar:
  [get] Getting: http://www.apache.org/licenses/LICENSE-2.0
  [get] To: 

 [copy] Copying 10 files to 


clean:

main:

clean:
   [delete] Deleting: 


check-compiler-home:

check-compiler:

compile:

compile-js:
 [echo] Compiling mustella.swc
 [echo] ROYALE_HOME: 

 [echo] ROYALE_COMPILER_HOME: 

 [java] args:
 [java] 
+royalelib=
 [java] +playerglobal.version=11.7
 [java] +env.PLAYERGLOBAL_HOME=${env.PLAYERGLOBAL_HOME}
 [java] -compiler.strict-xml=true
 [java] -compiler.targets=SWF,JSRoyale
 [java] 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

I will check your changes, but looking into the code you didn't touch
parameter parsing. It probably will be the same story for BrowserRouter and
HasRouter - Maybe it's worth to place it in  RouteToParameters ?

pon., 20 kwi 2020 o 16:38 Harbs  napisał(a):

> I just pushed something. It builds, but I don’t have a setup to be able to
> test it properly.
>
> Calling setState() and renderState() should work, but I still haven’t
> finished beads to intercept links.
>
> Let me know how it goes…
>
> Harbs
>
> > On Apr 20, 2020, at 4:45 PM, Piotr Zarzycki 
> wrote:
> >
> > Harbs,
> >
> > Do you think you will have something pushed today/tomorrow or is it
> rather
> > something for the next week or so ?
> >
> > pon., 20 kwi 2020 o 11:56 Piotr Zarzycki 
> > napisał(a):
> >
> >> Ok. Thanks I look forward to your update.
> >>
> >> pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):
> >>
> >>> I’m deprecating Router and replacing it with HashRouter and
> BrowserRouter.
> >>>
> >>> I’m going to try and keep the same beads working with either router.
> >>>
>  On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >>> wrote:
> 
>  Harbs,
> 
>  What please describe what are you going to change exactly. Since I
> need
> >>> to
>  move forward with my feature in application I will probably implement
>  adhoc solution with Router in app only, but I would like to avoid some
> >>> big
>  changes when you commit your code.
> 
>  Thanks,
>  Piotr
> 
>  pon., 20 kwi 2020 o 09:52 Harbs  >>> harbs.li...@gmail.com>> napisał(a):
> 
> > There are beads which handle the following:
> >
> > 1. Paths — in a hash router, this would be the part of the url
> between
> >>> the
> > hash and the question mark or a second hash. In a “browser router”
> this
> > would be the section between the base and and the question mark or a
> >>> hash
> > 2. Parameters — handles between the question mark and subsequent
> hash.
> > (yes RouteToParameter works)
> > 3. I started work on dealing with trailing hash links for scrolling
> to
> > anchor (or rather id) behavior, but that’s not yet done. (Something
> >>> like
> > this:
> >
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> >>> 
> <
> >
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
> >>>  >>)
> >
> > Ideally all of these beads should work in either kind of router. This
> >>> is
> > already PAYG, but it’s going to take some work to get this working
> and
> >>> PAYG
> > for both kinds of routers.
> >
> > I’ll try to work on this today…
> >
> > Harbs
> >
> >> On Apr 20, 2020, at 10:01 AM, Carlos Rovira <
> carlosrov...@apache.org>
> > wrote:
> >>
> >> Hi Piotr,
> >>
> >> I used hashes with params, so that's completely fine and we should
> >>> have
> > it.
> >> In fact, I think we already should have it since I'm seeing
> >> "RoutToParameter" class right? Maybe Harbs should confirm this since
> >>> he
> >> implemented, and I just saw the class but still not use it.
> >>
> >>
> >> El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
> >> piotrzarzyck...@gmail.com>) escribió:
> >>
> >>> Harbs,
> >>>
> >>> Agreed with that. We can rename them, but even in case of
> HashRouter
> >>> -
> > does
> >>> exclude it ability to have parameters ? Does those parameters not
> > exists in
> >>> HasRouter as well. Is it not a common stuff no matter what kind of
> >>> url
> > it
> >>> is ?
> >>>
> >>> niedz., 19 kwi 2020 o 15:52 Harbs 
> >>> napisał(a):
> >>>
>  After thinking about this some more, I’m thinking that Router
> >>> should be
>  named and we should add another type of router for standard path
> > routing.
> 
>  React calls them HashRouter and BrowserRouter. Maybe we should use
> >>> the
>  same names…
> 
> 
> >
> >>>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> >>> <
> 
> >
> >>>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> 
> 
> > On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com
> 
>  wrote:
> >
> > Hi Harbs,
> >
> > It sounds like you are asking me to check in onInit whether
> > if(location.hash) exists then do something, but if doesn't exists
> > check
>  url
> > params. - I may understand it in a wrong way, but I think
> > location.hash
>  may
> > exists and location.search - where parameters are stored could
> >>> exists
> > equally.
> >
> > 

Re: Routing (was Re: Spectrum Components)

[Harbs]

I just pushed something. It builds, but I don’t have a setup to be able to test 
it properly.

Calling setState() and renderState() should work, but I still haven’t finished 
beads to intercept links.

Let me know how it goes…

Harbs

> On Apr 20, 2020, at 4:45 PM, Piotr Zarzycki  wrote:
> 
> Harbs,
> 
> Do you think you will have something pushed today/tomorrow or is it rather
> something for the next week or so ?
> 
> pon., 20 kwi 2020 o 11:56 Piotr Zarzycki 
> napisał(a):
> 
>> Ok. Thanks I look forward to your update.
>> 
>> pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):
>> 
>>> I’m deprecating Router and replacing it with HashRouter and BrowserRouter.
>>> 
>>> I’m going to try and keep the same beads working with either router.
>>> 
 On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki 
>>> wrote:
 
 Harbs,
 
 What please describe what are you going to change exactly. Since I need
>>> to
 move forward with my feature in application I will probably implement
 adhoc solution with Router in app only, but I would like to avoid some
>>> big
 changes when you commit your code.
 
 Thanks,
 Piotr
 
 pon., 20 kwi 2020 o 09:52 Harbs >> harbs.li...@gmail.com>> napisał(a):
 
> There are beads which handle the following:
> 
> 1. Paths — in a hash router, this would be the part of the url between
>>> the
> hash and the question mark or a second hash. In a “browser router” this
> would be the section between the base and and the question mark or a
>>> hash
> 2. Parameters — handles between the question mark and subsequent hash.
> (yes RouteToParameter works)
> 3. I started work on dealing with trailing hash links for scrolling to
> anchor (or rather id) behavior, but that’s not yet done. (Something
>>> like
> this:
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>>>  <
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>>> >)
> 
> Ideally all of these beads should work in either kind of router. This
>>> is
> already PAYG, but it’s going to take some work to get this working and
>>> PAYG
> for both kinds of routers.
> 
> I’ll try to work on this today…
> 
> Harbs
> 
>> On Apr 20, 2020, at 10:01 AM, Carlos Rovira 
> wrote:
>> 
>> Hi Piotr,
>> 
>> I used hashes with params, so that's completely fine and we should
>>> have
> it.
>> In fact, I think we already should have it since I'm seeing
>> "RoutToParameter" class right? Maybe Harbs should confirm this since
>>> he
>> implemented, and I just saw the class but still not use it.
>> 
>> 
>> El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>) escribió:
>> 
>>> Harbs,
>>> 
>>> Agreed with that. We can rename them, but even in case of HashRouter
>>> -
> does
>>> exclude it ability to have parameters ? Does those parameters not
> exists in
>>> HasRouter as well. Is it not a common stuff no matter what kind of
>>> url
> it
>>> is ?
>>> 
>>> niedz., 19 kwi 2020 o 15:52 Harbs 
>>> napisał(a):
>>> 
 After thinking about this some more, I’m thinking that Router
>>> should be
 named and we should add another type of router for standard path
> routing.
 
 React calls them HashRouter and BrowserRouter. Maybe we should use
>>> the
 same names…
 
 
> 
>>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
>>> <
 
> 
>>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
 
 
> On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com
 
 wrote:
> 
> Hi Harbs,
> 
> It sounds like you are asking me to check in onInit whether
> if(location.hash) exists then do something, but if doesn't exists
> check
 url
> params. - I may understand it in a wrong way, but I think
> location.hash
 may
> exists and location.search - where parameters are stored could
>>> exists
> equally.
> 
> if(location.hash)
> {
> hashChangeHandler();
> }
> 
> if (location.search)
> {
> parseParameters();
> }
> 
> Am I missing something ?
> 
> Thanks,
> Piotr
> 
> pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
> 
>> Whatever you think is fine by me.
>> 
>> I don’t remember why I have "if(location.hash)”. It’s possible you
> can
 get
>> rid of that conditional.
>> 
>> It could be you can get rid of that and 

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Harbs,

Do you think you will have something pushed today/tomorrow or is it rather
something for the next week or so ?

pon., 20 kwi 2020 o 11:56 Piotr Zarzycki 
napisał(a):

> Ok. Thanks I look forward to your update.
>
> pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):
>
>> I’m deprecating Router and replacing it with HashRouter and BrowserRouter.
>>
>> I’m going to try and keep the same beads working with either router.
>>
>> > On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki 
>> wrote:
>> >
>> > Harbs,
>> >
>> > What please describe what are you going to change exactly. Since I need
>> to
>> > move forward with my feature in application I will probably implement
>> > adhoc solution with Router in app only, but I would like to avoid some
>> big
>> > changes when you commit your code.
>> >
>> > Thanks,
>> > Piotr
>> >
>> > pon., 20 kwi 2020 o 09:52 Harbs > harbs.li...@gmail.com>> napisał(a):
>> >
>> >> There are beads which handle the following:
>> >>
>> >> 1. Paths — in a hash router, this would be the part of the url between
>> the
>> >> hash and the question mark or a second hash. In a “browser router” this
>> >> would be the section between the base and and the question mark or a
>> hash
>> >> 2. Parameters — handles between the question mark and subsequent hash.
>> >> (yes RouteToParameter works)
>> >> 3. I started work on dealing with trailing hash links for scrolling to
>> >> anchor (or rather id) behavior, but that’s not yet done. (Something
>> like
>> >> this:
>> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>>  <
>> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior
>> >)
>> >>
>> >> Ideally all of these beads should work in either kind of router. This
>> is
>> >> already PAYG, but it’s going to take some work to get this working and
>> PAYG
>> >> for both kinds of routers.
>> >>
>> >> I’ll try to work on this today…
>> >>
>> >> Harbs
>> >>
>> >>> On Apr 20, 2020, at 10:01 AM, Carlos Rovira 
>> >> wrote:
>> >>>
>> >>> Hi Piotr,
>> >>>
>> >>> I used hashes with params, so that's completely fine and we should
>> have
>> >> it.
>> >>> In fact, I think we already should have it since I'm seeing
>> >>> "RoutToParameter" class right? Maybe Harbs should confirm this since
>> he
>> >>> implemented, and I just saw the class but still not use it.
>> >>>
>> >>>
>> >>> El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
>> >>> piotrzarzyck...@gmail.com>) escribió:
>> >>>
>>  Harbs,
>> 
>>  Agreed with that. We can rename them, but even in case of HashRouter
>> -
>> >> does
>>  exclude it ability to have parameters ? Does those parameters not
>> >> exists in
>>  HasRouter as well. Is it not a common stuff no matter what kind of
>> url
>> >> it
>>  is ?
>> 
>>  niedz., 19 kwi 2020 o 15:52 Harbs 
>> napisał(a):
>> 
>> > After thinking about this some more, I’m thinking that Router
>> should be
>> > named and we should add another type of router for standard path
>> >> routing.
>> >
>> > React calls them HashRouter and BrowserRouter. Maybe we should use
>> the
>> > same names…
>> >
>> >
>> >>
>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
>>  <
>> >
>> >>
>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
>> >
>> >
>> >> On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki <
>> >> piotrzarzyck...@gmail.com
>> >
>> > wrote:
>> >>
>> >> Hi Harbs,
>> >>
>> >> It sounds like you are asking me to check in onInit whether
>> >> if(location.hash) exists then do something, but if doesn't exists
>> >> check
>> > url
>> >> params. - I may understand it in a wrong way, but I think
>> >> location.hash
>> > may
>> >> exists and location.search - where parameters are stored could
>> exists
>> >> equally.
>> >>
>> >> if(location.hash)
>> >> {
>> >> hashChangeHandler();
>> >> }
>> >>
>> >> if (location.search)
>> >> {
>> >> parseParameters();
>> >> }
>> >>
>> >> Am I missing something ?
>> >>
>> >> Thanks,
>> >> Piotr
>> >>
>> >> pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
>> >>
>> >>> Whatever you think is fine by me.
>> >>>
>> >>> I don’t remember why I have "if(location.hash)”. It’s possible you
>> >> can
>> > get
>> >>> rid of that conditional.
>> >>>
>> >>> It could be you can get rid of that and handle hashRecieved in a
>> >> bead.
>> > If
>> >>> the hashReceived event has no hash you can then check the URL.You
>> do
>> > need
>> >>> to make sure that you always get a stateChange event and don’t
>>  dispatch
>> > it
>> >>> twice.
>> >>>
>> >>> Feel free to play around with the code… ;-)
>> >>>
>> >>> Harbs
>> >>>
>> 

Release Step 011 Succeeded

[apacheroyaleci]

>From the royale-asjs repo:
1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.7 
-DskipTests=true
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_011_Sign 
-Drelease.version=0.9.7
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_011_Upload 
-Drelease.version=0.9.7
This will upload the signed artifacts to Maven Release Staging.  Verify that 
the compiler and typedefs artifacts are there along with the asjs artifacts, 
then hit the close to close the staging repo. (https://repository.apache.org/)

Build failed in Jenkins: royale-asjs_jsonly #1334

[apacheroyaleci]

See 


Changes:


--
[...truncated 1.71 MB...]

check-air-home:

check-compiler-home:

check-compile-env:
 [echo] OS: Windows Server 2016 / 10.0 / amd64
 [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.251-b08
 [echo] Java: 1.8.0_251
 [echo] Ant: Apache Ant(TM) version 1.9.9 compiled on February 2 2017 Ant 
Java Version: 1.8

prepare:

compile:

flat-ui-icons:
 [java] Error: Unable to access jarfile 

 [java] Java Result: 1

main:

main:

tweak-for-jsonly:
 [copy] Copying 1 file to 

 [copy] Copying 1 file to 


check-royale-config:

fixup-royale-config:

ide:

post-build:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

 [copy] Copying 1 file to 

 [copy] Copying 1 file to 

[touch] Creating 

[touch] Creating 

[touch] Creating 


last-message-if-airsdk:

main:
 [echo] ant main target completed on 04/20/2020 12:25:44 PM

sample-themes:

check-runtime-env:

runtime-setup:

mustella-setup:

load-task:

marmotinni-setup:

prepare:
 [echo] Making lib directory 
:\jenkins\workspace\royale-asjs_jsonly\marmotinni\java/lib
[mkdir] Created dir: 


selenium3-jar-check:

selenium3-jar:
[mkdir] Created dir: 


download-zip:
[mkdir] Created dir: 

  [get] Getting: https://bit.ly/2zm3ZzF
  [get] To: 

  [get] https://bit.ly/2zm3ZzF permanently moved to 
https://selenium-release.storage.googleapis.com/3.141/selenium-java-3.141.59.zip

untar-file:

unzip-file:
[unzip] Expanding: 

 into 


check-sum:

copy-downloaded-jar:
  [get] Getting: http://www.apache.org/licenses/LICENSE-2.0
  [get] To: 

 [copy] Copying 10 files to 


clean:

main:

clean:
   [delete] Deleting: 


check-compiler-home:

check-compiler:

compile:

compile-js:
 [echo] Compiling mustella.swc
 [echo] ROYALE_HOME: 

 [echo] ROYALE_COMPILER_HOME: 

 [java] args:
 [java] 
+royalelib=
 [java] +playerglobal.version=11.7
 [java] +env.PLAYERGLOBAL_HOME=${env.PLAYERGLOBAL_HOME}
 [java] -compiler.strict-xml=true
 [java] -compiler.targets=SWF,JSRoyale
 [java] 

Re: Repository for tutorials

[Andrew Wetmore]

I am not sure how that makes more complexity for end users. I would presume
that, once we have a set of tutorials, a site visitor would get to them
from the website by a single click. However, I take your larger point that
the docs repository can probably host all the tutorials we would like to
create.

a

On Mon, Apr 20, 2020 at 7:47 AM Carlos Rovira 
wrote:

> I was not aware that exists.
>
> IMHO, and as I said before, I don't think is worth it to have more repos
> and fronts open, we should do the opposite, since that means complexity for
> end users, and that means people not coming to Royale to stay.
>
> El lun., 20 abr. 2020 a las 10:53, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi,
> >
> > We have also [1] - maybe this is good candidate for changes etc.
> >
> > [1] https://github.com/apache/royale-tourjs
> >
> > pon., 20 kwi 2020 o 09:19 Carlos Rovira 
> > napisał(a):
> >
> > > Hi Andrew,
> > >
> > > I think "royale-docs" is a separated repository itself (from the main
> > > project) that should have all the learning material. That's docs, for
> > now,
> > > but your "Royale in a Week" project is ok for me in that place. Maybe
> is
> > > more about to expose/highlight it better in that royale-docs page with
> a
> > > banner or something as we have it and storing all of it in a concrete
> and
> > > organized subfolder of royale-docs repo.
> > >
> > > Royale docs could be as well hosting other tutorials and even the blog
> > > examples, so website turns to just a marketing face for the project.
> > >
> > > As you probably know, I'm investing some free time in looking to how to
> > > create a Royale App for it so we use our own, and was trying to make
> > royale
> > > load markdown from github, but it's turning a bit complicated, due to
> > > github using Kramdown and many other things. So maybe this is the
> > solution:
> > > migrate blog examples to royale-docs converting to mark-down and make
> > > website just center the website in trying to create a Royale web that
> > > centers in marketing and presentation of the technology.
> > >
> > > Another thing I expect for the future is decrease the repositories we
> > have,
> > > since I think we have many and that could be a bit cumbersome to people
> > > interested in Royale. One of the things I'd like before 1.0 is just 1
> > repo
> > > instead of 3 for (compiler,typedefs and framework), that will make for
> > sure
> > > a difference for people coming to Royale and will streamline lots of
> > things
> > > like builds and releases).
> > >
> > > Thanks
> > >
> > >
> > > El dom., 19 abr. 2020 a las 23:52, Andrew Wetmore (<
> cottag...@gmail.com
> > >)
> > > escribió:
> > >
> > > > Hi:
> > > >
> > > > Hi: I see that flink.apache.org has requested a separate git
> > repository
> > > > for
> > > > the self-directed learning modules they hope to deploy. As we move
> > closer
> > > > to Royale 1.0 it will become more important to have a suite of
> > tutorials
> > > to
> > > > extends the excellent how-tos @carlos has been posting on the blog..
> > > >
> > > > I have committed to creating Royale in a Week, which will have lots
> of
> > > > stuff to store: scripts, videos, code samples, transcripts, and so
> on.
> > > Can
> > > > we fit that all into the existing documentation repository? Or should
> > we
> > > > request a separate one?
> > > >
> > > > A
> > > >
> > > > --
> > > > Andrew Wetmore
> > > >
> > > > http://cottage14.blogspot.com/
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

RE: [royale-compiler] branch release/0.9.7 updated: Update compiler build tools version

[Yishay Weiss]

Carlos, are you sure your commit belongs in dev at this stage? If we are going 
to merge release into dev anyway, maybe it’s best to wait until then to avoid 
this conflict. Also, I’m not a Git expert, but wouldn’t the merge algorithm 
detect the identity in content anyway and avoid conflict?

From: Piotr Zarzycki
Sent: Monday, April 20, 2020 2:30 PM
To: Apache Royale Development
Subject: Re: [royale-compiler] branch release/0.9.7 updated: Update compiler 
build tools version

Agree with Carlos - It may end up with problems. Actually after release
branch should be probably just merged to develop and probably master (not
sure here) without changes.

pon., 20 kwi 2020 o 13:27 Carlos Rovira 
napisał(a):

> Hi Yishay,
>
> since I did the same in develop, will not be better to just cherry pick my
> commit on release branch?
> I think doing this way will make the merge to develop from release
> problematic since will find different changes (although are the same) and
> you'll need to resolve the merge manually.
>
> maybe I'm wrong
>
> Thanks
>
>
> El lun., 20 abr. 2020 a las 12:58,  escribió:
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > yishayw pushed a commit to branch release/0.9.7
> > in repository https://gitbox.apache.org/repos/asf/royale-compiler.git
> >
> >
> > The following commit(s) were added to refs/heads/release/0.9.7 by this
> > push:
> >  new 1b8f24a  Update compiler build tools version
> > 1b8f24a is described below
> >
> > commit 1b8f24aee6bf21d25ae75b039b88c00a596c46bb
> > Author: DESKTOP-RH4S838\Yishay 
> > AuthorDate: Mon Apr 20 13:58:20 2020 +0300
> >
> > Update compiler build tools version
> > ---
> >  pom.xml | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/pom.xml b/pom.xml
> > index 3fea91d..1ee3dd9 100644
> > --- a/pom.xml
> > +++ b/pom.xml
> > @@ -47,7 +47,7 @@
> >
> >
> UTF-8
> >  3.3.1
> >
> > -1.1.0
> > +1.2.0
> >  1.1.0
> >
> >  4.15.0
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


--

Piotr Zarzycki

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

Re: [royale-compiler] branch release/0.9.7 updated: Update compiler build tools version

[Piotr Zarzycki]

Agree with Carlos - It may end up with problems. Actually after release
branch should be probably just merged to develop and probably master (not
sure here) without changes.

pon., 20 kwi 2020 o 13:27 Carlos Rovira 
napisał(a):

> Hi Yishay,
>
> since I did the same in develop, will not be better to just cherry pick my
> commit on release branch?
> I think doing this way will make the merge to develop from release
> problematic since will find different changes (although are the same) and
> you'll need to resolve the merge manually.
>
> maybe I'm wrong
>
> Thanks
>
>
> El lun., 20 abr. 2020 a las 12:58,  escribió:
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > yishayw pushed a commit to branch release/0.9.7
> > in repository https://gitbox.apache.org/repos/asf/royale-compiler.git
> >
> >
> > The following commit(s) were added to refs/heads/release/0.9.7 by this
> > push:
> >  new 1b8f24a  Update compiler build tools version
> > 1b8f24a is described below
> >
> > commit 1b8f24aee6bf21d25ae75b039b88c00a596c46bb
> > Author: DESKTOP-RH4S838\Yishay 
> > AuthorDate: Mon Apr 20 13:58:20 2020 +0300
> >
> > Update compiler build tools version
> > ---
> >  pom.xml | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/pom.xml b/pom.xml
> > index 3fea91d..1ee3dd9 100644
> > --- a/pom.xml
> > +++ b/pom.xml
> > @@ -47,7 +47,7 @@
> >
> >
> UTF-8
> >  3.3.1
> >
> > -1.1.0
> > +1.2.0
> >  1.1.0
> >
> >  4.15.0
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

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

Re: [royale-compiler] branch release/0.9.7 updated: Update compiler build tools version

[Carlos Rovira]

Hi Yishay,

since I did the same in develop, will not be better to just cherry pick my
commit on release branch?
I think doing this way will make the merge to develop from release
problematic since will find different changes (although are the same) and
you'll need to resolve the merge manually.

maybe I'm wrong

Thanks


El lun., 20 abr. 2020 a las 12:58,  escribió:

> This is an automated email from the ASF dual-hosted git repository.
>
> yishayw pushed a commit to branch release/0.9.7
> in repository https://gitbox.apache.org/repos/asf/royale-compiler.git
>
>
> The following commit(s) were added to refs/heads/release/0.9.7 by this
> push:
>  new 1b8f24a  Update compiler build tools version
> 1b8f24a is described below
>
> commit 1b8f24aee6bf21d25ae75b039b88c00a596c46bb
> Author: DESKTOP-RH4S838\Yishay 
> AuthorDate: Mon Apr 20 13:58:20 2020 +0300
>
> Update compiler build tools version
> ---
>  pom.xml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/pom.xml b/pom.xml
> index 3fea91d..1ee3dd9 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -47,7 +47,7 @@
>
>  UTF-8
>  3.3.1
>
> -1.1.0
> +1.2.0
>  1.1.0
>
>  4.15.0
>
>

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

RE: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

[Yishay Weiss]

Thanks for explaining.


From: Carlos Rovira 
Sent: Monday, April 20, 2020 9:55:13 AM
To: Apache Royale Development 
Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

ok Yishay,

now I see it in central :)

about your question on why we should use 1.2.0. Maven has build tools as an
artifact, so using 1.1.0 will make people using the old source code no
matter what you have in source. That is one of the features of Maven that
all artifacts and its versions are officially stored in a central repo so
all people knows that they are using the right bits. If you build with Ant,
that will work since Ant just build from the sources you have and does not
have a concept of dependencies coming from a trusted source.

In this particular case the fix introduced in 1.2.0 was to make
reproducible builds working (or at least is needed for that, since that is
still to be checked if that works), along other fixes in compiler.

Thanks




El dom., 19 abr. 2020 a las 19:37, Yishay Weiss ()
escribió:

> Turns out my public key needed to be distributed to a keyserver.
>
>
>
> gpg --keyserver http://keyserver.ubuntu.com --send-keys 
>
>
>
> did the trick. You should see it now.
>
>
>
>
>
>
>
> *From:* Yishay Weiss 
> *Sent:* Sunday, April 19, 2020 5:22:56 PM
> *To:* dev@royale.apache.org 
> *Subject:* RE: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
>
>
>
> Thanks for spotting that. It looks like it failed signature validation on
> releasing the folder, even though it had passed it when closing the folder.
> I’ll see if I can figure this out…
>
> From: Carlos Rovira >
> Sent: Sunday, April 19, 2020 5:12 PM
> To: Apache Royale Development >
> Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
>
> I think 1.2.0 must be pushed to maven central
>
>
> https://search.maven.org/artifact/org.apache.royale.compiler/compiler-build-tools
>
> El dom., 19 abr. 2020 a las 16:10, Carlos Rovira ( >)
> escribió:
>
> > Ok Yishay,
> >
> > and is this version used in current 0.9.7 ongoing release process?
> >
> > thanks
> >
> >
> >
> > El dom., 19 abr. 2020 a las 15:37, Yishay Weiss ( >)
> > escribió:
> >
> >> Hi Carlos,
> >>
> >> It’s already been released, just haven’t announced it yet.
> >>
> >> From: Carlos Rovira >
> >> Sent: Sunday, April 19, 2020 4:12 PM
> >> To: Apache Royale Development >
> >> Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
> >>
> >> Hi
> >>
> >> can we consider this vote finished?
> >>
> >> also, I think current main release is not using this 1.2.0 right? so the
> >> fixes will be not applied
> >>
> >> Maybe I'm wrong
> >>
> >> Thanks
> >>
> >>
> >>
> >> El mié., 15 abr. 2020 a las 23:05, Harbs ()
> >> escribió:
> >>
> >> > I’m not going to have the time to look at this before the 72 hours are
> >> > over, so here’s my official +0 vote… ;-)
> >> >
> >> > Harbs
> >> >
> >> > > On Apr 13, 2020, at 11:25 PM, apacheroyal...@gmail.com wrote:
> >> > >
> >> > > Hi,
> >> > > This is the vote for the 1.2.0 release of Apache Royale Compiler
> Build
> >> > Tools.  The release candidate can be found here;
> >> > >
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/
> >> > >
> >> > > Before voting please review the section,'What are the ASF
> requirements
> >> > on approving a release?', at:
> >> > > http://www.apache.org/dev/release.html#approving-a-release
> >> > >
> >> > > At a minimum you would be expected to check that:
> >> > > - SHA and signed packages are correct
> >> > > - NOTICE and LICENSE files are all fine
> >> > > - That "mvn clean install" in the root of the source package
> completes
> >> > successfully
> >> > > - That you can modify other compiler poms to use that version of
> >> > compiler-build-tools and build the compiler.
> >> > >
> >> > > The KEYS file is at
> >> > https://dist.apache.org/repos/dist/release/royale/KEYS
> >> > >
> >> > > Maven artifacts are staged here:
> >> > >
> >> https://repository.apache.org/content/repositories/orgapacheroyale-1064
> >> > >
> >> > > Please vote to approve this release:
> >> > > +1 Approve the release
> >> > > -1 Disapprove the release (please provide specific comments to why)
> >> > >
> >> > > This vote will be open for 72 hours or until a result can be called.
> >> > >
> >> > > The vote passes if there is:
> >> > > - At least 3 +1 votes from the PMC
> >> > > - More positive votes than negative votes
> >> > >
> >> > > Remember that this is a 'beta-quality' release so expect there will
> be
> >> > many bugs found. IMO the goal is not to try to find and fix bugs in
> the
> >> RC,
> >> > but to make sure we have the packaging right, and enough functionality
> >> that
> >> > folks will have some success trying to use it.  People who are not in
> >> PMC
> >> > are also encouraged to test out the release and vote, 

Re: Separate mailing list for Jenkins notifications

[Andrew Wetmore]

I think this is a good idea. Let's give it a generic name like "notif" or
something so we can use it for other automated senders besides Jenkins, as
we run into them.

a

On Mon, Apr 20, 2020 at 5:53 AM Piotr Zarzycki 
wrote:

> Hi Guys,
>
> In the last year or so all notifications from Jenkins build are going to
> development mailing list. It becomes very messy I see every day 40-50
> emails where 80% of that is notification from Jenkins.
>
> I would like to propose create separate mailing list to have such
> notifications there.
>
> Is it possible?
>
> Please share your thoughts on that subject.
>
> Thanks,
> --
>
> Piotr Zarzycki
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Repository for tutorials

[Carlos Rovira]

I was not aware that exists.

IMHO, and as I said before, I don't think is worth it to have more repos
and fronts open, we should do the opposite, since that means complexity for
end users, and that means people not coming to Royale to stay.

El lun., 20 abr. 2020 a las 10:53, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi,
>
> We have also [1] - maybe this is good candidate for changes etc.
>
> [1] https://github.com/apache/royale-tourjs
>
> pon., 20 kwi 2020 o 09:19 Carlos Rovira 
> napisał(a):
>
> > Hi Andrew,
> >
> > I think "royale-docs" is a separated repository itself (from the main
> > project) that should have all the learning material. That's docs, for
> now,
> > but your "Royale in a Week" project is ok for me in that place. Maybe is
> > more about to expose/highlight it better in that royale-docs page with a
> > banner or something as we have it and storing all of it in a concrete and
> > organized subfolder of royale-docs repo.
> >
> > Royale docs could be as well hosting other tutorials and even the blog
> > examples, so website turns to just a marketing face for the project.
> >
> > As you probably know, I'm investing some free time in looking to how to
> > create a Royale App for it so we use our own, and was trying to make
> royale
> > load markdown from github, but it's turning a bit complicated, due to
> > github using Kramdown and many other things. So maybe this is the
> solution:
> > migrate blog examples to royale-docs converting to mark-down and make
> > website just center the website in trying to create a Royale web that
> > centers in marketing and presentation of the technology.
> >
> > Another thing I expect for the future is decrease the repositories we
> have,
> > since I think we have many and that could be a bit cumbersome to people
> > interested in Royale. One of the things I'd like before 1.0 is just 1
> repo
> > instead of 3 for (compiler,typedefs and framework), that will make for
> sure
> > a difference for people coming to Royale and will streamline lots of
> things
> > like builds and releases).
> >
> > Thanks
> >
> >
> > El dom., 19 abr. 2020 a las 23:52, Andrew Wetmore ( >)
> > escribió:
> >
> > > Hi:
> > >
> > > Hi: I see that flink.apache.org has requested a separate git
> repository
> > > for
> > > the self-directed learning modules they hope to deploy. As we move
> closer
> > > to Royale 1.0 it will become more important to have a suite of
> tutorials
> > to
> > > extends the excellent how-tos @carlos has been posting on the blog..
> > >
> > > I have committed to creating Royale in a Week, which will have lots of
> > > stuff to store: scripts, videos, code samples, transcripts, and so on.
> > Can
> > > we fit that all into the existing documentation repository? Or should
> we
> > > request a separate one?
> > >
> > > A
> > >
> > > --
> > > Andrew Wetmore
> > >
> > > http://cottage14.blogspot.com/
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


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

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Ok. Thanks I look forward to your update.

pon., 20 kwi 2020 o 11:51 Harbs  napisał(a):

> I’m deprecating Router and replacing it with HashRouter and BrowserRouter.
>
> I’m going to try and keep the same beads working with either router.
>
> > On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki 
> wrote:
> >
> > Harbs,
> >
> > What please describe what are you going to change exactly. Since I need
> to
> > move forward with my feature in application I will probably implement
> > adhoc solution with Router in app only, but I would like to avoid some
> big
> > changes when you commit your code.
> >
> > Thanks,
> > Piotr
> >
> > pon., 20 kwi 2020 o 09:52 Harbs  harbs.li...@gmail.com>> napisał(a):
> >
> >> There are beads which handle the following:
> >>
> >> 1. Paths — in a hash router, this would be the part of the url between
> the
> >> hash and the question mark or a second hash. In a “browser router” this
> >> would be the section between the base and and the question mark or a
> hash
> >> 2. Parameters — handles between the question mark and subsequent hash.
> >> (yes RouteToParameter works)
> >> 3. I started work on dealing with trailing hash links for scrolling to
> >> anchor (or rather id) behavior, but that’s not yet done. (Something like
> >> this:
> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior <
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior> <
> >> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior <
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior>>)
> >>
> >> Ideally all of these beads should work in either kind of router. This is
> >> already PAYG, but it’s going to take some work to get this working and
> PAYG
> >> for both kinds of routers.
> >>
> >> I’ll try to work on this today…
> >>
> >> Harbs
> >>
> >>> On Apr 20, 2020, at 10:01 AM, Carlos Rovira 
> >> wrote:
> >>>
> >>> Hi Piotr,
> >>>
> >>> I used hashes with params, so that's completely fine and we should have
> >> it.
> >>> In fact, I think we already should have it since I'm seeing
> >>> "RoutToParameter" class right? Maybe Harbs should confirm this since he
> >>> implemented, and I just saw the class but still not use it.
> >>>
> >>>
> >>> El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
> >>> piotrzarzyck...@gmail.com>) escribió:
> >>>
>  Harbs,
> 
>  Agreed with that. We can rename them, but even in case of HashRouter -
> >> does
>  exclude it ability to have parameters ? Does those parameters not
> >> exists in
>  HasRouter as well. Is it not a common stuff no matter what kind of url
> >> it
>  is ?
> 
>  niedz., 19 kwi 2020 o 15:52 Harbs  napisał(a):
> 
> > After thinking about this some more, I’m thinking that Router should
> be
> > named and we should add another type of router for standard path
> >> routing.
> >
> > React calls them HashRouter and BrowserRouter. Maybe we should use
> the
> > same names…
> >
> >
> >>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
>  <
> >
> >>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> >
> >
> >> On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com
> >
> > wrote:
> >>
> >> Hi Harbs,
> >>
> >> It sounds like you are asking me to check in onInit whether
> >> if(location.hash) exists then do something, but if doesn't exists
> >> check
> > url
> >> params. - I may understand it in a wrong way, but I think
> >> location.hash
> > may
> >> exists and location.search - where parameters are stored could
> exists
> >> equally.
> >>
> >> if(location.hash)
> >> {
> >> hashChangeHandler();
> >> }
> >>
> >> if (location.search)
> >> {
> >> parseParameters();
> >> }
> >>
> >> Am I missing something ?
> >>
> >> Thanks,
> >> Piotr
> >>
> >> pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
> >>
> >>> Whatever you think is fine by me.
> >>>
> >>> I don’t remember why I have "if(location.hash)”. It’s possible you
> >> can
> > get
> >>> rid of that conditional.
> >>>
> >>> It could be you can get rid of that and handle hashRecieved in a
> >> bead.
> > If
> >>> the hashReceived event has no hash you can then check the URL.You
> do
> > need
> >>> to make sure that you always get a stateChange event and don’t
>  dispatch
> > it
> >>> twice.
> >>>
> >>> Feel free to play around with the code… ;-)
> >>>
> >>> Harbs
> >>>
>  On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> >>> wrote:
> 
>  I think it would be better to have it here in Router.
> 
>  pt., 17 kwi 2020 o 09:37 Harbs 
> napisał(a):
> 
> > Alternatively, you can subclass Router to support setting the
> > parameters

Re: Routing (was Re: Spectrum Components)

[Harbs]

I’m deprecating Router and replacing it with HashRouter and BrowserRouter.

I’m going to try and keep the same beads working with either router.

> On Apr 20, 2020, at 11:55 AM, Piotr Zarzycki  
> wrote:
> 
> Harbs,
> 
> What please describe what are you going to change exactly. Since I need to
> move forward with my feature in application I will probably implement
> adhoc solution with Router in app only, but I would like to avoid some big
> changes when you commit your code.
> 
> Thanks,
> Piotr
> 
> pon., 20 kwi 2020 o 09:52 Harbs  > napisał(a):
> 
>> There are beads which handle the following:
>> 
>> 1. Paths — in a hash router, this would be the part of the url between the
>> hash and the question mark or a second hash. In a “browser router” this
>> would be the section between the base and and the question mark or a hash
>> 2. Parameters — handles between the question mark and subsequent hash.
>> (yes RouteToParameter works)
>> 3. I started work on dealing with trailing hash links for scrolling to
>> anchor (or rather id) behavior, but that’s not yet done. (Something like
>> this:
>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior 
>>  <
>> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior 
>> >)
>> 
>> Ideally all of these beads should work in either kind of router. This is
>> already PAYG, but it’s going to take some work to get this working and PAYG
>> for both kinds of routers.
>> 
>> I’ll try to work on this today…
>> 
>> Harbs
>> 
>>> On Apr 20, 2020, at 10:01 AM, Carlos Rovira 
>> wrote:
>>> 
>>> Hi Piotr,
>>> 
>>> I used hashes with params, so that's completely fine and we should have
>> it.
>>> In fact, I think we already should have it since I'm seeing
>>> "RoutToParameter" class right? Maybe Harbs should confirm this since he
>>> implemented, and I just saw the class but still not use it.
>>> 
>>> 
>>> El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
>>> piotrzarzyck...@gmail.com>) escribió:
>>> 
 Harbs,
 
 Agreed with that. We can rename them, but even in case of HashRouter -
>> does
 exclude it ability to have parameters ? Does those parameters not
>> exists in
 HasRouter as well. Is it not a common stuff no matter what kind of url
>> it
 is ?
 
 niedz., 19 kwi 2020 o 15:52 Harbs  napisał(a):
 
> After thinking about this some more, I’m thinking that Router should be
> named and we should add another type of router for standard path
>> routing.
> 
> React calls them HashRouter and BrowserRouter. Maybe we should use the
> same names…
> 
> 
>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
 <
> 
>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> 
> 
>> On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com
> 
> wrote:
>> 
>> Hi Harbs,
>> 
>> It sounds like you are asking me to check in onInit whether
>> if(location.hash) exists then do something, but if doesn't exists
>> check
> url
>> params. - I may understand it in a wrong way, but I think
>> location.hash
> may
>> exists and location.search - where parameters are stored could exists
>> equally.
>> 
>> if(location.hash)
>> {
>> hashChangeHandler();
>> }
>> 
>> if (location.search)
>> {
>> parseParameters();
>> }
>> 
>> Am I missing something ?
>> 
>> Thanks,
>> Piotr
>> 
>> pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
>> 
>>> Whatever you think is fine by me.
>>> 
>>> I don’t remember why I have "if(location.hash)”. It’s possible you
>> can
> get
>>> rid of that conditional.
>>> 
>>> It could be you can get rid of that and handle hashRecieved in a
>> bead.
> If
>>> the hashReceived event has no hash you can then check the URL.You do
> need
>>> to make sure that you always get a stateChange event and don’t
 dispatch
> it
>>> twice.
>>> 
>>> Feel free to play around with the code… ;-)
>>> 
>>> Harbs
>>> 
 On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
>>> wrote:
 
 I think it would be better to have it here in Router.
 
 pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
 
> Alternatively, you can subclass Router to support setting the
> parameters
> in the onInit method.
> 
> Not sure which of these is best.
> 
>> On Apr 17, 2020, at 10:35 AM, Harbs 
>> wrote:
>> 
>> Actually, it’s not going to work because the
> router.routeState.parameters will not be set.
>> 
>> You will likely need to add code to set the

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Harbs,

What please describe what are you going to change exactly. Since I need to
move forward with my feature in application I will probably implement
adhoc solution with Router in app only, but I would like to avoid some big
changes when you commit your code.

Thanks,
Piotr

pon., 20 kwi 2020 o 09:52 Harbs  napisał(a):

> There are beads which handle the following:
>
> 1. Paths — in a hash router, this would be the part of the url between the
> hash and the question mark or a second hash. In a “browser router” this
> would be the section between the base and and the question mark or a hash
> 2. Parameters — handles between the question mark and subsequent hash.
> (yes RouteToParameter works)
> 3. I started work on dealing with trailing hash links for scrolling to
> anchor (or rather id) behavior, but that’s not yet done. (Something like
> this:
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior <
> https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior>)
>
> Ideally all of these beads should work in either kind of router. This is
> already PAYG, but it’s going to take some work to get this working and PAYG
> for both kinds of routers.
>
> I’ll try to work on this today…
>
> Harbs
>
> > On Apr 20, 2020, at 10:01 AM, Carlos Rovira 
> wrote:
> >
> > Hi Piotr,
> >
> > I used hashes with params, so that's completely fine and we should have
> it.
> > In fact, I think we already should have it since I'm seeing
> > "RoutToParameter" class right? Maybe Harbs should confirm this since he
> > implemented, and I just saw the class but still not use it.
> >
> >
> > El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> >> Harbs,
> >>
> >> Agreed with that. We can rename them, but even in case of HashRouter -
> does
> >> exclude it ability to have parameters ? Does those parameters not
> exists in
> >> HasRouter as well. Is it not a common stuff no matter what kind of url
> it
> >> is ?
> >>
> >> niedz., 19 kwi 2020 o 15:52 Harbs  napisał(a):
> >>
> >>> After thinking about this some more, I’m thinking that Router should be
> >>> named and we should add another type of router for standard path
> routing.
> >>>
> >>> React calls them HashRouter and BrowserRouter. Maybe we should use the
> >>> same names…
> >>>
> >>>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> >> <
> >>>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> >>>
> >>>
>  On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com
> >>>
> >>> wrote:
> 
>  Hi Harbs,
> 
>  It sounds like you are asking me to check in onInit whether
>  if(location.hash) exists then do something, but if doesn't exists
> check
> >>> url
>  params. - I may understand it in a wrong way, but I think
> location.hash
> >>> may
>  exists and location.search - where parameters are stored could exists
>  equally.
> 
>  if(location.hash)
>  {
>  hashChangeHandler();
>  }
> 
>  if (location.search)
>  {
>   parseParameters();
>  }
> 
>  Am I missing something ?
> 
>  Thanks,
>  Piotr
> 
>  pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
> 
> > Whatever you think is fine by me.
> >
> > I don’t remember why I have "if(location.hash)”. It’s possible you
> can
> >>> get
> > rid of that conditional.
> >
> > It could be you can get rid of that and handle hashRecieved in a
> bead.
> >>> If
> > the hashReceived event has no hash you can then check the URL.You do
> >>> need
> > to make sure that you always get a stateChange event and don’t
> >> dispatch
> >>> it
> > twice.
> >
> > Feel free to play around with the code… ;-)
> >
> > Harbs
> >
> >> On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> >>> piotrzarzyck...@gmail.com>
> > wrote:
> >>
> >> I think it would be better to have it here in Router.
> >>
> >> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >>
> >>> Alternatively, you can subclass Router to support setting the
> >>> parameters
> >>> in the onInit method.
> >>>
> >>> Not sure which of these is best.
> >>>
>  On Apr 17, 2020, at 10:35 AM, Harbs 
> wrote:
> 
>  Actually, it’s not going to work because the
> >>> router.routeState.parameters will not be set.
> 
>  You will likely need to add code to set the
> > router.routeState.parameters
> >>> using the part of the location after the question mark.
> 
>  The easiest way to do that would be to either:
>  1. Modify RouteToParameters.stateChanged to first check that there
> >>> is a
> >>> parameters value and then set it if not.
>  2. Subclass RouteToParameters and override stateChanged to make
> >> that
> >>> check first.
> 
> > On Apr 17, 2020, at 10:29 AM, Harbs  >>  >>> 

Re: Repository for tutorials

[Piotr Zarzycki]

Hi,

We have also [1] - maybe this is good candidate for changes etc.

[1] https://github.com/apache/royale-tourjs

pon., 20 kwi 2020 o 09:19 Carlos Rovira 
napisał(a):

> Hi Andrew,
>
> I think "royale-docs" is a separated repository itself (from the main
> project) that should have all the learning material. That's docs, for now,
> but your "Royale in a Week" project is ok for me in that place. Maybe is
> more about to expose/highlight it better in that royale-docs page with a
> banner or something as we have it and storing all of it in a concrete and
> organized subfolder of royale-docs repo.
>
> Royale docs could be as well hosting other tutorials and even the blog
> examples, so website turns to just a marketing face for the project.
>
> As you probably know, I'm investing some free time in looking to how to
> create a Royale App for it so we use our own, and was trying to make royale
> load markdown from github, but it's turning a bit complicated, due to
> github using Kramdown and many other things. So maybe this is the solution:
> migrate blog examples to royale-docs converting to mark-down and make
> website just center the website in trying to create a Royale web that
> centers in marketing and presentation of the technology.
>
> Another thing I expect for the future is decrease the repositories we have,
> since I think we have many and that could be a bit cumbersome to people
> interested in Royale. One of the things I'd like before 1.0 is just 1 repo
> instead of 3 for (compiler,typedefs and framework), that will make for sure
> a difference for people coming to Royale and will streamline lots of things
> like builds and releases).
>
> Thanks
>
>
> El dom., 19 abr. 2020 a las 23:52, Andrew Wetmore ()
> escribió:
>
> > Hi:
> >
> > Hi: I see that flink.apache.org has requested a separate git repository
> > for
> > the self-directed learning modules they hope to deploy. As we move closer
> > to Royale 1.0 it will become more important to have a suite of tutorials
> to
> > extends the excellent how-tos @carlos has been posting on the blog..
> >
> > I have committed to creating Royale in a Week, which will have lots of
> > stuff to store: scripts, videos, code samples, transcripts, and so on.
> Can
> > we fit that all into the existing documentation repository? Or should we
> > request a separate one?
> >
> > A
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

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

Separate mailing list for Jenkins notifications

[Piotr Zarzycki]

Hi Guys,

In the last year or so all notifications from Jenkins build are going to
development mailing list. It becomes very messy I see every day 40-50
emails where 80% of that is notification from Jenkins.

I would like to propose create separate mailing list to have such
notifications there.

Is it possible?

Please share your thoughts on that subject.

Thanks,
-- 

Piotr Zarzycki

Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

[Piotr Zarzycki]

Yishay,

Good example is also an application. When you have Royale application and
wanted you to build it by ANT and Maven on a completely clean PC, fresh
windows installation.

In case of ANT you need to download Apache Royale SDK and point to it in
your script.

In case of Maven you need to tell where ARTIFACTS are (in Maven
settings.xml) and type "mvn package" in console - this will download and
build everything what is needed for application.

Thanks,
Piotr

pon., 20 kwi 2020 o 09:03 Carlos Rovira 
napisał(a):

> ok Yishay,
>
> now I see it in central :)
>
> about your question on why we should use 1.2.0. Maven has build tools as an
> artifact, so using 1.1.0 will make people using the old source code no
> matter what you have in source. That is one of the features of Maven that
> all artifacts and its versions are officially stored in a central repo so
> all people knows that they are using the right bits. If you build with Ant,
> that will work since Ant just build from the sources you have and does not
> have a concept of dependencies coming from a trusted source.
>
> In this particular case the fix introduced in 1.2.0 was to make
> reproducible builds working (or at least is needed for that, since that is
> still to be checked if that works), along other fixes in compiler.
>
> Thanks
>
>
>
>
> El dom., 19 abr. 2020 a las 19:37, Yishay Weiss ()
> escribió:
>
> > Turns out my public key needed to be distributed to a keyserver.
> >
> >
> >
> > gpg --keyserver http://keyserver.ubuntu.com --send-keys 
> >
> >
> >
> > did the trick. You should see it now.
> >
> >
> >
> >
> >
> >
> >
> > *From:* Yishay Weiss 
> > *Sent:* Sunday, April 19, 2020 5:22:56 PM
> > *To:* dev@royale.apache.org 
> > *Subject:* RE: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
> >
> >
> >
> > Thanks for spotting that. It looks like it failed signature validation on
> > releasing the folder, even though it had passed it when closing the
> folder.
> > I’ll see if I can figure this out…
> >
> > From: Carlos Rovira > >
> > Sent: Sunday, April 19, 2020 5:12 PM
> > To: Apache Royale Development > >
> > Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
> >
> > I think 1.2.0 must be pushed to maven central
> >
> >
> >
> https://search.maven.org/artifact/org.apache.royale.compiler/compiler-build-tools
> >
> > El dom., 19 abr. 2020 a las 16:10, Carlos Rovira (<
> carlosrov...@apache.org
> > >)
> > escribió:
> >
> > > Ok Yishay,
> > >
> > > and is this version used in current 0.9.7 ongoing release process?
> > >
> > > thanks
> > >
> > >
> > >
> > > El dom., 19 abr. 2020 a las 15:37, Yishay Weiss (<
> yishayj...@hotmail.com
> > >)
> > > escribió:
> > >
> > >> Hi Carlos,
> > >>
> > >> It’s already been released, just haven’t announced it yet.
> > >>
> > >> From: Carlos Rovira > >
> > >> Sent: Sunday, April 19, 2020 4:12 PM
> > >> To: Apache Royale Development > >
> > >> Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
> > >>
> > >> Hi
> > >>
> > >> can we consider this vote finished?
> > >>
> > >> also, I think current main release is not using this 1.2.0 right? so
> the
> > >> fixes will be not applied
> > >>
> > >> Maybe I'm wrong
> > >>
> > >> Thanks
> > >>
> > >>
> > >>
> > >> El mié., 15 abr. 2020 a las 23:05, Harbs ()
> > >> escribió:
> > >>
> > >> > I’m not going to have the time to look at this before the 72 hours
> are
> > >> > over, so here’s my official +0 vote… ;-)
> > >> >
> > >> > Harbs
> > >> >
> > >> > > On Apr 13, 2020, at 11:25 PM, apacheroyal...@gmail.com wrote:
> > >> > >
> > >> > > Hi,
> > >> > > This is the vote for the 1.2.0 release of Apache Royale Compiler
> > Build
> > >> > Tools.  The release candidate can be found here;
> > >> > >
> > >> >
> > >>
> >
> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/
> > >> > >
> > >> > > Before voting please review the section,'What are the ASF
> > requirements
> > >> > on approving a release?', at:
> > >> > > http://www.apache.org/dev/release.html#approving-a-release
> > >> > >
> > >> > > At a minimum you would be expected to check that:
> > >> > > - SHA and signed packages are correct
> > >> > > - NOTICE and LICENSE files are all fine
> > >> > > - That "mvn clean install" in the root of the source package
> > completes
> > >> > successfully
> > >> > > - That you can modify other compiler poms to use that version of
> > >> > compiler-build-tools and build the compiler.
> > >> > >
> > >> > > The KEYS file is at
> > >> > https://dist.apache.org/repos/dist/release/royale/KEYS
> > >> > >
> > >> > > Maven artifacts are staged here:
> > >> > >
> > >>
> https://repository.apache.org/content/repositories/orgapacheroyale-1064
> > >> > >
> > >> > > Please vote to approve this release:
> > >> > > +1 Approve the release
> > >> > > -1 Disapprove the release (please provide specific comments 

How did you folks get past step 007?

[Christofer Dutz]

Hi all,

so as I saw you’re at one of the steps in the framework repo, I thought: “How 
on earth did they get past 007?”
So I dug up the email, set my java version to the same as on the server and ran 
the scripts …

ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7 
-DskipTests=true

and the step failed with exactly the same error message as our attempts did:

notlast:
compare_files:
 [echo] comparing royale-typedefs-node-0.9.7-typedefs.swc
BUILD FAILED
/Users/christofer.dutz/Projects/Apache/Royale/royale/royale-typedefs/releasesteps.xml:167:
 The following error occurred while executing this line:
/Users/christofer.dutz/Projects/Apache/Royale/royale/royale-typedefs/releasesteps.xml:185:
 The following error occurred while executing this line:
/Users/christofer.dutz/Projects/Apache/Royale/royale/royale-typedefs/releasesteps.xml:196:
 The following error occurred while executing this line:
/Users/christofer.dutz/Projects/Apache/Royale/royale/royale-typedefs/releasesteps.xml:232:
 royale-typedefs-node-0.9.7-typedefs.swc does not match
Total time: 1 minute 21 seconds

Even the differences were identical to mine (except that the timecode 
differences seem to have been fixed or have gone away till the next time our 
daylight-saving time is out of sync again)

So I thought: “Ok so this just used the release version of the compiler that I 
created, so let’s update that to the one you folks staged”.
So I ran:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.7
and
ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.7 
-DskipTests=true
after the first, so I was using the same compiler version. But it still failed.

When comparing the swcs of the node typedef IntelliJ tells me that the 
catalog.xml of the node module built on the CI server contains a “http” script 
(class) and the one built locally contains a “net” instead.
However the problem with the changed order of properties in the library.swc 
seems to have been fixed by latest changes in the compiler.

So I thought … ok … let me check the others (the ant script aborts after the 
first error).
And the “js” typedef has more differences:

  *   The SHA-256 checksums differ
  *   Document.cookie is String when built locally but was Object when built on 
the CI server
  *   The number after the $ sign for quite some subclasses differs.
I gave up after that.

So I can’t really see this is a reproducible build.

However I don’t think they have to be, but if you insist on reproducible build, 
I think they should be reproducible for anyone or they aren’t worth being 
called “reproducible”.

Chris

Re: Problems to create AS3 externs when JS library returns some kind of object

[Carlos Rovira]

Hi Josh,

just let you know that here [1] I used your approach for "markdown-it" js
library and seems to work fine.
So I still think we have some issue since the same didn't worked for
"marked" library (or maybe I did something wrong at that time).

But my guess is "markdownit" is class that can be instantiated in AS3 while
"marked" is a function (or at least I couldn't create as a class) but
library has function methods that can be applied in an AS3 way.

Anyway don't want to make you spend time on this, just want to expose here
so we can refer to it if this issue comes up again at a later time.

Thanks

[1]
https://github.com/apache/royale-asjs/tree/develop/examples/jewel/royale-website/src/main/royale

El sáb., 18 abr. 2020 a las 1:09, Carlos Rovira ()
escribió:

> Hi Josh,
>
> that's right I could be doing something wrong. What I really don't
> understand is how setOptions can apply to a concrete marked object.
> that's what I could not make it work, and I was supposing that was due to
> the fact that is just a function, not a class, since to make a class I
> can't have a method "marked" (that get 3 params and returns a string)
> because "marked" is will be the reserved word for the constructor.
>
> Although if you say me you got this working I'll try again as I have some
> time.
>
> Thanks Josh
>
>
>
> El vie., 17 abr. 2020 a las 23:53, Josh Tynjala (<
> joshtynj...@bowlerhat.dev>) escribió:
>
>> To be clear, I have successfully used the approach that I suggested with
>> other libraries.
>>
>> Have you tried calling marked["setOptions"]() instead? I think that you
>> should rule out the possibility that you were using the API incorrectly.
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC 
>>
>>
>> On Fri, Apr 17, 2020 at 2:40 PM Carlos Rovira 
>> wrote:
>>
>> > Hi Josh,
>> >
>> > I already tried that approach (without the highlighter to avoid
>> > complexity), and was not working.
>> > I think what's happening is "marked" is not a class is just a function
>> that
>> > gets a string and returns a string, so a instance is created and
>> destroyed
>> > each time, but we are not able to store in a var or use "setOptions" to
>> > affect that instance and then pass a string and get the new string.
>> >
>> > As I said I think we have a problem here or a limitation. Or at least is
>> > what it seems to me.
>> >
>> > I was able to use other library (markdown-it) and for now I was able in
>> > that one to apply configurations, still trying, but seems that one is
>> > modeled in a "royale compatible way", but I think Royale should be able
>> to
>> > use any js lib out there to be really a js solution.
>> >
>> > Thanks for the suggestion and for taking a look :)
>> >
>> > Carlos
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > El vie., 17 abr. 2020 a las 19:24, Josh Tynjala (<
>> > joshtynj...@bowlerhat.dev>)
>> > escribió:
>> >
>> > > You may be able to do something like this instead:
>> > >
>> > > import marked.setOptions;
>> > > import marked.Renderer;
>> > >
>> > > setOptions({
>> > >   renderer: new Renderer(),
>> > >   highlight: function(code, language) {
>> > > const hljs = require('highlight.js');
>> > > const validLanguage = hljs.getLanguage(language) ? language :
>> > > 'plaintext';
>> > > return hljs.highlight(validLanguage, code).value;
>> > >   },
>> > >   pedantic: false,
>> > >   gfm: true,
>> > >   breaks: false,
>> > >   sanitize: false,
>> > >   smartLists: true,
>> > >   smartypants: false,
>> > >   xhtml: false
>> > > });
>> > >
>> > > console.log(marked(markdownString));
>> > >
>> > >
>> > > --
>> > > Josh Tynjala
>> > > Bowler Hat LLC 
>> > >
>> > >
>> > > On Fri, Apr 17, 2020 at 9:54 AM Carlos Rovira <
>> carlosrov...@apache.org>
>> > > wrote:
>> > >
>> > > > Hi,
>> > > >
>> > > > I think we have some kind of limitation. trying multiple ways with
>> the
>> > > > "marked" js library and I couldn't objects in the marked library (
>> > > > 'setOptions' and the 'Renderer').
>> > > >
>> > > > I was able just to declare as a function:
>> > > >
>> > > > package
>> > > > {
>> > > > /**
>> > > > * @externs
>> > > > */
>> > > > COMPILE::JS
>> > > > public function marked(s:String):String {
>> > > > return null;
>> > > > };
>> > > > }
>> > > >
>> > > > but creating package "marked" and creating "setOptions" and
>> "Renderer"
>> > as
>> > > > functions in that package was not working for me
>> > > >
>> > > > following library spec I'll need to create an object like this:
>> > > >
>> > > > options = {
>> > > > renderer: new marked.Renderer(),
>> > > > pedantic: false,
>> > > > gfm: true,
>> > > > breaks: false,
>> > > > sanitize: false,
>> > > > smartLists: true,
>> > > > smartypants: false,
>> > > > xhtml: false
>> > > > };
>> > > >
>> > > > Then pass to marked (extending the function:
>> > > >
>> > > > package
>> > > > {
>> > > > /**
>> > > > * @externs
>> > > > */
>> > > > COMPILE::JS
>> > > > public function marked(s:String, options:Object = null,
>> > > 

Build failed in Jenkins: royale-asjs_jsonly #1333

[apacheroyaleci]

See 


Changes:


--
[...truncated 1.71 MB...]

check-air-home:

check-compiler-home:

check-compile-env:
 [echo] OS: Windows Server 2016 / 10.0 / amd64
 [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.251-b08
 [echo] Java: 1.8.0_251
 [echo] Ant: Apache Ant(TM) version 1.9.9 compiled on February 2 2017 Ant 
Java Version: 1.8

prepare:

compile:

flat-ui-icons:
 [java] Error: Unable to access jarfile 

 [java] Java Result: 1

main:

main:

tweak-for-jsonly:
 [copy] Copying 1 file to 

 [copy] Copying 1 file to 


check-royale-config:

fixup-royale-config:

ide:

post-build:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

 [copy] Copying 1 file to 

 [copy] Copying 1 file to 

[touch] Creating 

[touch] Creating 

[touch] Creating 


last-message-if-airsdk:

main:
 [echo] ant main target completed on 04/20/2020 08:24:37 AM

sample-themes:

check-runtime-env:

runtime-setup:

mustella-setup:

load-task:

marmotinni-setup:

prepare:
 [echo] Making lib directory 
:\jenkins\workspace\royale-asjs_jsonly\marmotinni\java/lib
[mkdir] Created dir: 


selenium3-jar-check:

selenium3-jar:
[mkdir] Created dir: 


download-zip:
[mkdir] Created dir: 

  [get] Getting: https://bit.ly/2zm3ZzF
  [get] To: 

  [get] https://bit.ly/2zm3ZzF permanently moved to 
https://selenium-release.storage.googleapis.com/3.141/selenium-java-3.141.59.zip

untar-file:

unzip-file:
[unzip] Expanding: 

 into 


check-sum:

copy-downloaded-jar:
  [get] Getting: http://www.apache.org/licenses/LICENSE-2.0
  [get] To: 

 [copy] Copying 10 files to 


clean:

main:

clean:
   [delete] Deleting: 


check-compiler-home:

check-compiler:

compile:

compile-js:
 [echo] Compiling mustella.swc
 [echo] ROYALE_HOME: 

 [echo] ROYALE_COMPILER_HOME: 

 [java] args:
 [java] 
+royalelib=
 [java] +playerglobal.version=11.7
 [java] +env.PLAYERGLOBAL_HOME=${env.PLAYERGLOBAL_HOME}
 [java] -compiler.strict-xml=true
 [java] -compiler.targets=SWF,JSRoyale
 [java] 

Re: Routing (was Re: Spectrum Components)

[Harbs]

There are beads which handle the following:

1. Paths — in a hash router, this would be the part of the url between the hash 
and the question mark or a second hash. In a “browser router” this would be the 
section between the base and and the question mark or a hash
2. Parameters — handles between the question mark and subsequent hash. (yes 
RouteToParameter works)
3. I started work on dealing with trailing hash links for scrolling to anchor 
(or rather id) behavior, but that’s not yet done. (Something like this: 
https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior 
)

Ideally all of these beads should work in either kind of router. This is 
already PAYG, but it’s going to take some work to get this working and PAYG for 
both kinds of routers.

I’ll try to work on this today…

Harbs

> On Apr 20, 2020, at 10:01 AM, Carlos Rovira  wrote:
> 
> Hi Piotr,
> 
> I used hashes with params, so that's completely fine and we should have it.
> In fact, I think we already should have it since I'm seeing
> "RoutToParameter" class right? Maybe Harbs should confirm this since he
> implemented, and I just saw the class but still not use it.
> 
> 
> El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
> 
>> Harbs,
>> 
>> Agreed with that. We can rename them, but even in case of HashRouter - does
>> exclude it ability to have parameters ? Does those parameters not exists in
>> HasRouter as well. Is it not a common stuff no matter what kind of url it
>> is ?
>> 
>> niedz., 19 kwi 2020 o 15:52 Harbs  napisał(a):
>> 
>>> After thinking about this some more, I’m thinking that Router should be
>>> named and we should add another type of router for standard path routing.
>>> 
>>> React calls them HashRouter and BrowserRouter. Maybe we should use the
>>> same names…
>>> 
>>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
>> <
>>> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
>>> 
>>> 
 On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki >> 
>>> wrote:
 
 Hi Harbs,
 
 It sounds like you are asking me to check in onInit whether
 if(location.hash) exists then do something, but if doesn't exists check
>>> url
 params. - I may understand it in a wrong way, but I think location.hash
>>> may
 exists and location.search - where parameters are stored could exists
 equally.
 
 if(location.hash)
 {
 hashChangeHandler();
 }
 
 if (location.search)
 {
  parseParameters();
 }
 
 Am I missing something ?
 
 Thanks,
 Piotr
 
 pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
 
> Whatever you think is fine by me.
> 
> I don’t remember why I have "if(location.hash)”. It’s possible you can
>>> get
> rid of that conditional.
> 
> It could be you can get rid of that and handle hashRecieved in a bead.
>>> If
> the hashReceived event has no hash you can then check the URL.You do
>>> need
> to make sure that you always get a stateChange event and don’t
>> dispatch
>>> it
> twice.
> 
> Feel free to play around with the code… ;-)
> 
> Harbs
> 
>> On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com>
> wrote:
>> 
>> I think it would be better to have it here in Router.
>> 
>> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
>> 
>>> Alternatively, you can subclass Router to support setting the
>>> parameters
>>> in the onInit method.
>>> 
>>> Not sure which of these is best.
>>> 
 On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
 
 Actually, it’s not going to work because the
>>> router.routeState.parameters will not be set.
 
 You will likely need to add code to set the
> router.routeState.parameters
>>> using the part of the location after the question mark.
 
 The easiest way to do that would be to either:
 1. Modify RouteToParameters.stateChanged to first check that there
>>> is a
>>> parameters value and then set it if not.
 2. Subclass RouteToParameters and override stateChanged to make
>> that
>>> check first.
 
> On Apr 17, 2020, at 10:29 AM, Harbs > >> harbs.li...@gmail.com>> wrote:
> 
> I’m pretty sure it’ll work without the hash as well.
> 
> Give it a try.
> 
>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com >
>> wrote:
>> 
>> Hi Harbs,
>> 
>> Thanks for pointing me out, but this is still that Routing
>> expects
>>> me
>>> to
>> use in url hashes - The question is - What if I can't use hashes,
>>> but
>>> url
>> looks like I have presented in previous email ?
>> 

Re: Repository for tutorials

[Carlos Rovira]

Hi Andrew,

I think "royale-docs" is a separated repository itself (from the main
project) that should have all the learning material. That's docs, for now,
but your "Royale in a Week" project is ok for me in that place. Maybe is
more about to expose/highlight it better in that royale-docs page with a
banner or something as we have it and storing all of it in a concrete and
organized subfolder of royale-docs repo.

Royale docs could be as well hosting other tutorials and even the blog
examples, so website turns to just a marketing face for the project.

As you probably know, I'm investing some free time in looking to how to
create a Royale App for it so we use our own, and was trying to make royale
load markdown from github, but it's turning a bit complicated, due to
github using Kramdown and many other things. So maybe this is the solution:
migrate blog examples to royale-docs converting to mark-down and make
website just center the website in trying to create a Royale web that
centers in marketing and presentation of the technology.

Another thing I expect for the future is decrease the repositories we have,
since I think we have many and that could be a bit cumbersome to people
interested in Royale. One of the things I'd like before 1.0 is just 1 repo
instead of 3 for (compiler,typedefs and framework), that will make for sure
a difference for people coming to Royale and will streamline lots of things
like builds and releases).

Thanks


El dom., 19 abr. 2020 a las 23:52, Andrew Wetmore ()
escribió:

> Hi:
>
> Hi: I see that flink.apache.org has requested a separate git repository
> for
> the self-directed learning modules they hope to deploy. As we move closer
> to Royale 1.0 it will become more important to have a suite of tutorials to
> extends the excellent how-tos @carlos has been posting on the blog..
>
> I have committed to creating Royale in a Week, which will have lots of
> stuff to store: scripts, videos, code samples, transcripts, and so on. Can
> we fit that all into the existing documentation repository? Or should we
> request a separate one?
>
> A
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>


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

Release Step 010 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands:
git push
git push origin org.apache.royale.framework-0.9.7-rc2

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

Build failed in Jenkins: royale-asjs_jsonly #1332

[apacheroyaleci]

See 


Changes:


--
[...truncated 1.71 MB...]

check-air-home:

check-compiler-home:

check-compile-env:
 [echo] OS: Windows Server 2016 / 10.0 / amd64
 [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.251-b08
 [echo] Java: 1.8.0_251
 [echo] Ant: Apache Ant(TM) version 1.9.9 compiled on February 2 2017 Ant 
Java Version: 1.8

prepare:

compile:

flat-ui-icons:
 [java] Error: Unable to access jarfile 

 [java] Java Result: 1

main:

main:

tweak-for-jsonly:
 [copy] Copying 1 file to 

 [copy] Copying 1 file to 


check-royale-config:

fixup-royale-config:

ide:

post-build:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

 [copy] Copying 1 file to 

 [copy] Copying 1 file to 

[touch] Creating 

[touch] Creating 

[touch] Creating 


last-message-if-airsdk:

main:
 [echo] ant main target completed on 04/20/2020 07:14:15 AM

sample-themes:

check-runtime-env:

runtime-setup:

mustella-setup:

load-task:

marmotinni-setup:

prepare:
 [echo] Making lib directory 
:\jenkins\workspace\royale-asjs_jsonly\marmotinni\java/lib
[mkdir] Created dir: 


selenium3-jar-check:

selenium3-jar:
[mkdir] Created dir: 


download-zip:
[mkdir] Created dir: 

  [get] Getting: https://bit.ly/2zm3ZzF
  [get] To: 

  [get] https://bit.ly/2zm3ZzF permanently moved to 
https://selenium-release.storage.googleapis.com/3.141/selenium-java-3.141.59.zip

untar-file:

unzip-file:
[unzip] Expanding: 

 into 


check-sum:

copy-downloaded-jar:
  [get] Getting: http://www.apache.org/licenses/LICENSE-2.0
  [get] To: 

 [copy] Copying 10 files to 


clean:

main:

clean:
   [delete] Deleting: 


check-compiler-home:

check-compiler:

compile:

compile-js:
 [echo] Compiling mustella.swc
 [echo] ROYALE_HOME: 

 [echo] ROYALE_COMPILER_HOME: 

 [java] args:
 [java] 
+royalelib=
 [java] +playerglobal.version=11.7
 [java] +env.PLAYERGLOBAL_HOME=${env.PLAYERGLOBAL_HOME}
 [java] -compiler.strict-xml=true
 [java] -compiler.targets=SWF,JSRoyale
 [java] 

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

On Mon, Apr 20, 2020 at 12:01 AM Alex Harui 
wrote:

> I see compiler-jx/lib in the Workspace for royale-compiler on my VM.  If
> you are talking about your VM, you can compare console output from recent
> successful builds on both VMs.
>
>
I was talking about my VM.
A rebuild of royale-compiler seems to have fixed that problem.  Now
royale-typedefs passes as well!

Next up royale-asjs_jsonly...


> I'm done for tonight.  Good luck,
> -Alex
>
> On 4/19/20, 11:50 PM, "OmPrakash Muppirala"  wrote:
>
> On Sun, Apr 19, 2020 at 11:37 PM Alex Harui 
> wrote:
>
> > Royale-compiler has to be built first.  This is an example of shared
> > resources that I mentioned upthread.  Royale-typedefs is going to
> look for
> > a sibling workspace folder called royale-compiler with a built of
> > royale-compiler in it.  If royale-compiler fails to create all of its
> > binaries or is in the process of building them, royale-typedefs will
> report
> > an error.
> >
>
> Got it.  I was just looking at the logic here:
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-typedefs%2Fblob%2F85c74dde104294a0127ce46a8795d7534216e7eb%2Fjs%2Fbuild.xml%23L53data=02%7C01%7Caharui%40adobe.com%7C10c9e091b8054ef206df08d7e4f70e1a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229622064138237sdata=WjJhmdD0PeHDCYfqg%2Bf4mofhnQHdEPnwwj2ti%2FqlmII%3Dreserved=0
>
> Weird.  The royale-compiler build says it was successful, but I cant
> find
> the lib directory under
> C:\jenkins\workspace\royale-compiler\compiler-jx
>
>
>
>
> >
> > What should probably happen is that royale-typedefs pulls down the
> > lastsuccessfulartifacts from royale-compiler, but I've never found
> enough
> > time and energy to try to make changes like that since most of us do
> have
> > all of the folders as siblings.
> >
> > HTH,
> > -Alex
> >
> > On 4/19/20, 11:31 PM, "OmPrakash Muppirala" 
> wrote:
> >
> > I am now getting this error on royale-typedefs build:
> >
> > BUILD FAILEDc:\jenkins\workspace\royale-typedefs\build.xml:58:
> The
> > following error occurred while executing this line:
> > c:\jenkins\workspace\royale-typedefs\js\build.xml:91: src
> >
> >
> 'c:\jenkins\workspace\royale-typedefs\js\${ROYALE_TRANSPILER_HOME}\lib\google\closure-compiler\compiler.jar'
> > doesn't exist.
> >
> >
> > Where does the ROYALE_TRANSPILER_HOME var come from?
> >
> > Here is the full console output:
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fview%2FAgent%25202%2520data=02%7C01%7Caharui%40adobe.com%7C10c9e091b8054ef206df08d7e4f70e1a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229622064148235sdata=Rl%2F6kGkOf3Z2pauOtISD6aoqJ23M05iKMMxUV0eweuc%3Dreserved=0(Om's%20VM)/job/royale-typedefs/552/console
> >
> > On Sun, Apr 19, 2020 at 11:24 PM OmPrakash Muppirala <
> > bigosma...@gmail.com>
> > wrote:
> >
> > > On Sun, Apr 19, 2020 at 11:08 PM Alex Harui
>  > >
> > > wrote:
> > >
> > >> Congratulations!  But does that mean that JAVA_HOME is
> pointing at
> > a JRE
> > >> instead of a JDK?  If you have other issues that might be a
> factor.
> > >>
> > >
> > > Yeah, I messed up initially by getting the JRE instead of
> JDK.  I
> > have
> > > since corrected it.  But for some reason Ant still thinks that
> > JAVA_HOME is
> > > the jre directory.
> > > I don't know how to fix this, hence the hack :-|
> > >
> > >
> > >
> > >
> > >>
> > >> HTH,
> > >> -Alex
> > >>
> > >> On 4/19/20, 10:50 PM, "OmPrakash Muppirala" <
> bigosma...@gmail.com>
> > >> wrote:
> > >>
> > >> I copied tools.jar from  jdk/lib to the jre/lib.  That
> seems to
> > have
> > >> fixed
> > >> the issue.
> > >> We now have a successful build of the royale-compiler on
> the
> > new Agent
> > >> machine!!
> > >>
> > >> On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala <
> > >> bigosma...@gmail.com>
> > >> wrote:
> > >>
> > >> > Restart dint help.  Although Serkan's reply made me
> look at
> > how Ant
> > >> was
> > >> > getting invoked.
> > >> >
> > >> > I see this warning that tools.jar is missing:
> > >> >
> > >> > [royale-compiler] $ cmd.exe /C
> > >> "C:\apache\apache-ant-1.9.9\bin\ant.bat -file jenkins.xml
> > >> -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit
> > >> %%ERRORLEVEL%%"
> > >> >
> > >> > Unable to locate tools.jar. Expected to find 

Build failed in Jenkins: royale-asjs_jsonly #1331

[apacheroyaleci]

See 


Changes:


--
[...truncated 1.71 MB...]

check-playerglobal-home:

check-air-home:

check-compiler-home:

check-compile-env:
 [echo] OS: Windows Server 2016 / 10.0 / amd64
 [echo] VM: Java HotSpot(TM) 64-Bit Server VM / 25.251-b08
 [echo] Java: 1.8.0_251
 [echo] Ant: Apache Ant(TM) version 1.9.9 compiled on February 2 2017 Ant 
Java Version: 1.8

prepare:

compile:

flat-ui-icons:
 [java] Error: Unable to access jarfile 

 [java] Java Result: 1

main:

main:

tweak-for-jsonly:
 [copy] Copying 1 file to 

 [copy] Copying 1 file to 


check-royale-config:

fixup-royale-config:

ide:

post-build:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

 [copy] Copying 1 file to 

 [copy] Copying 1 file to 

[touch] Creating 

[touch] Creating 

[touch] Creating 


last-message-if-airsdk:

main:
 [echo] ant main target completed on 04/20/2020 07:01:41 AM

sample-themes:

check-runtime-env:

runtime-setup:

mustella-setup:

load-task:

marmotinni-setup:

prepare:
 [echo] Making lib directory 
:\jenkins\workspace\royale-asjs_jsonly\marmotinni\java/lib
[mkdir] Created dir: 


selenium3-jar-check:

selenium3-jar:
[mkdir] Created dir: 


download-zip:
[mkdir] Created dir: 

  [get] Getting: https://bit.ly/2zm3ZzF
  [get] To: 

  [get] https://bit.ly/2zm3ZzF permanently moved to 
https://selenium-release.storage.googleapis.com/3.141/selenium-java-3.141.59.zip

untar-file:

unzip-file:
[unzip] Expanding: 

 into 


check-sum:

copy-downloaded-jar:
  [get] Getting: http://www.apache.org/licenses/LICENSE-2.0
  [get] To: 

 [copy] Copying 10 files to 


clean:

main:

clean:

check-compiler-home:

check-compiler:

compile:

compile-js:
 [echo] Compiling mustella.swc
 [echo] ROYALE_HOME: 

 [echo] ROYALE_COMPILER_HOME: 

 [java] args:
 [java] 
+royalelib=
 [java] +playerglobal.version=11.7
 [java] +env.PLAYERGLOBAL_HOME=${env.PLAYERGLOBAL_HOME}
 [java] -compiler.strict-xml=true
 [java] -compiler.targets=SWF,JSRoyale
 [java] 
-output=
 [java] 

Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

[Carlos Rovira]

ok Yishay,

now I see it in central :)

about your question on why we should use 1.2.0. Maven has build tools as an
artifact, so using 1.1.0 will make people using the old source code no
matter what you have in source. That is one of the features of Maven that
all artifacts and its versions are officially stored in a central repo so
all people knows that they are using the right bits. If you build with Ant,
that will work since Ant just build from the sources you have and does not
have a concept of dependencies coming from a trusted source.

In this particular case the fix introduced in 1.2.0 was to make
reproducible builds working (or at least is needed for that, since that is
still to be checked if that works), along other fixes in compiler.

Thanks




El dom., 19 abr. 2020 a las 19:37, Yishay Weiss ()
escribió:

> Turns out my public key needed to be distributed to a keyserver.
>
>
>
> gpg --keyserver http://keyserver.ubuntu.com --send-keys 
>
>
>
> did the trick. You should see it now.
>
>
>
>
>
>
>
> *From:* Yishay Weiss 
> *Sent:* Sunday, April 19, 2020 5:22:56 PM
> *To:* dev@royale.apache.org 
> *Subject:* RE: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
>
>
>
> Thanks for spotting that. It looks like it failed signature validation on
> releasing the folder, even though it had passed it when closing the folder.
> I’ll see if I can figure this out…
>
> From: Carlos Rovira >
> Sent: Sunday, April 19, 2020 5:12 PM
> To: Apache Royale Development >
> Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
>
> I think 1.2.0 must be pushed to maven central
>
>
> https://search.maven.org/artifact/org.apache.royale.compiler/compiler-build-tools
>
> El dom., 19 abr. 2020 a las 16:10, Carlos Rovira ( >)
> escribió:
>
> > Ok Yishay,
> >
> > and is this version used in current 0.9.7 ongoing release process?
> >
> > thanks
> >
> >
> >
> > El dom., 19 abr. 2020 a las 15:37, Yishay Weiss ( >)
> > escribió:
> >
> >> Hi Carlos,
> >>
> >> It’s already been released, just haven’t announced it yet.
> >>
> >> From: Carlos Rovira >
> >> Sent: Sunday, April 19, 2020 4:12 PM
> >> To: Apache Royale Development >
> >> Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
> >>
> >> Hi
> >>
> >> can we consider this vote finished?
> >>
> >> also, I think current main release is not using this 1.2.0 right? so the
> >> fixes will be not applied
> >>
> >> Maybe I'm wrong
> >>
> >> Thanks
> >>
> >>
> >>
> >> El mié., 15 abr. 2020 a las 23:05, Harbs ()
> >> escribió:
> >>
> >> > I’m not going to have the time to look at this before the 72 hours are
> >> > over, so here’s my official +0 vote… ;-)
> >> >
> >> > Harbs
> >> >
> >> > > On Apr 13, 2020, at 11:25 PM, apacheroyal...@gmail.com wrote:
> >> > >
> >> > > Hi,
> >> > > This is the vote for the 1.2.0 release of Apache Royale Compiler
> Build
> >> > Tools.  The release candidate can be found here;
> >> > >
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/
> >> > >
> >> > > Before voting please review the section,'What are the ASF
> requirements
> >> > on approving a release?', at:
> >> > > http://www.apache.org/dev/release.html#approving-a-release
> >> > >
> >> > > At a minimum you would be expected to check that:
> >> > > - SHA and signed packages are correct
> >> > > - NOTICE and LICENSE files are all fine
> >> > > - That "mvn clean install" in the root of the source package
> completes
> >> > successfully
> >> > > - That you can modify other compiler poms to use that version of
> >> > compiler-build-tools and build the compiler.
> >> > >
> >> > > The KEYS file is at
> >> > https://dist.apache.org/repos/dist/release/royale/KEYS
> >> > >
> >> > > Maven artifacts are staged here:
> >> > >
> >> https://repository.apache.org/content/repositories/orgapacheroyale-1064
> >> > >
> >> > > Please vote to approve this release:
> >> > > +1 Approve the release
> >> > > -1 Disapprove the release (please provide specific comments to why)
> >> > >
> >> > > This vote will be open for 72 hours or until a result can be called.
> >> > >
> >> > > The vote passes if there is:
> >> > > - At least 3 +1 votes from the PMC
> >> > > - More positive votes than negative votes
> >> > >
> >> > > Remember that this is a 'beta-quality' release so expect there will
> be
> >> > many bugs found. IMO the goal is not to try to find and fix bugs in
> the
> >> RC,
> >> > but to make sure we have the packaging right, and enough functionality
> >> that
> >> > folks will have some success trying to use it.  People who are not in
> >> PMC
> >> > are also encouraged to test out the release and vote, although their
> >> votes
> >> > will not be binding, they can influence how the PMC votes.
> >> > >
> >> > > When voting please indicate what OS, IDE, Flash Player version and
> AIR
> >> > version you tested with.
> >> 

Re: Prioritize Release Jobs on CI

[Alex Harui]

I see compiler-jx/lib in the Workspace for royale-compiler on my VM.  If you 
are talking about your VM, you can compare console output from recent 
successful builds on both VMs.

I'm done for tonight.  Good luck,
-Alex

On 4/19/20, 11:50 PM, "OmPrakash Muppirala"  wrote:

On Sun, Apr 19, 2020 at 11:37 PM Alex Harui 
wrote:

> Royale-compiler has to be built first.  This is an example of shared
> resources that I mentioned upthread.  Royale-typedefs is going to look for
> a sibling workspace folder called royale-compiler with a built of
> royale-compiler in it.  If royale-compiler fails to create all of its
> binaries or is in the process of building them, royale-typedefs will 
report
> an error.
>

Got it.  I was just looking at the logic here:

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-typedefs%2Fblob%2F85c74dde104294a0127ce46a8795d7534216e7eb%2Fjs%2Fbuild.xml%23L53data=02%7C01%7Caharui%40adobe.com%7C10c9e091b8054ef206df08d7e4f70e1a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229622064138237sdata=WjJhmdD0PeHDCYfqg%2Bf4mofhnQHdEPnwwj2ti%2FqlmII%3Dreserved=0

Weird.  The royale-compiler build says it was successful, but I cant find
the lib directory under C:\jenkins\workspace\royale-compiler\compiler-jx




>
> What should probably happen is that royale-typedefs pulls down the
> lastsuccessfulartifacts from royale-compiler, but I've never found enough
> time and energy to try to make changes like that since most of us do have
> all of the folders as siblings.
>
> HTH,
> -Alex
>
> On 4/19/20, 11:31 PM, "OmPrakash Muppirala"  wrote:
>
> I am now getting this error on royale-typedefs build:
>
> BUILD FAILEDc:\jenkins\workspace\royale-typedefs\build.xml:58: The
> following error occurred while executing this line:
> c:\jenkins\workspace\royale-typedefs\js\build.xml:91: src
>
> 
'c:\jenkins\workspace\royale-typedefs\js\${ROYALE_TRANSPILER_HOME}\lib\google\closure-compiler\compiler.jar'
> doesn't exist.
>
>
> Where does the ROYALE_TRANSPILER_HOME var come from?
>
> Here is the full console output:
>
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fview%2FAgent%25202%2520data=02%7C01%7Caharui%40adobe.com%7C10c9e091b8054ef206df08d7e4f70e1a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229622064148235sdata=Rl%2F6kGkOf3Z2pauOtISD6aoqJ23M05iKMMxUV0eweuc%3Dreserved=0(Om's%20VM)/job/royale-typedefs/552/console
>
> On Sun, Apr 19, 2020 at 11:24 PM OmPrakash Muppirala <
> bigosma...@gmail.com>
> wrote:
>
> > On Sun, Apr 19, 2020 at 11:08 PM Alex Harui 
 >
> > wrote:
> >
> >> Congratulations!  But does that mean that JAVA_HOME is pointing at
> a JRE
> >> instead of a JDK?  If you have other issues that might be a factor.
> >>
> >
> > Yeah, I messed up initially by getting the JRE instead of JDK.  I
> have
> > since corrected it.  But for some reason Ant still thinks that
> JAVA_HOME is
> > the jre directory.
> > I don't know how to fix this, hence the hack :-|
> >
> >
> >
> >
> >>
> >> HTH,
> >> -Alex
> >>
> >> On 4/19/20, 10:50 PM, "OmPrakash Muppirala" 
> >> wrote:
> >>
> >> I copied tools.jar from  jdk/lib to the jre/lib.  That seems to
> have
> >> fixed
> >> the issue.
> >> We now have a successful build of the royale-compiler on the
> new Agent
> >> machine!!
> >>
> >> On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala <
> >> bigosma...@gmail.com>
> >> wrote:
> >>
> >> > Restart dint help.  Although Serkan's reply made me look at
> how Ant
> >> was
> >> > getting invoked.
> >> >
> >> > I see this warning that tools.jar is missing:
> >> >
> >> > [royale-compiler] $ cmd.exe /C
> >> "C:\apache\apache-ant-1.9.9\bin\ant.bat -file jenkins.xml
> >> -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit
> >> %%ERRORLEVEL%%"
> >> >
> >> > Unable to locate tools.jar. Expected to find it in C:\Program
> >> Files\Java\jre1.8.0_251\lib\tools.jar
> >> >
> >> >
> >> > I am pretty sure this is related to this issue.
> >> >
> >> >
> >> > On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala <
> >> bigosma...@gmail.com>
> >> > wrote:
> >> >
> >> >>
> >> >>
> >> >> On Sun, Apr 19, 2020 at 

Re: Routing (was Re: Spectrum Components)

[Carlos Rovira]

Hi Piotr,

I used hashes with params, so that's completely fine and we should have it.
In fact, I think we already should have it since I'm seeing
"RoutToParameter" class right? Maybe Harbs should confirm this since he
implemented, and I just saw the class but still not use it.


El dom., 19 abr. 2020 a las 16:23, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Harbs,
>
> Agreed with that. We can rename them, but even in case of HashRouter - does
> exclude it ability to have parameters ? Does those parameters not exists in
> HasRouter as well. Is it not a common stuff no matter what kind of url it
> is ?
>
> niedz., 19 kwi 2020 o 15:52 Harbs  napisał(a):
>
> > After thinking about this some more, I’m thinking that Router should be
> > named and we should add another type of router for standard path routing.
> >
> > React calls them HashRouter and BrowserRouter. Maybe we should use the
> > same names…
> >
> > https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> <
> > https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter
> >
> >
> > > On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki  >
> > wrote:
> > >
> > > Hi Harbs,
> > >
> > > It sounds like you are asking me to check in onInit whether
> > > if(location.hash) exists then do something, but if doesn't exists check
> > url
> > > params. - I may understand it in a wrong way, but I think location.hash
> > may
> > > exists and location.search - where parameters are stored could exists
> > > equally.
> > >
> > > if(location.hash)
> > > {
> > >  hashChangeHandler();
> > > }
> > >
> > > if (location.search)
> > > {
> > >   parseParameters();
> > > }
> > >
> > > Am I missing something ?
> > >
> > > Thanks,
> > > Piotr
> > >
> > > pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
> > >
> > >> Whatever you think is fine by me.
> > >>
> > >> I don’t remember why I have "if(location.hash)”. It’s possible you can
> > get
> > >> rid of that conditional.
> > >>
> > >> It could be you can get rid of that and handle hashRecieved in a bead.
> > If
> > >> the hashReceived event has no hash you can then check the URL.You do
> > need
> > >> to make sure that you always get a stateChange event and don’t
> dispatch
> > it
> > >> twice.
> > >>
> > >> Feel free to play around with the code… ;-)
> > >>
> > >> Harbs
> > >>
> > >>> On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > >> wrote:
> > >>>
> > >>> I think it would be better to have it here in Router.
> > >>>
> > >>> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> > >>>
> >  Alternatively, you can subclass Router to support setting the
> > parameters
> >  in the onInit method.
> > 
> >  Not sure which of these is best.
> > 
> > > On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> > >
> > > Actually, it’s not going to work because the
> >  router.routeState.parameters will not be set.
> > >
> > > You will likely need to add code to set the
> > >> router.routeState.parameters
> >  using the part of the location after the question mark.
> > >
> > > The easiest way to do that would be to either:
> > > 1. Modify RouteToParameters.stateChanged to first check that there
> > is a
> >  parameters value and then set it if not.
> > > 2. Subclass RouteToParameters and override stateChanged to make
> that
> >  check first.
> > >
> > >> On Apr 17, 2020, at 10:29 AM, Harbs   >  harbs.li...@gmail.com>> wrote:
> > >>
> > >> I’m pretty sure it’ll work without the hash as well.
> > >>
> > >> Give it a try.
> > >>
> > >>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> >  piotrzarzyck...@gmail.com >
> wrote:
> > >>>
> > >>> Hi Harbs,
> > >>>
> > >>> Thanks for pointing me out, but this is still that Routing
> expects
> > me
> >  to
> > >>> use in url hashes - The question is - What if I can't use hashes,
> > but
> >  url
> > >>> looks like I have presented in previous email ?
> > >>>
> > >>> Thanks,
> > >>> Piotr
> > >>>
> > >>> pt., 17 kwi 2020 o 09:20 Harbs  >  harbs.li...@gmail.com>> napisał(a):
> > >>>
> >  This app uses both path based and query based routing:
> > 
> > 
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> > <
> >  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>
> <
> > 
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> > <
> >  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
> > 
> >  You can see how it’s done here:
> > 
> > 
> > >>
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >  <
> > 
> > >>
> >
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> > >
> >  <
> > 
> > 
> 

Jenkins build is back to normal : royale-typedefs #553

[apacheroyaleci]

See 

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

On Sun, Apr 19, 2020 at 11:37 PM Alex Harui 
wrote:

> Royale-compiler has to be built first.  This is an example of shared
> resources that I mentioned upthread.  Royale-typedefs is going to look for
> a sibling workspace folder called royale-compiler with a built of
> royale-compiler in it.  If royale-compiler fails to create all of its
> binaries or is in the process of building them, royale-typedefs will report
> an error.
>

Got it.  I was just looking at the logic here:
https://github.com/apache/royale-typedefs/blob/85c74dde104294a0127ce46a8795d7534216e7eb/js/build.xml#L53

Weird.  The royale-compiler build says it was successful, but I cant find
the lib directory under C:\jenkins\workspace\royale-compiler\compiler-jx




>
> What should probably happen is that royale-typedefs pulls down the
> lastsuccessfulartifacts from royale-compiler, but I've never found enough
> time and energy to try to make changes like that since most of us do have
> all of the folders as siblings.
>
> HTH,
> -Alex
>
> On 4/19/20, 11:31 PM, "OmPrakash Muppirala"  wrote:
>
> I am now getting this error on royale-typedefs build:
>
> BUILD FAILEDc:\jenkins\workspace\royale-typedefs\build.xml:58: The
> following error occurred while executing this line:
> c:\jenkins\workspace\royale-typedefs\js\build.xml:91: src
>
> 'c:\jenkins\workspace\royale-typedefs\js\${ROYALE_TRANSPILER_HOME}\lib\google\closure-compiler\compiler.jar'
> doesn't exist.
>
>
> Where does the ROYALE_TRANSPILER_HOME var come from?
>
> Here is the full console output:
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fview%2FAgent%25202%2520data=02%7C01%7Caharui%40adobe.com%7Ca55fd899b7b247fcf6f308d7e4f468a0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229610695411638sdata=vvN91svHM9UrGH%2FpsQoFdpyHgyVMwatr5NJ9s9%2FUfzc%3Dreserved=0(Om's%20VM)/job/royale-typedefs/552/console
>
> On Sun, Apr 19, 2020 at 11:24 PM OmPrakash Muppirala <
> bigosma...@gmail.com>
> wrote:
>
> > On Sun, Apr 19, 2020 at 11:08 PM Alex Harui  >
> > wrote:
> >
> >> Congratulations!  But does that mean that JAVA_HOME is pointing at
> a JRE
> >> instead of a JDK?  If you have other issues that might be a factor.
> >>
> >
> > Yeah, I messed up initially by getting the JRE instead of JDK.  I
> have
> > since corrected it.  But for some reason Ant still thinks that
> JAVA_HOME is
> > the jre directory.
> > I don't know how to fix this, hence the hack :-|
> >
> >
> >
> >
> >>
> >> HTH,
> >> -Alex
> >>
> >> On 4/19/20, 10:50 PM, "OmPrakash Muppirala" 
> >> wrote:
> >>
> >> I copied tools.jar from  jdk/lib to the jre/lib.  That seems to
> have
> >> fixed
> >> the issue.
> >> We now have a successful build of the royale-compiler on the
> new Agent
> >> machine!!
> >>
> >> On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala <
> >> bigosma...@gmail.com>
> >> wrote:
> >>
> >> > Restart dint help.  Although Serkan's reply made me look at
> how Ant
> >> was
> >> > getting invoked.
> >> >
> >> > I see this warning that tools.jar is missing:
> >> >
> >> > [royale-compiler] $ cmd.exe /C
> >> "C:\apache\apache-ant-1.9.9\bin\ant.bat -file jenkins.xml
> >> -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit
> >> %%ERRORLEVEL%%"
> >> >
> >> > Unable to locate tools.jar. Expected to find it in C:\Program
> >> Files\Java\jre1.8.0_251\lib\tools.jar
> >> >
> >> >
> >> > I am pretty sure this is related to this issue.
> >> >
> >> >
> >> > On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala <
> >> bigosma...@gmail.com>
> >> > wrote:
> >> >
> >> >>
> >> >>
> >> >> On Sun, Apr 19, 2020 at 10:15 PM Alex Harui
> >> 
> >> >> wrote:
> >> >>
> >> >>> Did you reboot your VM?  Also, have you checked what user is
> >> running
> >> >>> Jenkins on your VM?  I think that can sometimes be a
> problem.  I
> >> might be
> >> >>> running Jenkins as the user.
> >> >>>
> >> >>>
> >> >> Agents don't require Jenkins to be running.  I will give the
> >> rebooting of
> >> >> the VM a shot .
> >> >>
> >> >> Thanks,
> >> >> Om
> >> >>
> >> >>
> >> >>> -Alex
> >> >>>
> >> >>> On 4/19/20, 10:01 PM, "OmPrakash Muppirala" <
> bigosma...@gmail.com
> >> >
> >> >>> wrote:
> >> >>>
> >> >>> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui
> >> 
> >> >>> wrote:
> >> >>>
> >> >>> > Should be here:
> >> >>> >
> >> >>> >
> >> >>>
> >>
> 

Re: Prioritize Release Jobs on CI

[Alex Harui]

Royale-compiler has to be built first.  This is an example of shared resources 
that I mentioned upthread.  Royale-typedefs is going to look for a sibling 
workspace folder called royale-compiler with a built of royale-compiler in it.  
If royale-compiler fails to create all of its binaries or is in the process of 
building them, royale-typedefs will report an error.

What should probably happen is that royale-typedefs pulls down the 
lastsuccessfulartifacts from royale-compiler, but I've never found enough time 
and energy to try to make changes like that since most of us do have all of the 
folders as siblings.

HTH,
-Alex

On 4/19/20, 11:31 PM, "OmPrakash Muppirala"  wrote:

I am now getting this error on royale-typedefs build:

BUILD FAILEDc:\jenkins\workspace\royale-typedefs\build.xml:58: The
following error occurred while executing this line:
c:\jenkins\workspace\royale-typedefs\js\build.xml:91: src

'c:\jenkins\workspace\royale-typedefs\js\${ROYALE_TRANSPILER_HOME}\lib\google\closure-compiler\compiler.jar'
doesn't exist.


Where does the ROYALE_TRANSPILER_HOME var come from?

Here is the full console output:

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fview%2FAgent%25202%2520data=02%7C01%7Caharui%40adobe.com%7Ca55fd899b7b247fcf6f308d7e4f468a0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229610695411638sdata=vvN91svHM9UrGH%2FpsQoFdpyHgyVMwatr5NJ9s9%2FUfzc%3Dreserved=0(Om's%20VM)/job/royale-typedefs/552/console

On Sun, Apr 19, 2020 at 11:24 PM OmPrakash Muppirala 
wrote:

> On Sun, Apr 19, 2020 at 11:08 PM Alex Harui 
> wrote:
>
>> Congratulations!  But does that mean that JAVA_HOME is pointing at a JRE
>> instead of a JDK?  If you have other issues that might be a factor.
>>
>
> Yeah, I messed up initially by getting the JRE instead of JDK.  I have
> since corrected it.  But for some reason Ant still thinks that JAVA_HOME 
is
> the jre directory.
> I don't know how to fix this, hence the hack :-|
>
>
>
>
>>
>> HTH,
>> -Alex
>>
>> On 4/19/20, 10:50 PM, "OmPrakash Muppirala" 
>> wrote:
>>
>> I copied tools.jar from  jdk/lib to the jre/lib.  That seems to have
>> fixed
>> the issue.
>> We now have a successful build of the royale-compiler on the new 
Agent
>> machine!!
>>
>> On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala <
>> bigosma...@gmail.com>
>> wrote:
>>
>> > Restart dint help.  Although Serkan's reply made me look at how Ant
>> was
>> > getting invoked.
>> >
>> > I see this warning that tools.jar is missing:
>> >
>> > [royale-compiler] $ cmd.exe /C
>> "C:\apache\apache-ant-1.9.9\bin\ant.bat -file jenkins.xml
>> -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit
>> %%ERRORLEVEL%%"
>> >
>> > Unable to locate tools.jar. Expected to find it in C:\Program
>> Files\Java\jre1.8.0_251\lib\tools.jar
>> >
>> >
>> > I am pretty sure this is related to this issue.
>> >
>> >
>> > On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala <
>> bigosma...@gmail.com>
>> > wrote:
>> >
>> >>
>> >>
>> >> On Sun, Apr 19, 2020 at 10:15 PM Alex Harui
>> 
>> >> wrote:
>> >>
>> >>> Did you reboot your VM?  Also, have you checked what user is
>> running
>> >>> Jenkins on your VM?  I think that can sometimes be a problem.  I
>> might be
>> >>> running Jenkins as the user.
>> >>>
>> >>>
>> >> Agents don't require Jenkins to be running.  I will give the
>> rebooting of
>> >> the VM a shot .
>> >>
>> >> Thanks,
>> >> Om
>> >>
>> >>
>> >>> -Alex
>> >>>
>> >>> On 4/19/20, 10:01 PM, "OmPrakash Muppirala" > >
>> >>> wrote:
>> >>>
>> >>> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui
>> 
>> >>> wrote:
>> >>>
>> >>> > Should be here:
>> >>> >
>> >>> >
>> >>>
>> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2FconfigureTools%2Fdata=02%7C01%7Caharui%40adobe.com%7Ca55fd899b7b247fcf6f308d7e4f468a0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229610695411638sdata=L6YhauHRF8IcSIlLJVFGn%2BPY5Ut%2BC9i2OBaNUF2yX20%3Dreserved=0
>> >>>
>> >>>
>> >>> My git is located in the same exact location as master.
>> >>> Moreover, the git call from the commandline executes fine.
>> The git
>> >>> call
>> >>> from ant exec is what is failing.
>> >>>
>> >>>
>> >>>
>> >>>   

Re: Prioritize Release Jobs on CI

[Alex Harui]

On 4/19/20, 11:25 PM, "OmPrakash Muppirala"  wrote:

On Sun, Apr 19, 2020 at 11:08 PM Alex Harui 
wrote:

> Congratulations!  But does that mean that JAVA_HOME is pointing at a JRE
> instead of a JDK?  If you have other issues that might be a factor.
>

Yeah, I messed up initially by getting the JRE instead of JDK.  I have
since corrected it.  But for some reason Ant still thinks that JAVA_HOME is
the jre directory.
I don't know how to fix this, hence the hack :-|

If you want to dig deeper, one idea is to run a Jenkins Job with a batch file 
that dumps out PATH and JAVA_HOME.  This post seems to imply that Ant may store 
info in .antrc and/or ant.conf files.

HTH,
-Alex



>
> HTH,
> -Alex
>
> On 4/19/20, 10:50 PM, "OmPrakash Muppirala"  wrote:
>
> I copied tools.jar from  jdk/lib to the jre/lib.  That seems to have
> fixed
> the issue.
> We now have a successful build of the royale-compiler on the new Agent
> machine!!
>
> On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala <
> bigosma...@gmail.com>
> wrote:
>
> > Restart dint help.  Although Serkan's reply made me look at how Ant
> was
> > getting invoked.
> >
> > I see this warning that tools.jar is missing:
> >
> > [royale-compiler] $ cmd.exe /C
> "C:\apache\apache-ant-1.9.9\bin\ant.bat -file jenkins.xml
> -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit
> %%ERRORLEVEL%%"
> >
> > Unable to locate tools.jar. Expected to find it in C:\Program
> Files\Java\jre1.8.0_251\lib\tools.jar
> >
> >
> > I am pretty sure this is related to this issue.
> >
> >
> > On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala <
> bigosma...@gmail.com>
> > wrote:
> >
> >>
> >>
> >> On Sun, Apr 19, 2020 at 10:15 PM Alex Harui
> 
> >> wrote:
> >>
> >>> Did you reboot your VM?  Also, have you checked what user is
> running
> >>> Jenkins on your VM?  I think that can sometimes be a problem.  I
> might be
> >>> running Jenkins as the user.
> >>>
> >>>
> >> Agents don't require Jenkins to be running.  I will give the
> rebooting of
> >> the VM a shot .
> >>
> >> Thanks,
> >> Om
> >>
> >>
> >>> -Alex
> >>>
> >>> On 4/19/20, 10:01 PM, "OmPrakash Muppirala" 
> >>> wrote:
> >>>
> >>> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui
> 
> >>> wrote:
> >>>
> >>> > Should be here:
> >>> >
> >>> >
> >>>
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2FconfigureTools%2Fdata=02%7C01%7Caharui%40adobe.com%7C064142121e184b7a721f08d7e4f39a91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229607239796954sdata=VBfhdjYkWvKLxPRasbxtkfkxJRGfGsyMf0w7EmaMQGY%3Dreserved=0
> >>>
> >>>
> >>> My git is located in the same exact location as master.
> >>> Moreover, the git call from the commandline executes fine.
> The git
> >>> call
> >>> from ant exec is what is failing.
> >>>
> >>>
> >>>
> >>> >
> >>> >
> >>> > HTH,
> >>> > -Alex
> >>> >
> >>> > From: OmPrakash Muppirala 
> >>> > Reply-To: "dev@royale.apache.org" 
> >>> > Date: Sunday, April 19, 2020 at 9:37 PM
> >>> > To: Apache Royale Development 
> >>> > Subject: Re: Prioritize Release Jobs on CI
> >>> >
> >>> > I'm a bit stumped here.  The royale-compiler is failing with
> this
> >>> error:
> >>> >
> >>> >
> >>> > BUILD FAILED
> >>> >
> >>> > c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute
> >>> failed:
> >>> > java.io.IOException: Cannot run program "git" (in directory
> >>> > "c:\jenkins\workspace\royale-compiler"): CreateProcess
> error=2,
> >>> The system
> >>> > cannot find the file specified
> >>> >
> >>> >   at java.lang.ProcessBuilder.start(Unknown Source)
> >>> >
> >>> >
> >>> > It is from this part of the jenkins.xml:
> >>> >
> >>> >
> >>> > 
> >>> > 
> >>> > 
> >>> > 
> >>> > 

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

I am now getting this error on royale-typedefs build:

BUILD FAILEDc:\jenkins\workspace\royale-typedefs\build.xml:58: The
following error occurred while executing this line:
c:\jenkins\workspace\royale-typedefs\js\build.xml:91: src
'c:\jenkins\workspace\royale-typedefs\js\${ROYALE_TRANSPILER_HOME}\lib\google\closure-compiler\compiler.jar'
doesn't exist.


Where does the ROYALE_TRANSPILER_HOME var come from?

Here is the full console output:
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/view/Agent%202%20(Om's%20VM)/job/royale-typedefs/552/console

On Sun, Apr 19, 2020 at 11:24 PM OmPrakash Muppirala 
wrote:

> On Sun, Apr 19, 2020 at 11:08 PM Alex Harui 
> wrote:
>
>> Congratulations!  But does that mean that JAVA_HOME is pointing at a JRE
>> instead of a JDK?  If you have other issues that might be a factor.
>>
>
> Yeah, I messed up initially by getting the JRE instead of JDK.  I have
> since corrected it.  But for some reason Ant still thinks that JAVA_HOME is
> the jre directory.
> I don't know how to fix this, hence the hack :-|
>
>
>
>
>>
>> HTH,
>> -Alex
>>
>> On 4/19/20, 10:50 PM, "OmPrakash Muppirala" 
>> wrote:
>>
>> I copied tools.jar from  jdk/lib to the jre/lib.  That seems to have
>> fixed
>> the issue.
>> We now have a successful build of the royale-compiler on the new Agent
>> machine!!
>>
>> On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala <
>> bigosma...@gmail.com>
>> wrote:
>>
>> > Restart dint help.  Although Serkan's reply made me look at how Ant
>> was
>> > getting invoked.
>> >
>> > I see this warning that tools.jar is missing:
>> >
>> > [royale-compiler] $ cmd.exe /C
>> "C:\apache\apache-ant-1.9.9\bin\ant.bat -file jenkins.xml
>> -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit
>> %%ERRORLEVEL%%"
>> >
>> > Unable to locate tools.jar. Expected to find it in C:\Program
>> Files\Java\jre1.8.0_251\lib\tools.jar
>> >
>> >
>> > I am pretty sure this is related to this issue.
>> >
>> >
>> > On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala <
>> bigosma...@gmail.com>
>> > wrote:
>> >
>> >>
>> >>
>> >> On Sun, Apr 19, 2020 at 10:15 PM Alex Harui
>> 
>> >> wrote:
>> >>
>> >>> Did you reboot your VM?  Also, have you checked what user is
>> running
>> >>> Jenkins on your VM?  I think that can sometimes be a problem.  I
>> might be
>> >>> running Jenkins as the user.
>> >>>
>> >>>
>> >> Agents don't require Jenkins to be running.  I will give the
>> rebooting of
>> >> the VM a shot .
>> >>
>> >> Thanks,
>> >> Om
>> >>
>> >>
>> >>> -Alex
>> >>>
>> >>> On 4/19/20, 10:01 PM, "OmPrakash Muppirala" > >
>> >>> wrote:
>> >>>
>> >>> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui
>> 
>> >>> wrote:
>> >>>
>> >>> > Should be here:
>> >>> >
>> >>> >
>> >>>
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2FconfigureTools%2Fdata=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229586200405113sdata=RhBraBN5pQDVrqAbMoXKejWBTwyqtSwd7DURGcQSwUg%3Dreserved=0
>> >>>
>> >>>
>> >>> My git is located in the same exact location as master.
>> >>> Moreover, the git call from the commandline executes fine.
>> The git
>> >>> call
>> >>> from ant exec is what is failing.
>> >>>
>> >>>
>> >>>
>> >>> >
>> >>> >
>> >>> > HTH,
>> >>> > -Alex
>> >>> >
>> >>> > From: OmPrakash Muppirala 
>> >>> > Reply-To: "dev@royale.apache.org" 
>> >>> > Date: Sunday, April 19, 2020 at 9:37 PM
>> >>> > To: Apache Royale Development 
>> >>> > Subject: Re: Prioritize Release Jobs on CI
>> >>> >
>> >>> > I'm a bit stumped here.  The royale-compiler is failing
>> with this
>> >>> error:
>> >>> >
>> >>> >
>> >>> > BUILD FAILED
>> >>> >
>> >>> > c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute
>> >>> failed:
>> >>> > java.io.IOException: Cannot run program "git" (in directory
>> >>> > "c:\jenkins\workspace\royale-compiler"): CreateProcess
>> error=2,
>> >>> The system
>> >>> > cannot find the file specified
>> >>> >
>> >>> >   at java.lang.ProcessBuilder.start(Unknown Source)
>> >>> >
>> >>> >
>> >>> > It is from this part of the jenkins.xml:
>> >>> >
>> >>> >
>> >>> > 
>> >>> > 
>> >>> > 
>> >>> > 
>> >>> > 

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

On Sun, Apr 19, 2020 at 11:08 PM Alex Harui 
wrote:

> Congratulations!  But does that mean that JAVA_HOME is pointing at a JRE
> instead of a JDK?  If you have other issues that might be a factor.
>

Yeah, I messed up initially by getting the JRE instead of JDK.  I have
since corrected it.  But for some reason Ant still thinks that JAVA_HOME is
the jre directory.
I don't know how to fix this, hence the hack :-|




>
> HTH,
> -Alex
>
> On 4/19/20, 10:50 PM, "OmPrakash Muppirala"  wrote:
>
> I copied tools.jar from  jdk/lib to the jre/lib.  That seems to have
> fixed
> the issue.
> We now have a successful build of the royale-compiler on the new Agent
> machine!!
>
> On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala <
> bigosma...@gmail.com>
> wrote:
>
> > Restart dint help.  Although Serkan's reply made me look at how Ant
> was
> > getting invoked.
> >
> > I see this warning that tools.jar is missing:
> >
> > [royale-compiler] $ cmd.exe /C
> "C:\apache\apache-ant-1.9.9\bin\ant.bat -file jenkins.xml
> -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit
> %%ERRORLEVEL%%"
> >
> > Unable to locate tools.jar. Expected to find it in C:\Program
> Files\Java\jre1.8.0_251\lib\tools.jar
> >
> >
> > I am pretty sure this is related to this issue.
> >
> >
> > On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala <
> bigosma...@gmail.com>
> > wrote:
> >
> >>
> >>
> >> On Sun, Apr 19, 2020 at 10:15 PM Alex Harui
> 
> >> wrote:
> >>
> >>> Did you reboot your VM?  Also, have you checked what user is
> running
> >>> Jenkins on your VM?  I think that can sometimes be a problem.  I
> might be
> >>> running Jenkins as the user.
> >>>
> >>>
> >> Agents don't require Jenkins to be running.  I will give the
> rebooting of
> >> the VM a shot .
> >>
> >> Thanks,
> >> Om
> >>
> >>
> >>> -Alex
> >>>
> >>> On 4/19/20, 10:01 PM, "OmPrakash Muppirala" 
> >>> wrote:
> >>>
> >>> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui
> 
> >>> wrote:
> >>>
> >>> > Should be here:
> >>> >
> >>> >
> >>>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2FconfigureTools%2Fdata=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229586200405113sdata=RhBraBN5pQDVrqAbMoXKejWBTwyqtSwd7DURGcQSwUg%3Dreserved=0
> >>>
> >>>
> >>> My git is located in the same exact location as master.
> >>> Moreover, the git call from the commandline executes fine.
> The git
> >>> call
> >>> from ant exec is what is failing.
> >>>
> >>>
> >>>
> >>> >
> >>> >
> >>> > HTH,
> >>> > -Alex
> >>> >
> >>> > From: OmPrakash Muppirala 
> >>> > Reply-To: "dev@royale.apache.org" 
> >>> > Date: Sunday, April 19, 2020 at 9:37 PM
> >>> > To: Apache Royale Development 
> >>> > Subject: Re: Prioritize Release Jobs on CI
> >>> >
> >>> > I'm a bit stumped here.  The royale-compiler is failing with
> this
> >>> error:
> >>> >
> >>> >
> >>> > BUILD FAILED
> >>> >
> >>> > c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute
> >>> failed:
> >>> > java.io.IOException: Cannot run program "git" (in directory
> >>> > "c:\jenkins\workspace\royale-compiler"): CreateProcess
> error=2,
> >>> The system
> >>> > cannot find the file specified
> >>> >
> >>> >   at java.lang.ProcessBuilder.start(Unknown Source)
> >>> >
> >>> >
> >>> > It is from this part of the jenkins.xml:
> >>> >
> >>> >
> >>> > 
> >>> > 
> >>> > 
> >>> > 
> >>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-librarydata=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229586200405113sdata=AJO8lF1H7VG%2Fy9T1I9p0%2Fsqjh8cQ8U8exbInYHyuch0%3Dreserved=0
> >>> <
> >>> >
> >>>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-librarydata=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229586200415104sdata=2%2BG3WpItozbraXCp2Q4XACBXizsHNZQYMAgiSaaPXwo%3Dreserved=0
> >>> >"
> >>> > />
> >>> > 
> >>> > 
> >>> > Cloned fresh copy of Google Closure
> Library
> >>> > 
> >>> >
> >>> > I am not sure how this executable call works without the
> full path.
> >>> >
> >>> > I checked the env variables, 

Re: Prioritize Release Jobs on CI

[Alex Harui]

Congratulations!  But does that mean that JAVA_HOME is pointing at a JRE 
instead of a JDK?  If you have other issues that might be a factor.

HTH,
-Alex

On 4/19/20, 10:50 PM, "OmPrakash Muppirala"  wrote:

I copied tools.jar from  jdk/lib to the jre/lib.  That seems to have fixed
the issue.
We now have a successful build of the royale-compiler on the new Agent
machine!!

On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala 
wrote:

> Restart dint help.  Although Serkan's reply made me look at how Ant was
> getting invoked.
>
> I see this warning that tools.jar is missing:
>
> [royale-compiler] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-file jenkins.xml -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit 
%%ERRORLEVEL%%"
>
> Unable to locate tools.jar. Expected to find it in C:\Program 
Files\Java\jre1.8.0_251\lib\tools.jar
>
>
> I am pretty sure this is related to this issue.
>
>
> On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala 

> wrote:
>
>>
>>
>> On Sun, Apr 19, 2020 at 10:15 PM Alex Harui 
>> wrote:
>>
>>> Did you reboot your VM?  Also, have you checked what user is running
>>> Jenkins on your VM?  I think that can sometimes be a problem.  I might 
be
>>> running Jenkins as the user.
>>>
>>>
>> Agents don't require Jenkins to be running.  I will give the rebooting of
>> the VM a shot .
>>
>> Thanks,
>> Om
>>
>>
>>> -Alex
>>>
>>> On 4/19/20, 10:01 PM, "OmPrakash Muppirala" 
>>> wrote:
>>>
>>> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui 

>>> wrote:
>>>
>>> > Should be here:
>>> >
>>> >
>>> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2FconfigureTools%2Fdata=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229586200405113sdata=RhBraBN5pQDVrqAbMoXKejWBTwyqtSwd7DURGcQSwUg%3Dreserved=0
>>>
>>>
>>> My git is located in the same exact location as master.
>>> Moreover, the git call from the commandline executes fine.  The git
>>> call
>>> from ant exec is what is failing.
>>>
>>>
>>>
>>> >
>>> >
>>> > HTH,
>>> > -Alex
>>> >
>>> > From: OmPrakash Muppirala 
>>> > Reply-To: "dev@royale.apache.org" 
>>> > Date: Sunday, April 19, 2020 at 9:37 PM
>>> > To: Apache Royale Development 
>>> > Subject: Re: Prioritize Release Jobs on CI
>>> >
>>> > I'm a bit stumped here.  The royale-compiler is failing with this
>>> error:
>>> >
>>> >
>>> > BUILD FAILED
>>> >
>>> > c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute
>>> failed:
>>> > java.io.IOException: Cannot run program "git" (in directory
>>> > "c:\jenkins\workspace\royale-compiler"): CreateProcess error=2,
>>> The system
>>> > cannot find the file specified
>>> >
>>> >   at java.lang.ProcessBuilder.start(Unknown Source)
>>> >
>>> >
>>> > It is from this part of the jenkins.xml:
>>> >
>>> >
>>> > 
>>> > 
>>> > 
>>> > 
>>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-librarydata=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229586200405113sdata=AJO8lF1H7VG%2Fy9T1I9p0%2Fsqjh8cQ8U8exbInYHyuch0%3Dreserved=0
>>> <
>>> >
>>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-librarydata=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229586200415104sdata=2%2BG3WpItozbraXCp2Q4XACBXizsHNZQYMAgiSaaPXwo%3Dreserved=0
>>> >"
>>> > />
>>> > 
>>> > 
>>> > Cloned fresh copy of Google Closure Library
>>> > 
>>> >
>>> > I am not sure how this executable call works without the full 
path.
>>> >
>>> > I checked the env variables, I do have both the git/bin and 
git/cmd
>>> > directory in the PATH:
>>> >
>>> > [cid:ii_k97zkk9o0]
>>> >
>>> > What am I missing?
>>> >
>>> > Thanks,
>>> > Om
>>> >
>>> > On Sat, Apr 18, 2020 at 11:54 PM OmPrakash Muppirala <
>>> bigosma...@gmail.com
>>> > > wrote:
>>> > Update - I have successfully attached my VM as a slave agent of 
our
>>> > Jenkins instance.
>>> > I am going to pull the job - /royale-asjs_jsonly and