Build failed in Jenkins: royale-asjs_MXTests #776

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

Build failed in Jenkins: royale-asjs_MXTests #775

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

Release Step 007 Succeeded

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

Release Step 006 Succeeded

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 005a Succeeded

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

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

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

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

Release Step 002a Succeeded

Continue on to Release Step 003

Release Step 002 Succeeded

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 001a Succeeded

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

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.

Re: About having an Apache Royale page on Wikipedia

It is now here: [1]. I will update the Apache Flex site, which mentions Royale, to point to it. [1] https://en.wikipedia.org/wiki/Apache_Royale On Fri, May 17, 2019 at 1:56 PM Andrew Wetmore wrote: > Following the GEMO "good enough, move on" principle, I am going to try to > move the page to "l

Re: About having an Apache Royale page on Wikipedia

Following the GEMO "good enough, move on" principle, I am going to try to move the page to "live" status. We can continue refining it and adding information indefinitely. On Fri, May 17, 2019 at 1:21 PM Andrew Wetmore wrote: > @Carlos if the client does not want to give access to a pre-productio

Re: About having an Apache Royale page on Wikipedia

@Carlos if the client does not want to give access to a pre-production site, would they agree to our posting a webtour, a video of the site in action? Thank you for the thoughts about what to say about Royale. I will include multi-target thoughts!. On Fri, May 17, 2019 at 12:45 PM Carlos Rovira

Re: About having an Apache Royale page on Wikipedia

Hi, we asking our client about what we can share about our first production royale app. Let's see if we can post the link to a pre-production site, if we can post user/pass to enter it, and if we can't do that at least post some screen shots @Andrew Wetmore thanks for working on the wikipedia pa

Build failed in Jenkins: royale-asjs_MXTests #774

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

Re: Royale Docs Changes Proposal

@Piotr: yes, that is correct. If I use the menu, it is like I am using the table of contents of a physical book. If I follow a link within the text, it is as if I am picking up a different physical book. On Fri, May 17, 2019 at 7:18 AM Piotr Zarzycki wrote: > Andrew, > > By saying that: > > "If

Re: About having an Apache Royale page on Wikipedia

Here is the current state of our Wikipedia page in my editor area [1]. I have a few things to add, like figuring out how to make the logo appear in the info box and adding more interesting stuff to the "salient features" section. I also want to add a section about the community and how to become a

Re: About having an Apache Royale page on Wikipedia

That sucks… :-( One thing I like about git based wikis is that you can edit locally on a text editor and these things don’t happen (as long as your text editor does automatic saves). > On May 17, 2019, at 1:24 PM, Andrew Wetmore wrote: > > @Harbs: thank you! > > Slight setback on the Wikiped

Re: About having an Apache Royale page on Wikipedia

@Harbs: thank you! Slight setback on the Wikipedia page: I was about 80% done creating it in the Wikipedia sandbox, stepped away to do other things for a couple of hours, Windows did an update and all my work was lost (the sandbox does not seem to have a "save" function). When I am done swearing a

Re: Royale Docs Changes Proposal

Andrew, By saying that: "If I am starting from the help docs I do not want the window to suddenly be focusing on something else; I would prefer a new window to appear with whatever I clicked on so I can go back to the first window easily and continue my studies." Do you mean when you are being i

Re: Royale Docs Changes Proposal

I agree with @Piotr that context is key. If I am starting from the help docs I do not want the window to suddenly be focusing on something else; I would prefer a new window to appear with whatever I clicked on so I can go back to the first window easily and continue my studies. Similarly, if my con

Re: Royale Docs Changes Proposal

Let's see whether Andrew have different thoughts. He is an expert in case of documentation ;) Adrian is working on 1 or 2 small pull requests more. ;) pt., 17 maj 2019 o 10:11 Carlos Rovira napisał(a): > Ok Piotr, > > so I think we have all set as you said, and we just need to worry about the >

Re: Royale Docs Changes Proposal

Ok Piotr, so I think we have all set as you said, and we just need to worry about the content created to follow that guidelines :) El vie., 17 may. 2019 a las 10:07, Piotr Zarzycki (< piotrzarzyck...@gmail.com>) escribió: > In my opinion it depends where you are clicking on Get Started. If you

Re: Royale Docs Changes Proposal

In my opinion it depends where you are clicking on Get Started. If you are clicking on Get Started on main page (main menu or footer) you should stay in the same window. I think it should be true for whatever option in main menu you are clicking. However if you are in Docs already and click on "Ap

Re: Royale Docs Changes Proposal

Hi Andrew, ok, so website navigation happens on the same window and docs in its own window. That's ok for me too. What to do with the case of pages like "Get Started"? The link is in website, but goes to royale docs thanks El jue., 16 may. 2019 a las 20:41, Andrew Wetmore () escribió: > I th

Re: About having an Apache Royale page on Wikipedia

Here’s one: https://marketinginflection.com/printui-demo.php > On May 17, 2019, at 1:27 AM, Andrew Wetmore wrote: > > I believe there are a couple of live applications using Royale. Do we have > links to them I could reference on the Wikipedia