Re: Royale Docs Changes Proposal

[Piotr Zarzycki]

Hi Guys,

One small thing apart of above changes which are in progress. "Get Started"
in the main menu on the website and "Getting Started" in the footer are
pointing us to the same page. Words are different - What do you think to
align them and have in footer "Get Started" as well?

Thanks,
Piotr

śr., 8 maj 2019 o 10:04 Carlos Rovira  napisał(a):

> Hi Andrian,
>
> thanks for joining us. I think you're right, so for me is ok to start
> helping in docs and videos since is our main focus now.
>
> Thanks and welcome to Apache Royale! :)
>
>
>
> El mié., 8 may. 2019 a las 9:16, Yishay Weiss ()
> escribió:
>
> > Hi Adrian and Welcome,
> >
> >
> >
> > These changes all sound good to me.
> >
> >
> >
> > Yishay
> >
> >
> >
> > 
> > From: Adrian Szuszkiewicz 
> > Sent: Tuesday, May 7, 2019 6:47:56 PM
> > To: dev@royale.apache.org
> > Subject: Royale Docs Changes Proposal
> >
> > Hi all :)
> >
> > Introduction
> >
> > My name is Adrian and together with Piotr I am preparing a set of video
> > tutorials about Moonshine IDE, Royale and ActionScript. I am completely
> new
> > to this technology stack and a few days ago I was reading Royale Docs for
> > the first time. There were a couple of things I found confusing about the
> > structure of the documentation. I believe that with a few minor changes
> to
> > the docs we can achieve more clarity. If the Team agrees I volunteer to
> do
> > the changes. Here’s what I propose:
> >
> > Merging Getting Started
> >
> > There are two pages with awfully similar titles and responsibilities:
> >
> >-
> >
> >Getting Started [https://royale.apache.org/getting-started/]
> reachable
> >from "Get Started" button on main Royale page
> >-
> >
> >Get started with Royale [
> >https://apache.github.io/royale-docs/Get%20Started.html] reachable
> from
> >"Get Started" item in doc’s table of content.
> >
> > In my opinion, the existence of two Get Started pages is very confusing.
> If
> > you agree I’d like to:
> >
> >1.
> >
> >Move all the content of Getting Started page to Get started with
> Royale
> > in
> >the docs
> >2.
> >
> >Make Get Started button on main Royale page point to Get started with
> >Royale in the docs.
> >
> >
> > Renaming Links with Instructions
> >
> > On "Getting Started" page there are four links with instructions about
> how
> > to install and configure Royale in different editors. When I was reading
> > the docs for the first time I skipped those links because I thought they
> > only point to download locations, not the instructions. I’d like to
> rename
> > them as follows:
> >
> >-
> >
> >“Moonshine IDE” -> “Instructions for Moonshine IDE”
> >-
> >
> >“Visual Studio Code” -> “Instructions for Visual Studio Code”
> >-
> >
> >“Adobe Flash Builder” -> “Instructions for Adobe Flash Builder”
> >-
> >
> >“IntelliJ IDEA” -> “Instructions for IntelliJ IDEA” [this link is
> empty
> >but I’d keep it anyway]
> >
> >
> > Changing Menu Behavior
> >
> > The Table of Content menu on the right side in the docs behaves in a
> weird
> > way. When you click on an item it doesn't automatically expand. But when
> > you select your topic from the main text then it expands correctly
> showing
> > all its children. At first, I thought the menu was incomplete and
> > disjointed but then I realized it just doesn’t expand at right times. It
> > made me feel a little bit lost in the docs and track my journey through
> > them in the notepad. If you agree I’d like to fix expanding behavior.
> >
> > It's easier to conceptualize this in a video:
> > https://www.youtube.com/watch?v=GHzDnH8h6gE&feature=youtu.be
> >
> >
> > Have a great day,
> >
> > Adrian
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

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

Re: Problems with Java 12

[Harbs]

Yeah. Looks like the problem. Thanks.

Maybe we should keep 1.6 the default, but allow a environment variable to set 
it higher?

> On May 15, 2019, at 9:58 AM, Alex Harui  wrote:
> 
> Looks like royale-asjs/build.xml specifies 1.5.  That's probably an 
> accidental copy from Flex.
> 
> That said, I'm not sure that flex-compiler-oem will work with Flash Builder 
> if the target is not 1.6.  If that's true, we'll need some way to not build 
> that jar on Java 12.
> 
> -Alex
> 
> On 5/14/19, 11:49 PM, "Harbs"  wrote:
> 
>Progress.
> 
>I was building using `ant all` on asjs.
> 
>When I build using `ant` on royale-compiler, I got a bunch of errors:
>   [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 6
>   [javac] error: Source option 6 is no longer supported. Use 7 or later.
>   [javac] error: Target option 6 is no longer supported. Use 7 or later.
> 
>Changing all the javac.src properties to 1.7 made the compilation complete.
> 
>I switched back to royale-asjs and ran `ant all` again and I get this:
> 
>compile:
>   [javac] Compiling 3 source files to 
> C:\Apache\royale-compiler\compiler\target\classes
>   [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 5
>   [javac] error: Source option 5 is no longer supported. Use 7 or later.
>   [javac] error: Target option 5 is no longer supported. Use 7 or later.
> 
>BUILD FAILED
>C:\Apache\royale-asjs\build.xml:1948: The following error occurred while 
> executing this line:
>C:\Apache\royale-asjs\build.xml:2035: The following error occurred while 
> executing this line:
>C:\Apache\royale-compiler\build.xml:68: The following error occurred while 
> executing this line:
>C:\Apache\royale-compiler\compiler\build.xml:486: Compile failed; see the 
> compiler error output for details.
> 
> 
>> On May 14, 2019, at 7:06 PM, Alex Harui  wrote:
>> 
>> I just switched to compiler-build-tools, ran "ant clean" then "ant".  The 
>> console said 
>> "warning: [options] bootstrap class path not set in conjunction with -source 
>> 1.6"
>> 
>> What do you get?  Maybe the main build.xml sets something but I didn't see 
>> it.  Swfutils sets 1.5.  That can probably be changed, but I thought 
>> swfutils ran after compiler-build-tools.  Maybe you have an environment 
>> variable or local.properties or env.properties.
>> 
>> -Alex
>> 
>> On 5/14/19, 8:44 AM, "Harbs"  wrote:
>> 
>>   Most of the build files were set to 1.6. There was one set to 1.5 (I don’t 
>> remember off-hand which one.
>> 
>>   Changing all of them did not help.
>> 
>>   I have no idea where this is being picked up from. Is it possible Maven 
>> artifacts are coming into play?
>> 
>>> On May 14, 2019, at 6:29 PM, Alex Harui  wrote:
>>> 
>>> I can't figure out why your build is trying to use 1.5.  My build.xml for 
>>> compiler-build-tools is using 1.6.
>>> 
>>> -Alex
>>> 
>>> On 5/14/19, 3:46 AM, "Harbs"  wrote:
>>> 
>>>  I’m setting up a new Windows machine and I installed Java 12. I can’t get 
>>> Royale to compile. I keep getting this error:
>>> 
>>>  annotate.class:
>>> [javac] Compiling 1 source file to 
>>> C:\Apache\royale-compiler\compiler-build-tools\target\classes
>>> [javac] warning: [options] bootstrap class path not set in conjunction 
>>> with -source 5
>>> [javac] error: Source option 5 is no longer supported. Use 7 or later.
>>> [javac] error: Target option 5 is no longer supported. Use 7 or later.
>>> 
>>>  I tried changing javac.src=1.7 instead of 1.5 in the build.xml files, but 
>>> it had no effect.
>>> 
>>>  Any suggestions (other than trying to figure out how to download an older 
>>> version of Java)?
>>> 
>>>  Harbs
>>> 
>> 
>> 
>> 
> 
> 
> 

[GitHub] [royale-docs] piotrzarzycki21 merged pull request #17: Move Getting Started to Docs

[GitBox]

piotrzarzycki21 merged pull request #17: Move Getting Started to Docs
URL: https://github.com/apache/royale-docs/pull/17
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Royale Docs Changes Proposal

[Adrian Szuszkiewicz]

My pull request

#17: Move Getting Started to Docs
URL: https://github.com/apache/royale-docs/pull/17

has just been merged. Now I would like to ask someone with WordPress access
to change the link on header's "GET STARTED" button and footer's "Getting
Started"

from: https://royale.apache.org/getting-started/
to: https://apache.github.io/royale-docs/Get%20Started.html

Thanks,
Adrian



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

Build failed in Jenkins: royale-asjs_MXTests #767

[Apache Royale CI Server]

See 


Changes:

[yishayjobs] All color models should have Number, so NaN is an option.

[yishayjobs] Thumb can disappear when selected color is empty.

--
[...truncated 2.06 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

Build failed in Jenkins: royale-asjs_MXTests #768

[Apache Royale CI Server]

See 


--
[...truncated 2.04 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[GitHub] [royale-docs] Aszusz opened a new pull request #19: Make the logo clickable

[GitBox]

Aszusz opened a new pull request #19: Make the logo clickable
URL: https://github.com/apache/royale-docs/pull/19
 
 
   This feature makes the Royale logo in docs clickable. It points to Royale 
main page.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [royale-docs] Aszusz opened a new pull request #20: Further improve build instructions

[GitBox]

Aszusz opened a new pull request #20: Further improve build instructions
URL: https://github.com/apache/royale-docs/pull/20
 
 
   Let me correct the instructions I provided last time. This method uses a 
built-in Jekyll server and doesn't require manipulating the baseurl parameter.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Problems with Java 12

[Alex Harui]

That's fine, although I think the more common pattern is to require use of 
env.properties and/or local.properties files.

It occurs to me that regarding Flash Builder, the source compatibility is less 
important than the target compatibility.  Does Java 12 have Java 1.6 target 
compatibility?

-Alex

On 5/15/19, 12:32 AM, "Harbs"  wrote:

Yeah. Looks like the problem. Thanks.

Maybe we should keep 1.6 the default, but allow a environment variable to 
set it higher?

> On May 15, 2019, at 9:58 AM, Alex Harui  wrote:
> 
> Looks like royale-asjs/build.xml specifies 1.5.  That's probably an 
accidental copy from Flex.
> 
> That said, I'm not sure that flex-compiler-oem will work with Flash 
Builder if the target is not 1.6.  If that's true, we'll need some way to not 
build that jar on Java 12.
> 
> -Alex
> 
> On 5/14/19, 11:49 PM, "Harbs"  wrote:
> 
>Progress.
> 
>I was building using `ant all` on asjs.
> 
>When I build using `ant` on royale-compiler, I got a bunch of errors:
>   [javac] warning: [options] bootstrap class path not set in 
conjunction with -source 6
>   [javac] error: Source option 6 is no longer supported. Use 7 or 
later.
>   [javac] error: Target option 6 is no longer supported. Use 7 or 
later.
> 
>Changing all the javac.src properties to 1.7 made the compilation 
complete.
> 
>I switched back to royale-asjs and ran `ant all` again and I get this:
> 
>compile:
>   [javac] Compiling 3 source files to 
C:\Apache\royale-compiler\compiler\target\classes
>   [javac] warning: [options] bootstrap class path not set in 
conjunction with -source 5
>   [javac] error: Source option 5 is no longer supported. Use 7 or 
later.
>   [javac] error: Target option 5 is no longer supported. Use 7 or 
later.
> 
>BUILD FAILED
>C:\Apache\royale-asjs\build.xml:1948: The following error occurred 
while executing this line:
>C:\Apache\royale-asjs\build.xml:2035: The following error occurred 
while executing this line:
>C:\Apache\royale-compiler\build.xml:68: The following error occurred 
while executing this line:
>C:\Apache\royale-compiler\compiler\build.xml:486: Compile failed; see 
the compiler error output for details.
> 
> 
>> On May 14, 2019, at 7:06 PM, Alex Harui  wrote:
>> 
>> I just switched to compiler-build-tools, ran "ant clean" then "ant".  
The console said 
>> "warning: [options] bootstrap class path not set in conjunction with 
-source 1.6"
>> 
>> What do you get?  Maybe the main build.xml sets something but I didn't 
see it.  Swfutils sets 1.5.  That can probably be changed, but I thought 
swfutils ran after compiler-build-tools.  Maybe you have an environment 
variable or local.properties or env.properties.
>> 
>> -Alex
>> 
>> On 5/14/19, 8:44 AM, "Harbs"  wrote:
>> 
>>   Most of the build files were set to 1.6. There was one set to 1.5 (I 
don’t remember off-hand which one.
>> 
>>   Changing all of them did not help.
>> 
>>   I have no idea where this is being picked up from. Is it possible 
Maven artifacts are coming into play?
>> 
>>> On May 14, 2019, at 6:29 PM, Alex Harui  
wrote:
>>> 
>>> I can't figure out why your build is trying to use 1.5.  My build.xml 
for compiler-build-tools is using 1.6.
>>> 
>>> -Alex
>>> 
>>> On 5/14/19, 3:46 AM, "Harbs"  wrote:
>>> 
>>>  I’m setting up a new Windows machine and I installed Java 12. I can’t 
get Royale to compile. I keep getting this error:
>>> 
>>>  annotate.class:
>>> [javac] Compiling 1 source file to 
C:\Apache\royale-compiler\compiler-build-tools\target\classes
>>> [javac] warning: [options] bootstrap class path not set in 
conjunction with -source 5
>>> [javac] error: Source option 5 is no longer supported. Use 7 or 
later.
>>> [javac] error: Target option 5 is no longer supported. Use 7 or 
later.
>>> 
>>>  I tried changing javac.src=1.7 instead of 1.5 in the build.xml files, 
but it had no effect.
>>> 
>>>  Any suggestions (other than trying to figure out how to download an 
older version of Java)?
>>> 
>>>  Harbs
>>> 
>> 
>> 
>> 
> 
> 
> 

[GitHub] [royale-docs] piotrzarzycki21 merged pull request #20: Further improve build instructions

[GitBox]

piotrzarzycki21 merged pull request #20: Further improve build instructions
URL: https://github.com/apache/royale-docs/pull/20
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [royale-docs] piotrzarzycki21 merged pull request #19: Make the logo clickable

[GitBox]

piotrzarzycki21 merged pull request #19: Make the logo clickable
URL: https://github.com/apache/royale-docs/pull/19
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Royale_Release_Step_001 - Build # 61 - Failure!

[Apache Royale CI Server]

Royale_Release_Step_001 - Build # 61 - Failure:

Check console output at 
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_001/61/
 to view the results.

Release Step 001 Succeeded

[Apache Royale CI Server]

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

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

Release Step 001a Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_001a_If_Utils and run the following 
commands:
git push

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

Release Step 002a Succeeded

[Apache Royale CI Server]

Continue on to Release Step 003

Release Step 002 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands:
git push
git push origin org.apache.royale.compiler-0.9.6-rc1

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

Release Step 003 Succeeded

[Apache Royale CI Server]

1. If you are releasing the utils jars (compiler-jburg-types and 
compiler-build-tools), Run:
  ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
 ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
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_003_Sign 
-Drelease.version=0.9.6
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload 
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging.  Do not "Close" 
the staging repository until the other repos have been added.

Release Step 004 Succeeded

[Apache Royale CI Server]

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

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

Release Step 005 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_005 and run the following commands:
git push

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

Release Step 005a Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_005a and run the following commands:
git push

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

Release Step 006 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands:
git push
git push origin org.apache.royale.typedefs-0.9.6-rc1

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

Release Step 007 Succeeded

[Apache Royale CI Server]

1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.6
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_007_Sign 
-Drelease.version=0.9.6
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_007_Upload 
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging.  Do not "Close" 
the staging repository until the other repos have been added.

Build failed in Jenkins: royale-asjs_MXTests #769

[Apache Royale CI Server]

See 


--
[...truncated 2.04 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

Build failed in Jenkins: royale-asjs_MXTests #770

[Apache Royale CI Server]

See 


--
[...truncated 2.04 MB...]
[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: 

[mxmlc] using source file: