Build failed in Jenkins: royale-asjs_MXTests #773

[Apache Royale CI Server]

See 


--
[...truncated 2.11 MB...]
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/MetaDataDefinition.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ISpinnerView.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/SpinnerView.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IViewportModel.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/WrappedHTMLElement.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/spark/layouts/supportClasses/DropLocation.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/layout/LayoutData.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/errors/CursorError.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/TextLineMetrics.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/styles/CSSStyleDeclaration.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/utils/FocusEventConverter.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/MethodDefinition.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/display/Graphics.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/ScrollControlBase.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/listClasses/ListBase.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IDataProviderVirtualItemRendererMapper.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/WatcherBase.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IImage.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/BrowserEvent.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/PanelModel.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/beads/models/PanelModel.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IPopUp.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/ButtonTestScript.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/spark/scripts/ButtonTestScript.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/ComboBase.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/DateField.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/RoyaleContext.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/ContainerBaseStrandChildren.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/BinaryData.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/UIUtils.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/ListSingleSelectionMouseController.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/MenuBarMouseController.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/controllers/MenuBarMouseController.js
[mxmlc] 
c:/jenkins/workspace/royale-asjs_MXTests/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/e

Build failed in Jenkins: royale-asjs_MXTests #772

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

Re: About having an Apache Royale page on Wikipedia

[Andrew Wetmore]

I believe there are a couple of live applications using Royale. Do we have
links to them I could reference on the Wikipedia page, or are they internal
company apps?

On Thu, May 16, 2019 at 3:28 PM Carlos Rovira 
wrote:

> Great Andrew! Thanks! :)
>
> El jue., 16 may. 2019 a las 20:23, Andrew Wetmore ()
> escribió:
>
> > I can do that! I am a Wikipedia editor, although not active enough to
> avoid
> > close scrutiny of what I write.
> >
> > The article will outline the origins, purpose, development, and
> particular
> > characteristics of Royale. Once I have the first version up and
> published,
> > we can work on improving it.
> >
> > On Thu, May 16, 2019 at 12:11 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Andrew,
> > >
> > > what do you think about to create a page in Wikipedia for Apache
> Royale?
> > > Then we can link from the website.
> > >
> > > I think that's a task where you can help a lot and where your writing
> and
> > > editing skills will be most needed that any other skills.
> > >
> > > Let us know what you think! :)
> > >
> > > Thank you
> > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> > >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Royale Docs Changes Proposal

[Andrew Wetmore]

I think "target=_blank" should be for links to location outside of Royale
docs. To me, that includes the Royale website. I would want it to open in a
new window rather than taking over the window I am using to read the docs.

On Thu, May 16, 2019 at 7:11 AM Carlos Rovira 
wrote:

> Hi Adrian,
>
> I read the Get Started page. Good work! :)
>
> just added a link that I think was missed, change it if you think it should
> point to other page.
>
> I want to ask about the links strategy. I see some of them that refers to
> the same Royale-docs part has target blank while other not.
> We talked about this when launched the website: In the website we put all
> links to be loaded on the same page, while external links to the site load
> in a blank page. I think we should do the same for Royale-docs. We just
> need to consider if website and Royale-docs must load in the same page. For
> example in website, a link to NPM will load in another page while mailing
> list info will load in the current one.
>
> thanks!
>
>
>
> El jue., 16 may. 2019 a las 11:07, Carlos Rovira ( >)
> escribió:
>
> > Hi
> >
> > I tried various plugin solutions for WP and no one seems to fit what we
> > need. So I changed the url to the docs page as suggested. Going to
> publish
> > the site.
> >
> > I see the styles in headers and other things are not matching the site
> > styles. I'll try to fix that soon.
> >
> > Thanks
> >
> >
> > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> carlosrov...@apache.org>)
> > escribió:
> >
> >> Hi, I'm looking into this now: How to make website render the content of
> >> a GitHub page.
> >> About Menu I'll change to "Get Started" as Piotr suggested
> >>
> >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> >> adrianszuszkiew...@gmail.com>) escribió:
> >>
> >>> 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/
> >>>
> >>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: About having an Apache Royale page on Wikipedia

[Carlos Rovira]

Great Andrew! Thanks! :)

El jue., 16 may. 2019 a las 20:23, Andrew Wetmore ()
escribió:

> I can do that! I am a Wikipedia editor, although not active enough to avoid
> close scrutiny of what I write.
>
> The article will outline the origins, purpose, development, and particular
> characteristics of Royale. Once I have the first version up and published,
> we can work on improving it.
>
> On Thu, May 16, 2019 at 12:11 PM Carlos Rovira 
> wrote:
>
> > Hi Andrew,
> >
> > what do you think about to create a page in Wikipedia for Apache Royale?
> > Then we can link from the website.
> >
> > I think that's a task where you can help a lot and where your writing and
> > editing skills will be most needed that any other skills.
> >
> > Let us know what you think! :)
> >
> > Thank you
> >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>


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

Re: About having an Apache Royale page on Wikipedia

[Andrew Wetmore]

I can do that! I am a Wikipedia editor, although not active enough to avoid
close scrutiny of what I write.

The article will outline the origins, purpose, development, and particular
characteristics of Royale. Once I have the first version up and published,
we can work on improving it.

On Thu, May 16, 2019 at 12:11 PM Carlos Rovira 
wrote:

> Hi Andrew,
>
> what do you think about to create a page in Wikipedia for Apache Royale?
> Then we can link from the website.
>
> I think that's a task where you can help a lot and where your writing and
> editing skills will be most needed that any other skills.
>
> Let us know what you think! :)
>
> Thank you
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

About having an Apache Royale page on Wikipedia

[Carlos Rovira]

Hi Andrew,

what do you think about to create a page in Wikipedia for Apache Royale?
Then we can link from the website.

I think that's a task where you can help a lot and where your writing and
editing skills will be most needed that any other skills.

Let us know what you think! :)

Thank you



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

[GitHub] [royale-docs] carlosrovira merged pull request #21: Improve toc menu expanding behavior

[GitBox]

carlosrovira merged pull request #21: Improve toc menu expanding behavior
URL: https://github.com/apache/royale-docs/pull/21
 
 
   


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

Build failed in Jenkins: royale-asjs_MXTests #771

[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 #21: Improve toc menu expanding behavior

[GitBox]

Aszusz opened a new pull request #21: Improve toc menu expanding behavior
URL: https://github.com/apache/royale-docs/pull/21
 
 
   This feature improves ToC menu expanding behavior. It makes the menu always 
expend the current item if it has any children. This allows the user to see 
where he/she can go next.
   
   Short video demonstration:
   
[05-16_15-07-44_desk.zip](https://github.com/apache/royale-docs/files/3187183/05-16_15-07-44_desk.zip)
   
   It also fixes a bug where both Welcome to Apache Royale and Get Started 
menus where both expended at the same time.
   
   


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

[Carlos Rovira]

Hi Piotr,

yes! I changed it, but still is in pre wp site, still didn't push it to
live. Will push in the next hours! :)

El jue., 16 may. 2019 a las 12:15, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:

> Hi Carlos,
>
> What about my proposal, cause you seems to missing that:
>
> ""Get Started" in the main menu on the website and "Getting Started" in the
> footer are pointing us to the same page, However words are different - What
> do you think to align them and have in footer "Get Started" as well?"
>
> Do you in favor of that ?
>
> czw., 16 maj 2019 o 12:11 Carlos Rovira 
> napisał(a):
>
> > Hi Adrian,
> >
> > I read the Get Started page. Good work! :)
> >
> > just added a link that I think was missed, change it if you think it
> should
> > point to other page.
> >
> > I want to ask about the links strategy. I see some of them that refers to
> > the same Royale-docs part has target blank while other not.
> > We talked about this when launched the website: In the website we put all
> > links to be loaded on the same page, while external links to the site
> load
> > in a blank page. I think we should do the same for Royale-docs. We just
> > need to consider if website and Royale-docs must load in the same page.
> For
> > example in website, a link to NPM will load in another page while mailing
> > list info will load in the current one.
> >
> > thanks!
> >
> >
> >
> > El jue., 16 may. 2019 a las 11:07, Carlos Rovira (<
> carlosrov...@apache.org
> > >)
> > escribió:
> >
> > > Hi
> > >
> > > I tried various plugin solutions for WP and no one seems to fit what we
> > > need. So I changed the url to the docs page as suggested. Going to
> > publish
> > > the site.
> > >
> > > I see the styles in headers and other things are not matching the site
> > > styles. I'll try to fix that soon.
> > >
> > > Thanks
> > >
> > >
> > > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> > carlosrov...@apache.org>)
> > > escribió:
> > >
> > >> Hi, I'm looking into this now: How to make website render the content
> of
> > >> a GitHub page.
> > >> About Menu I'll change to "Get Started" as Piotr suggested
> > >>
> > >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> > >> adrianszuszkiew...@gmail.com>) escribió:
> > >>
> > >>> 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/
> > >>>
> > >>
> > >>
> > >> --
> > >> Carlos Rovira
> > >> http://about.me/carlosrovira
> > >>
> > >>
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> > >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


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

Re: Royale Docs Changes Proposal

[Piotr Zarzycki]

Hi Carlos,

What about my proposal, cause you seems to missing that:

""Get Started" in the main menu on the website and "Getting Started" in the
footer are pointing us to the same page, However words are different - What
do you think to align them and have in footer "Get Started" as well?"

Do you in favor of that ?

czw., 16 maj 2019 o 12:11 Carlos Rovira 
napisał(a):

> Hi Adrian,
>
> I read the Get Started page. Good work! :)
>
> just added a link that I think was missed, change it if you think it should
> point to other page.
>
> I want to ask about the links strategy. I see some of them that refers to
> the same Royale-docs part has target blank while other not.
> We talked about this when launched the website: In the website we put all
> links to be loaded on the same page, while external links to the site load
> in a blank page. I think we should do the same for Royale-docs. We just
> need to consider if website and Royale-docs must load in the same page. For
> example in website, a link to NPM will load in another page while mailing
> list info will load in the current one.
>
> thanks!
>
>
>
> El jue., 16 may. 2019 a las 11:07, Carlos Rovira ( >)
> escribió:
>
> > Hi
> >
> > I tried various plugin solutions for WP and no one seems to fit what we
> > need. So I changed the url to the docs page as suggested. Going to
> publish
> > the site.
> >
> > I see the styles in headers and other things are not matching the site
> > styles. I'll try to fix that soon.
> >
> > Thanks
> >
> >
> > El jue., 16 may. 2019 a las 10:42, Carlos Rovira (<
> carlosrov...@apache.org>)
> > escribió:
> >
> >> Hi, I'm looking into this now: How to make website render the content of
> >> a GitHub page.
> >> About Menu I'll change to "Get Started" as Piotr suggested
> >>
> >> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> >> adrianszuszkiew...@gmail.com>) escribió:
> >>
> >>> 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/
> >>>
> >>
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

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

Re: Royale Docs Changes Proposal

[Carlos Rovira]

Hi Adrian,

I read the Get Started page. Good work! :)

just added a link that I think was missed, change it if you think it should
point to other page.

I want to ask about the links strategy. I see some of them that refers to
the same Royale-docs part has target blank while other not.
We talked about this when launched the website: In the website we put all
links to be loaded on the same page, while external links to the site load
in a blank page. I think we should do the same for Royale-docs. We just
need to consider if website and Royale-docs must load in the same page. For
example in website, a link to NPM will load in another page while mailing
list info will load in the current one.

thanks!



El jue., 16 may. 2019 a las 11:07, Carlos Rovira ()
escribió:

> Hi
>
> I tried various plugin solutions for WP and no one seems to fit what we
> need. So I changed the url to the docs page as suggested. Going to publish
> the site.
>
> I see the styles in headers and other things are not matching the site
> styles. I'll try to fix that soon.
>
> Thanks
>
>
> El jue., 16 may. 2019 a las 10:42, Carlos Rovira ()
> escribió:
>
>> Hi, I'm looking into this now: How to make website render the content of
>> a GitHub page.
>> About Menu I'll change to "Get Started" as Piotr suggested
>>
>> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
>> adrianszuszkiew...@gmail.com>) escribió:
>>
>>> 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/
>>>
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

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

Re: Royale Docs Changes Proposal

[Carlos Rovira]

Hi

I tried various plugin solutions for WP and no one seems to fit what we
need. So I changed the url to the docs page as suggested. Going to publish
the site.

I see the styles in headers and other things are not matching the site
styles. I'll try to fix that soon.

Thanks


El jue., 16 may. 2019 a las 10:42, Carlos Rovira ()
escribió:

> Hi, I'm looking into this now: How to make website render the content of a
> GitHub page.
> About Menu I'll change to "Get Started" as Piotr suggested
>
> El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
> adrianszuszkiew...@gmail.com>) escribió:
>
>> 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/
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

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

Re: Royale Docs Changes Proposal

[Carlos Rovira]

Hi, I'm looking into this now: How to make website render the content of a
GitHub page.
About Menu I'll change to "Get Started" as Piotr suggested

El mié., 15 may. 2019 a las 11:05, Adrian Szuszkiewicz (<
adrianszuszkiew...@gmail.com>) escribió:

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


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

Re: Problems with Java 12

[Harbs]

They are both set to the same variable.

> On May 16, 2019, at 10:22 AM, Yishay Weiss  wrote:
> 
> Apparently [1] you’d need to set the source compatibility to 6 as well.
> 
> 
> 
> [1] 
> https://stackoverflow.com/questions/10663450/whats-the-difference-between-source-and-target-compatibility
> 
> 
> 
> 
> From: Alex Harui 
> Sent: Wednesday, May 15, 2019 6:54:13 PM
> To: dev@royale.apache.org
> Subject: Re: Problems with Java 12
> 
> 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
 
>>> 
>>> 
>>> 
>> 
>> 
>> 
> 
> 
> 

RE: Problems with Java 12

[Yishay Weiss]

Apparently [1] you’d need to set the source compatibility to 6 as well.



[1] 
https://stackoverflow.com/questions/10663450/whats-the-difference-between-source-and-target-compatibility




From: Alex Harui 
Sent: Wednesday, May 15, 2019 6:54:13 PM
To: dev@royale.apache.org
Subject: Re: Problems with Java 12

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