Build failed in Jenkins: royale-asjs_MXTests #6

[apacheroyaleci]

See 


Changes:

[aharui] WebService compiles except for XMLDocument and getTimer

[aharui] ByteArray also needs IDataInput/Output

[aharui] beginnings of implementation of WebService

[aharui] handle proxy in  PropertyWatcher

[aharui] handle null

[aharui] elements call wasn't returning everything by default

[aharui] Emulation should use ClassAliasBead

[aharui] setup context root for JS at runtime instead of compile time

[aharui] fix JS ObjectUtil

[aharui] handle context root for JS at runtime

[aharui] SortOn actually always returns an Array

[aharui] output homedrive/homepath so we can try to see why new CI server can't

[carlosrovira] jewel-imagebutton: remove default browser outline and imports not

[carlosrovira] update all jewel themes


--
[...truncated 1.11 MB...]
[mxmlc] scanning for overrides: ObjectUtil
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: IStroke
[mxmlc] scanning for overrides: CursorError
[mxmlc] scanning for overrides: SortError
[mxmlc] scanning for overrides: ISort
[mxmlc] scanning for overrides: Sort
[mxmlc] scanning for overrides: IXMLNotifiable
[mxmlc] scanning for overrides: XMLListAdapter
[mxmlc] scanning for overrides: FlexChildInfo
[mxmlc] 

Build failed in Jenkins: royale-asjs #44

[apacheroyaleci]

See 


Changes:


--
[...truncated 1.15 MB...]
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [https]:23: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var http = require('http');
 [java]^^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [https]:24: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var tls = require('tls');
 [java]   ^^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [https]:84: WARNING - name module is not defined in the 
externs.
 [java] module.exports = https;
 [java] ^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [net]:23: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [net]:219: WARNING - name module is not defined in the 
externs.
 [java] module.exports = net;
 [java] ^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [os]:113: WARNING - name module is not defined in the 
externs.
 [java] module.exports = os;
 [java] ^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [path]:97: WARNING - name module is not defined in the 
externs.
 [java] module.exports = path;
 [java] ^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [punycode]:74: WARNING - name module is not defined in the 
externs.
 [java] module.exports = punycode;
 [java] ^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [querystring]:66: WARNING - name module is not defined in 
the externs.
 [java] module.exports = querystring;
 [java] ^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:22: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:23: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:84: WARNING - name module is not defined in the 
externs.
 [java] module.exports = readline;
 [java] ^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:23: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:24: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:48: WARNING - name module is not defined in the 
externs.
 [java] module.exports = repl;
 [java] ^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [stream]:23: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [stream]:254: WARNING - name module is not defined in the 
externs.
 [java] module.exports = stream;
 [java] ^^
 [java] 
 [java] Oct 17, 2019 4:30:53 AM 

Re: [Discussion] Where Nightly builds links must be located (we must remove it from download page)

[Alex Harui]

I think our invitation to become a committer by getting source code or getting 
involved should be emphasized more, but I'm not doing the work on the website.  
IMO, we've hit the point of diminishing returns.  Carlos should do something 
quick and simple to make the ASF happy unless he has time and energy to do more.

In theory, we should be friendly enough to add the link to the nightlies in the 
emails we send to folks on dev@ so they don't have to go looking for it on our 
website.  And if they forgot and deleted the email with the link, it is in the 
archives.   It really should be rare for someone to need to remind themselves 
of the link by finding it on the website.

My 2 cents,
-Alex

On 10/16/19, 2:10 PM, "Harbs"  wrote:

Maybe something like this would be better?

Source Code

For developers who want to get involved in framework development, source 
code and nightly build download links can be found on our get involved page 
.

> On Oct 16, 2019, at 11:36 PM, Alex Harui  wrote:
> 
> I'm not sure how that is better than the disclaimer that was there.  But 
if you feel it is important, we'll find out when the page gets reviewed again.
> 
> -Alex
> 
> On 10/16/19, 12:44 PM, "Harbs"  wrote:
> 
>I think we should add a section to the download page about nightly 
builds. Someone who is looking for the nightly builds might not know where to 
find it.
> 
>Something like:
> 
>We do not recommend nightly builds for application developers as they 
have not been properly tested and can have serious bugs. Nightly builds are 
useful if you want to get involved in framework development are are prepared to 
work with bleeding edge code. Source code and nightly build download links can 
be found on our “get involved” page[link].
> 
>Harbs
> 
>> On Oct 16, 2019, at 10:36 PM, Carlos Rovira  
wrote:
>> 
>> Hi,
>> 
>> I did it in pre:
>> 
>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.codeoscopic.com%2Fdownload%2Fdata=02%7C01%7Caharui%40adobe.com%7C64952ecd61b0454f330308d7527d4741%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068570328531253sdata=8FZhtsvW5EJG8TmW4S%2BAdk7AtbsO%2Bl6UIB%2BfzLZ5YSA%3Dreserved=0
>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.codeoscopic.com%2Fget-involved%2Fdata=02%7C01%7Caharui%40adobe.com%7C64952ecd61b0454f330308d7527d4741%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068570328531253sdata=xBp3SsuxsqWdXaDEUDLWZChgra%2BDUVJqr1bCUFyNGMA%3Dreserved=0
>> 
>> will push it tomorrow if nobody suggest any other change
>> 
>> thanks
>> 
>> Carlos
>> 
>> 
>> 
>> El mié., 16 oct. 2019 a las 21:27, Alex Harui 
()
>> escribió:
>> 
>>> Sounds ok to me.
>>> 
>>> On 10/16/19, 12:21 PM, "Carlos Rovira"  wrote:
>>> 
>>>   Hi,
>>> 
>>>   thanks all for sharing ideas on how to deal with this issue. For what 
I
>>>   read I like some of them.
>>> 
>>>   We already have a "Get Involved" page (most of the time with forget we
>>> have
>>>   menu options in the footer bar and top level menu options are only a
>>> subset
>>>   of what we think "most important" for newcomers).
>>>   With that page in mind, I think we have solve the "creation of a new
>>> page".
>>>   We can use that.
>>> 
>>>   What I see more easy is then is to move the nightly builds section to
>>> that
>>>   page, so we are done.
>>> 
>>>   Let me know what you think.
>>> 
>>>   Carlos
>>> 
>>> 
>>> 
>>>   El mié., 16 oct. 2019 a las 18:38, Alex Harui
>>> ()
>>>   escribió:
>>> 
 The principle behind the policy is not ridiculous.  AIUI, it is
>>> important
 that the general public only downloads artifacts that the PMC has
>>> approved
 as an act of the foundation, otherwise the foundation's ability to
>>> provide
 a legal shield for release managers is weakened.
 
 I mostly agree that the way the word "might" in the policy is being
 interpreted is "ridiculous".  I really don't think the general
>>> public is
 being encouraged to download our nightly builds the way the current
>>> site
 reads.  However, both Justin and I warned about the wording on the
>>> download
 page [1] before it went live because we've seen other projects get
 disrupted by similar nitpicking.  AFAICT, the trend at the ASF is to
 continue to be more restrictive about the word "might" 

Build failed in Jenkins: royale-asjs #43

[apacheroyaleci]

See 


Changes:


--
[...truncated 2.15 MB...]
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var excludedCount:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var valueChanged:Boolean;
 [java] ^
 [java] 
 [java] 4.4088879 seconds
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
 [java] Java Result: 2

compile-js:

main:

basictests-compile-java:
   [delete] Deleting directory 

[mkdir] Created dir: 

[javac] 
:1317:
 warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 12 source files to 

[javac] Note: 

 uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.

basictests:
[mxmlc] MXMLJSC
[mxmlc] 
-sdk-js-lib=
[mxmlc] +env.PLAYERGLOBAL_HOME=C:\adobe\flash
[mxmlc] -compiler.debug=true
[mxmlc] 
+royalelib=
[mxmlc] 
-closure-lib=
[mxmlc] 
-compiler.library-path+=
[mxmlc] 
-compiler.js-external-library-path=
[mxmlc] 
-compiler.js-library-path=
[mxmlc] 
-compiler.js-library-path+=
[mxmlc] --
[mxmlc] 

[mxmlc] Loading configuration: 

[mxmlc] Loading configuration: 

[mxmlc] 
[mxmlc] scanning for overrides: IFlexInfo
[mxmlc] scanning for overrides: ApplicationBase
[mxmlc] scanning for overrides: IEventDispatcher
[mxmlc] scanning for overrides: IInitialViewApplication
[mxmlc] scanning for overrides: IParent
[mxmlc] scanning for overrides: IPopUpHost
[mxmlc] scanning for overrides: IPopUpHostParent
[mxmlc] scanning for overrides: IRenderedObject
[mxmlc] scanning for overrides: IStrand
[mxmlc] scanning for overrides: Application
[mxmlc] scanning for overrides: BasicTestsApp
[mxmlc] scanning for overrides: DontSendScriptComplete
[mxmlc] scanning for overrides: ExitWhenDone
[mxmlc] scanning for overrides: SendFormattedResultsToLog
[mxmlc] scanning for overrides: RoyaleContext
[mxmlc] scanning for overrides: UnitTester
[mxmlc] scanning for overrides: ButtonTestScript
[mxmlc] scanning for overrides: CheckBoxTestScript
[mxmlc] scanning for overrides: HTMLElementWrapper
[mxmlc] scanning for overrides: IId
[mxmlc] scanning for overrides: IChild
[mxmlc] scanning for overrides: IUIBase
[mxmlc] scanning for overrides: ILayoutChild
[mxmlc] scanning for overrides: IParentIUIBase
[mxmlc] scanning for overrides: IRoyaleElement
[mxmlc] scanning for overrides: IStrandWithModel
[mxmlc] scanning for overrides: IStrandWithModelView
[mxmlc] scanning for overrides: IStyleableObject
[mxmlc] scanning for overrides: UIBase
[mxmlc] scanning for overrides: IContainer
[mxmlc] scanning for overrides: IContentViewHost
[mxmlc] scanning for overrides: 

New apache-royale questions for Oct 16 - Stack Exchange

[Stack Exchange]

***1 new question in [ApacheRoyale Tag Notifications 
filter]()
 on stackexchange.com***


[DataGrid cell background color issue on Apache 
Royale]()

Let't take this code js:Application 
xmlns:fx="http://ns.adobe.com/mxml/2009; 
xmlns:j="library://ns.apache.org/royale/jewel" ...

Tagged: datagrid

by [Fred]() on 






[Unsubscribe from this 
filter]()
 or change your email preferences by visitingyour [filter subscriptions page on 
stackexchange.com]().

If you no longer want to receive mail from Stack Exchange, unsubscribe from all 
stackexchange.com emails 

Questions? Comments? Let us know on our feedback site at 
.

Stack Exchange, Inc. 110 William St, 28th Floor, NY NY 10038

Build failed in Jenkins: royale-asjs #42

[apacheroyaleci]

See 


Changes:

[carlosrovira] jewel-imagebutton: remove default browser outline and imports not

[carlosrovira] update all jewel themes


--
[...truncated 2.15 MB...]
 [java] public var lastEvent:Event;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var excludedCount:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var valueChanged:Boolean;
 [java] ^
 [java] 
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
 [java] Java Result: 2

compile-js:

main:

basictests-compile-java:
   [delete] Deleting directory 

[mkdir] Created dir: 

[javac] 
:1317:
 warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 12 source files to 

[javac] Note: 

 uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.

basictests:
[mxmlc] MXMLJSC
[mxmlc] 
-sdk-js-lib=
[mxmlc] +env.PLAYERGLOBAL_HOME=C:\adobe\flash
[mxmlc] -compiler.debug=true
[mxmlc] 
+royalelib=
[mxmlc] 
-closure-lib=
[mxmlc] 
-compiler.library-path+=
[mxmlc] 
-compiler.js-external-library-path=
[mxmlc] 
-compiler.js-library-path=
[mxmlc] 
-compiler.js-library-path+=
[mxmlc] --
[mxmlc] 

[mxmlc] Loading configuration: 

[mxmlc] Loading configuration: 

[mxmlc] 
[mxmlc] scanning for overrides: IFlexInfo
[mxmlc] scanning for overrides: ApplicationBase
[mxmlc] scanning for overrides: IEventDispatcher
[mxmlc] scanning for overrides: IInitialViewApplication
[mxmlc] scanning for overrides: IParent
[mxmlc] scanning for overrides: IPopUpHost
[mxmlc] scanning for overrides: IPopUpHostParent
[mxmlc] scanning for overrides: IRenderedObject
[mxmlc] scanning for overrides: IStrand
[mxmlc] scanning for overrides: Application
[mxmlc] scanning for overrides: BasicTestsApp
[mxmlc] scanning for overrides: DontSendScriptComplete
[mxmlc] scanning for overrides: ExitWhenDone
[mxmlc] scanning for overrides: SendFormattedResultsToLog
[mxmlc] scanning for overrides: RoyaleContext
[mxmlc] scanning for overrides: UnitTester
[mxmlc] scanning for overrides: ButtonTestScript
[mxmlc] scanning for overrides: CheckBoxTestScript
[mxmlc] scanning for overrides: HTMLElementWrapper
[mxmlc] scanning for overrides: IId
[mxmlc] scanning for overrides: IChild
[mxmlc] scanning for overrides: IUIBase
[mxmlc] scanning for overrides: ILayoutChild
[mxmlc] scanning for overrides: IParentIUIBase
[mxmlc] scanning for overrides: IRoyaleElement
[mxmlc] scanning for overrides: IStrandWithModel
[mxmlc] scanning for overrides: IStrandWithModelView
[mxmlc] scanning for overrides: IStyleableObject
[mxmlc] scanning for overrides: 

Re: Testimonials Page (Was: Re: About Royale Docs Improvements over latest months)

[Carlos Rovira]

Hi folks,

please remember we have this request open. It's very few time for you you
all, just invest 5 minutes in send a phrase, name, job and picture to
appear in out testimonials page :)

This can sum to the rest of things that will make others want to use Royale


El vie., 4 oct. 2019 a las 10:19, Carlos Rovira ()
escribió:

> Thanks Andrew!
>
> I look forward to at least 2 more (better 3) to be able to mount the
> page. We look forward to your help in this regard! :)
>
>
> El jue., 3 oct. 2019 a las 22:40, Andrew Wetmore ()
> escribió:
>
>> "Apache Royale captures the best of Apache Flex and the best of new trends
>> in web development, so it's the best of both worlds. We migrated a Flex
>> application to JavaScript in significantly less time than it would have
>> taken using the most popular JavaScript frameworks. The productivity,
>> programming model and combination of OOP and declarative languages make
>> Apache Royale a very solid development environment and a lot of fun to
>> work
>> with! :)"
>>
>> On Thu, Oct 3, 2019 at 3:30 PM Carlos Rovira 
>> wrote:
>>
>> > Hi,
>> >
>> > Here's main that could serve as well as example (@Andrew if you can fix
>> any
>> > grammar disaster I could make, please go ahead! :D) :
>> >
>> > -
>> >
>> > "Apache Royale captures the best of Apache Flex and the best of new
>> trends
>> > in web development, so it's best of both worlds. We migrated a Flex
>> > application to javascript in significant less time than using the
>> current
>> > top notch javascript frameworks out there. The productivity, the
>> programing
>> > model and the combination of OOP and declarative languages makes it a
>> very
>> > solid tech and very fun to work with! :)"
>> >
>> > Carlos Rovira
>> > Executive Chairman at Codeoscopic
>> >
>> > profile img to use: EB6igxEXYAE-PvU
>> > 
>> >
>> > --
>> >
>> > I think is a small contribution that could be of help in our site.
>> Harbs,
>> > Yishay, Piotr, and the rest...please take this request into
>> consideration
>> > so we can fill the page with at least 4+ of this.
>> >
>> > thanks
>> >
>> > El mar., 1 oct. 2019 a las 20:54, Carlos Rovira (<
>> carlosrov...@apache.org
>> > >)
>> > escribió:
>> >
>> > > Hi all,
>> > >
>> > > we are talking about add a new "Testimonials" page were people could
>> > share
>> > > "How ApacheRoyale has helped" (you, your project, your company...)
>> with a
>> > > new app, or a migration from Flex.
>> > >
>> > > Please submit to this thread a phrase or a paragraph that will capture
>> > > that topic for you and help us to fill that page with useful
>> information
>> > > for others that come to Apache Royale.
>> > > (Note: Take into account that anyone that do this contribution is
>> under
>> > > the assumption that allows us to use his phrase, name and info
>> submitted
>> > in
>> > > out website as a Testimonial in that page and submitting implies give
>> us
>> > > permission to do that :))
>> > >
>> > > Please provide an image as well for the profile. It can be your
>> portrait,
>> > > or if you don't want your photo in our website, you can send us other
>> > > image(photo, logo or graphic) that represents you, to enhance the
>> > > testimonial. We reserve the option to use it or not depending on the
>> > image
>> > > provided if we think is not appropriate or could infringe some
>> copyright
>> > or
>> > > rule. For this reason, please try to use original content and nothing
>> > that
>> > > could be offensive or problematic with any of the Apache rules or the
>> > > common sense :)
>> > >
>> > > This will help others to decide to join us or use Royale since others
>> had
>> > > success in using it.
>> > >
>> > > Thanks all for your contribution to this page!! That will be of great
>> > > help! :)
>> > >
>> > > Carlos
>> > >
>> > >
>> > >
>> > > El mar., 1 oct. 2019 a las 20:39, Carlos Rovira (<
>> > carlosrov...@apache.org>)
>> > > escribió:
>> > >
>> > >> Hi,
>> > >> we can add testimonials page (as an additional page a part from
>> showcase
>> > >> page). The actual theme has that integrated that will be easy to do.
>> > >> Will start a thread so others can write its own testimonial to be
>> added.
>> > >>
>> > >> Thanks for the suggestion :)
>> > >>
>> > >>
>> > >>
>> > >> El mar., 1 oct. 2019 a las 19:37, Alex Harui
>> (> > >)
>> > >> escribió:
>> > >>
>> > >>> The showcase would be great, but if it is easier/faster to simply
>> have
>> > a
>> > >>> page of links to blogs of our committers like you and Harbs that
>> just
>> > >>> contain a paragraph or two about how Royale has helped, that might
>> be a
>> > >>> good place to start.
>> > >>>
>> > >>> -Alex
>> > >>>
>> > >>> On 10/1/19, 10:02 AM, "Carlos Rovira" 
>> > wrote:
>> > >>>
>> > >>> Hi Alex,
>> > >>>
>> > >>> El mar., 1 oct. 2019 a las 17:50, Alex Harui
>> > >>> ()
>> > >>> escribió:
>> > >>>
>> > >>> > Thanks for working on the docs.
>> > >>> 

Re: [Discussion] Where Nightly builds links must be located (we must remove it from download page)

[Harbs]

Maybe something like this would be better?

Source Code

For developers who want to get involved in framework development, source code 
and nightly build download links can be found on our get involved page 
.

> On Oct 16, 2019, at 11:36 PM, Alex Harui  wrote:
> 
> I'm not sure how that is better than the disclaimer that was there.  But if 
> you feel it is important, we'll find out when the page gets reviewed again.
> 
> -Alex
> 
> On 10/16/19, 12:44 PM, "Harbs"  wrote:
> 
>I think we should add a section to the download page about nightly builds. 
> Someone who is looking for the nightly builds might not know where to find it.
> 
>Something like:
> 
>We do not recommend nightly builds for application developers as they have 
> not been properly tested and can have serious bugs. Nightly builds are useful 
> if you want to get involved in framework development are are prepared to work 
> with bleeding edge code. Source code and nightly build download links can be 
> found on our “get involved” page[link].
> 
>Harbs
> 
>> On Oct 16, 2019, at 10:36 PM, Carlos Rovira  wrote:
>> 
>> Hi,
>> 
>> I did it in pre:
>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.codeoscopic.com%2Fdownload%2Fdata=02%7C01%7Caharui%40adobe.com%7Cdd9337709d634d42b24808d752713be1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068518597745376sdata=lPNkT%2Ba%2BS%2BpjtmVchfpX726g4a4zlgTMhf8SUYeh2xc%3Dreserved=0
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.codeoscopic.com%2Fget-involved%2Fdata=02%7C01%7Caharui%40adobe.com%7Cdd9337709d634d42b24808d752713be1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068518597745376sdata=kFpobNSVuN1%2FItk5YMO%2BzikIzqzMYq%2FFnqf8jQUJ68w%3Dreserved=0
>> 
>> will push it tomorrow if nobody suggest any other change
>> 
>> thanks
>> 
>> Carlos
>> 
>> 
>> 
>> El mié., 16 oct. 2019 a las 21:27, Alex Harui ()
>> escribió:
>> 
>>> Sounds ok to me.
>>> 
>>> On 10/16/19, 12:21 PM, "Carlos Rovira"  wrote:
>>> 
>>>   Hi,
>>> 
>>>   thanks all for sharing ideas on how to deal with this issue. For what I
>>>   read I like some of them.
>>> 
>>>   We already have a "Get Involved" page (most of the time with forget we
>>> have
>>>   menu options in the footer bar and top level menu options are only a
>>> subset
>>>   of what we think "most important" for newcomers).
>>>   With that page in mind, I think we have solve the "creation of a new
>>> page".
>>>   We can use that.
>>> 
>>>   What I see more easy is then is to move the nightly builds section to
>>> that
>>>   page, so we are done.
>>> 
>>>   Let me know what you think.
>>> 
>>>   Carlos
>>> 
>>> 
>>> 
>>>   El mié., 16 oct. 2019 a las 18:38, Alex Harui
>>> ()
>>>   escribió:
>>> 
 The principle behind the policy is not ridiculous.  AIUI, it is
>>> important
 that the general public only downloads artifacts that the PMC has
>>> approved
 as an act of the foundation, otherwise the foundation's ability to
>>> provide
 a legal shield for release managers is weakened.
 
 I mostly agree that the way the word "might" in the policy is being
 interpreted is "ridiculous".  I really don't think the general
>>> public is
 being encouraged to download our nightly builds the way the current
>>> site
 reads.  However, both Justin and I warned about the wording on the
>>> download
 page [1] before it went live because we've seen other projects get
 disrupted by similar nitpicking.  AFAICT, the trend at the ASF is to
 continue to be more restrictive about the word "might" and make it
>>> harder
 to find links to nightly builds on project websites.  Other projects
>>> that
 used to have links or links "below the fold" no longer do when I went
 looking just now.  It won't be worth it to fight it, so let's just
>>> plan on
 changing.
 
 I see other projects with separate pages, but there is always a
>>> chance
 that someday the word "might" will be restricted even more to include
 separate pages.  I'm not making the changes to the site, so I'll
>>> leave it
 up to those who are doing the work to decide.
 
 IMO, with that in mind, when I look at the current site, it is almost
 entirely tuned towards our users.  The only place we invite folks to
 contribute is way down on the landing page.  And the page that takes
>>> you to
 is about mailing lists.  I guess you could say that the GitHub link
>>> is an
 implied indicator that we're an open source project and that you
>>> should
 contribute.
 
 So, here are my ideas.  Feel free to reject them all:
 
 1) Move the nightly build portion of the download page to a wiki
>>> page in
 GitHub.
 2) Add a "Get Involved" or "Contributing" menu item similar to what
>>> Harbs
 suggested that goes to a different page like Andrew suggested
 3) Replace the GitHub menu item with the 

Re: [Discussion] Where Nightly builds links must be located (we must remove it from download page)

[Alex Harui]

I'm not sure how that is better than the disclaimer that was there.  But if you 
feel it is important, we'll find out when the page gets reviewed again.

-Alex

On 10/16/19, 12:44 PM, "Harbs"  wrote:

I think we should add a section to the download page about nightly builds. 
Someone who is looking for the nightly builds might not know where to find it.

Something like:

We do not recommend nightly builds for application developers as they have 
not been properly tested and can have serious bugs. Nightly builds are useful 
if you want to get involved in framework development are are prepared to work 
with bleeding edge code. Source code and nightly build download links can be 
found on our “get involved” page[link].

Harbs

> On Oct 16, 2019, at 10:36 PM, Carlos Rovira  
wrote:
> 
> Hi,
> 
> I did it in pre:
> 
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.codeoscopic.com%2Fdownload%2Fdata=02%7C01%7Caharui%40adobe.com%7Cdd9337709d634d42b24808d752713be1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068518597745376sdata=lPNkT%2Ba%2BS%2BpjtmVchfpX726g4a4zlgTMhf8SUYeh2xc%3Dreserved=0
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.codeoscopic.com%2Fget-involved%2Fdata=02%7C01%7Caharui%40adobe.com%7Cdd9337709d634d42b24808d752713be1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068518597745376sdata=kFpobNSVuN1%2FItk5YMO%2BzikIzqzMYq%2FFnqf8jQUJ68w%3Dreserved=0
> 
> will push it tomorrow if nobody suggest any other change
> 
> thanks
> 
> Carlos
> 
> 
> 
> El mié., 16 oct. 2019 a las 21:27, Alex Harui ()
> escribió:
> 
>> Sounds ok to me.
>> 
>> On 10/16/19, 12:21 PM, "Carlos Rovira"  wrote:
>> 
>>Hi,
>> 
>>thanks all for sharing ideas on how to deal with this issue. For what 
I
>>read I like some of them.
>> 
>>We already have a "Get Involved" page (most of the time with forget we
>> have
>>menu options in the footer bar and top level menu options are only a
>> subset
>>of what we think "most important" for newcomers).
>>With that page in mind, I think we have solve the "creation of a new
>> page".
>>We can use that.
>> 
>>What I see more easy is then is to move the nightly builds section to
>> that
>>page, so we are done.
>> 
>>Let me know what you think.
>> 
>>Carlos
>> 
>> 
>> 
>>El mié., 16 oct. 2019 a las 18:38, Alex Harui
>> ()
>>escribió:
>> 
>>> The principle behind the policy is not ridiculous.  AIUI, it is
>> important
>>> that the general public only downloads artifacts that the PMC has
>> approved
>>> as an act of the foundation, otherwise the foundation's ability to
>> provide
>>> a legal shield for release managers is weakened.
>>> 
>>> I mostly agree that the way the word "might" in the policy is being
>>> interpreted is "ridiculous".  I really don't think the general
>> public is
>>> being encouraged to download our nightly builds the way the current
>> site
>>> reads.  However, both Justin and I warned about the wording on the
>> download
>>> page [1] before it went live because we've seen other projects get
>>> disrupted by similar nitpicking.  AFAICT, the trend at the ASF is to
>>> continue to be more restrictive about the word "might" and make it
>> harder
>>> to find links to nightly builds on project websites.  Other projects
>> that
>>> used to have links or links "below the fold" no longer do when I went
>>> looking just now.  It won't be worth it to fight it, so let's just
>> plan on
>>> changing.
>>> 
>>> I see other projects with separate pages, but there is always a
>> chance
>>> that someday the word "might" will be restricted even more to include
>>> separate pages.  I'm not making the changes to the site, so I'll
>> leave it
>>> up to those who are doing the work to decide.
>>> 
>>> IMO, with that in mind, when I look at the current site, it is almost
>>> entirely tuned towards our users.  The only place we invite folks to
>>> contribute is way down on the landing page.  And the page that takes
>> you to
>>> is about mailing lists.  I guess you could say that the GitHub link
>> is an
>>> implied indicator that we're an open source project and that you
>> should
>>> contribute.
>>> 
>>> So, here are my ideas.  Feel free to reject them all:
>>> 
>>> 1) Move the nightly build portion of the download page to a wiki
>> page in
>>> GitHub.
>>> 2) Add a "Get Involved" or "Contributing" menu item similar to what
>> Harbs
>>> suggested that goes to a different page like Andrew suggested
>>> 3) Replace the GitHub menu item with the 

Re: [Discussion] Where Nightly builds links must be located (we must remove it from download page)

[Carlos Rovira]

Updated with your suggestion Harbs: https://royale.codeoscopic.com/download/



El mié., 16 oct. 2019 a las 21:44, Harbs () escribió:

> I think we should add a section to the download page about nightly builds.
> Someone who is looking for the nightly builds might not know where to find
> it.
>
> Something like:
>
> We do not recommend nightly builds for application developers as they have
> not been properly tested and can have serious bugs. Nightly builds are
> useful if you want to get involved in framework development are are
> prepared to work with bleeding edge code. Source code and nightly build
> download links can be found on our “get involved” page[link].
>
> Harbs
>
> > On Oct 16, 2019, at 10:36 PM, Carlos Rovira 
> wrote:
> >
> > Hi,
> >
> > I did it in pre:
> >
> > https://royale.codeoscopic.com/download/
> > https://royale.codeoscopic.com/get-involved/
> >
> > will push it tomorrow if nobody suggest any other change
> >
> > thanks
> >
> > Carlos
> >
> >
> >
> > El mié., 16 oct. 2019 a las 21:27, Alex Harui ( >)
> > escribió:
> >
> >> Sounds ok to me.
> >>
> >> On 10/16/19, 12:21 PM, "Carlos Rovira" 
> wrote:
> >>
> >>Hi,
> >>
> >>thanks all for sharing ideas on how to deal with this issue. For
> what I
> >>read I like some of them.
> >>
> >>We already have a "Get Involved" page (most of the time with forget
> we
> >> have
> >>menu options in the footer bar and top level menu options are only a
> >> subset
> >>of what we think "most important" for newcomers).
> >>With that page in mind, I think we have solve the "creation of a new
> >> page".
> >>We can use that.
> >>
> >>What I see more easy is then is to move the nightly builds section to
> >> that
> >>page, so we are done.
> >>
> >>Let me know what you think.
> >>
> >>Carlos
> >>
> >>
> >>
> >>El mié., 16 oct. 2019 a las 18:38, Alex Harui
> >> ()
> >>escribió:
> >>
> >>> The principle behind the policy is not ridiculous.  AIUI, it is
> >> important
> >>> that the general public only downloads artifacts that the PMC has
> >> approved
> >>> as an act of the foundation, otherwise the foundation's ability to
> >> provide
> >>> a legal shield for release managers is weakened.
> >>>
> >>> I mostly agree that the way the word "might" in the policy is being
> >>> interpreted is "ridiculous".  I really don't think the general
> >> public is
> >>> being encouraged to download our nightly builds the way the current
> >> site
> >>> reads.  However, both Justin and I warned about the wording on the
> >> download
> >>> page [1] before it went live because we've seen other projects get
> >>> disrupted by similar nitpicking.  AFAICT, the trend at the ASF is to
> >>> continue to be more restrictive about the word "might" and make it
> >> harder
> >>> to find links to nightly builds on project websites.  Other projects
> >> that
> >>> used to have links or links "below the fold" no longer do when I went
> >>> looking just now.  It won't be worth it to fight it, so let's just
> >> plan on
> >>> changing.
> >>>
> >>> I see other projects with separate pages, but there is always a
> >> chance
> >>> that someday the word "might" will be restricted even more to include
> >>> separate pages.  I'm not making the changes to the site, so I'll
> >> leave it
> >>> up to those who are doing the work to decide.
> >>>
> >>> IMO, with that in mind, when I look at the current site, it is almost
> >>> entirely tuned towards our users.  The only place we invite folks to
> >>> contribute is way down on the landing page.  And the page that takes
> >> you to
> >>> is about mailing lists.  I guess you could say that the GitHub link
> >> is an
> >>> implied indicator that we're an open source project and that you
> >> should
> >>> contribute.
> >>>
> >>> So, here are my ideas.  Feel free to reject them all:
> >>>
> >>> 1) Move the nightly build portion of the download page to a wiki
> >> page in
> >>> GitHub.
> >>> 2) Add a "Get Involved" or "Contributing" menu item similar to what
> >> Harbs
> >>> suggested that goes to a different page like Andrew suggested
> >>> 3) Replace the GitHub menu item with the "Get Involved" or
> >> "Contributing"
> >>> menu item
> >>> 4) Add analytics to the nightly build links so we can see how many
> >> people
> >>> click it
> >>> 5) Add a popup to the link to the nightly build so folks must agree
> >> to the
> >>> disclaimers.
> >>>
> >>> I recommend that we just do #1 and move on.  We've got plenty of
> >> other
> >>> things to work on.
> >>>
> >>> My 2 cents,
> >>> -Alex
> >>>
> >>> [1]
> >>>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F8564ab5687c631bd4961bf8b987a5e9d30d6673d5050f72b8a9aaa53%40%253Cdev.royale.apache.org%253Edata=02%7C01%7Caharui%40adobe.com%7C3069e9eec31c4fc643fd08d7526e02de%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068504849942445sdata=2LPwIowIFGZmQ%2FzCMYeq8xPcXKJKBQPPkqpX41U3V40%3Dreserved=0
> >>>
> 

Build failed in Jenkins: royale-asjs #41

[apacheroyaleci]

See 


Changes:

[aharui] WebService compiles except for XMLDocument and getTimer

[aharui] ByteArray also needs IDataInput/Output

[aharui] beginnings of implementation of WebService

[aharui] handle proxy in  PropertyWatcher

[aharui] handle null

[aharui] elements call wasn't returning everything by default

[aharui] Emulation should use ClassAliasBead

[aharui] setup context root for JS at runtime instead of compile time

[aharui] fix JS ObjectUtil

[aharui] handle context root for JS at runtime

[aharui] SortOn actually always returns an Array

[aharui] output homedrive/homepath so we can try to see why new CI server can't


--
[...truncated 2.15 MB...]
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var excludedCount:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var valueChanged:Boolean;
 [java] ^
 [java] 
 [java] 4.2191326 seconds
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
 [java] Java Result: 2

compile-js:

main:

basictests-compile-java:
   [delete] Deleting directory 

[mkdir] Created dir: 

[javac] 
:1317:
 warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 12 source files to 

[javac] Note: 

 uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.

basictests:
[mxmlc] MXMLJSC
[mxmlc] 
-sdk-js-lib=
[mxmlc] +env.PLAYERGLOBAL_HOME=C:\adobe\flash
[mxmlc] -compiler.debug=true
[mxmlc] 
+royalelib=
[mxmlc] 
-closure-lib=
[mxmlc] 
-compiler.library-path+=
[mxmlc] 
-compiler.js-external-library-path=
[mxmlc] 
-compiler.js-library-path=
[mxmlc] 
-compiler.js-library-path+=
[mxmlc] --
[mxmlc] 

[mxmlc] Loading configuration: 

[mxmlc] Loading configuration: 

[mxmlc] 
[mxmlc] scanning for overrides: IFlexInfo
[mxmlc] scanning for overrides: ApplicationBase
[mxmlc] scanning for overrides: IEventDispatcher
[mxmlc] scanning for overrides: IInitialViewApplication
[mxmlc] scanning for overrides: IParent
[mxmlc] scanning for overrides: IPopUpHost
[mxmlc] scanning for overrides: IPopUpHostParent
[mxmlc] scanning for overrides: IRenderedObject
[mxmlc] scanning for overrides: IStrand
[mxmlc] scanning for overrides: Application
[mxmlc] scanning for overrides: BasicTestsApp
[mxmlc] scanning for overrides: DontSendScriptComplete
[mxmlc] scanning for overrides: ExitWhenDone
[mxmlc] scanning for overrides: SendFormattedResultsToLog
[mxmlc] scanning for overrides: RoyaleContext
[mxmlc] scanning for overrides: UnitTester
[mxmlc] scanning for overrides: ButtonTestScript
[mxmlc] scanning for overrides: CheckBoxTestScript
[mxmlc] scanning for overrides: 

Re: [Discussion] Where Nightly builds links must be located (we must remove it from download page)

[Harbs]

I think we should add a section to the download page about nightly builds. 
Someone who is looking for the nightly builds might not know where to find it.

Something like:

We do not recommend nightly builds for application developers as they have not 
been properly tested and can have serious bugs. Nightly builds are useful if 
you want to get involved in framework development are are prepared to work with 
bleeding edge code. Source code and nightly build download links can be found 
on our “get involved” page[link].

Harbs

> On Oct 16, 2019, at 10:36 PM, Carlos Rovira  wrote:
> 
> Hi,
> 
> I did it in pre:
> 
> https://royale.codeoscopic.com/download/
> https://royale.codeoscopic.com/get-involved/
> 
> will push it tomorrow if nobody suggest any other change
> 
> thanks
> 
> Carlos
> 
> 
> 
> El mié., 16 oct. 2019 a las 21:27, Alex Harui ()
> escribió:
> 
>> Sounds ok to me.
>> 
>> On 10/16/19, 12:21 PM, "Carlos Rovira"  wrote:
>> 
>>Hi,
>> 
>>thanks all for sharing ideas on how to deal with this issue. For what I
>>read I like some of them.
>> 
>>We already have a "Get Involved" page (most of the time with forget we
>> have
>>menu options in the footer bar and top level menu options are only a
>> subset
>>of what we think "most important" for newcomers).
>>With that page in mind, I think we have solve the "creation of a new
>> page".
>>We can use that.
>> 
>>What I see more easy is then is to move the nightly builds section to
>> that
>>page, so we are done.
>> 
>>Let me know what you think.
>> 
>>Carlos
>> 
>> 
>> 
>>El mié., 16 oct. 2019 a las 18:38, Alex Harui
>> ()
>>escribió:
>> 
>>> The principle behind the policy is not ridiculous.  AIUI, it is
>> important
>>> that the general public only downloads artifacts that the PMC has
>> approved
>>> as an act of the foundation, otherwise the foundation's ability to
>> provide
>>> a legal shield for release managers is weakened.
>>> 
>>> I mostly agree that the way the word "might" in the policy is being
>>> interpreted is "ridiculous".  I really don't think the general
>> public is
>>> being encouraged to download our nightly builds the way the current
>> site
>>> reads.  However, both Justin and I warned about the wording on the
>> download
>>> page [1] before it went live because we've seen other projects get
>>> disrupted by similar nitpicking.  AFAICT, the trend at the ASF is to
>>> continue to be more restrictive about the word "might" and make it
>> harder
>>> to find links to nightly builds on project websites.  Other projects
>> that
>>> used to have links or links "below the fold" no longer do when I went
>>> looking just now.  It won't be worth it to fight it, so let's just
>> plan on
>>> changing.
>>> 
>>> I see other projects with separate pages, but there is always a
>> chance
>>> that someday the word "might" will be restricted even more to include
>>> separate pages.  I'm not making the changes to the site, so I'll
>> leave it
>>> up to those who are doing the work to decide.
>>> 
>>> IMO, with that in mind, when I look at the current site, it is almost
>>> entirely tuned towards our users.  The only place we invite folks to
>>> contribute is way down on the landing page.  And the page that takes
>> you to
>>> is about mailing lists.  I guess you could say that the GitHub link
>> is an
>>> implied indicator that we're an open source project and that you
>> should
>>> contribute.
>>> 
>>> So, here are my ideas.  Feel free to reject them all:
>>> 
>>> 1) Move the nightly build portion of the download page to a wiki
>> page in
>>> GitHub.
>>> 2) Add a "Get Involved" or "Contributing" menu item similar to what
>> Harbs
>>> suggested that goes to a different page like Andrew suggested
>>> 3) Replace the GitHub menu item with the "Get Involved" or
>> "Contributing"
>>> menu item
>>> 4) Add analytics to the nightly build links so we can see how many
>> people
>>> click it
>>> 5) Add a popup to the link to the nightly build so folks must agree
>> to the
>>> disclaimers.
>>> 
>>> I recommend that we just do #1 and move on.  We've got plenty of
>> other
>>> things to work on.
>>> 
>>> My 2 cents,
>>> -Alex
>>> 
>>> [1]
>>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F8564ab5687c631bd4961bf8b987a5e9d30d6673d5050f72b8a9aaa53%40%253Cdev.royale.apache.org%253Edata=02%7C01%7Caharui%40adobe.com%7C3069e9eec31c4fc643fd08d7526e02de%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068504849942445sdata=2LPwIowIFGZmQ%2FzCMYeq8xPcXKJKBQPPkqpX41U3V40%3Dreserved=0
>>> 
>>> On 10/16/19, 7:08 AM, "Josh Tynjala" 
>> wrote:
>>> 
>>>Hopefully a separate public page is allowed. What a ridiculous
>> policy!
>>> 
>>>--
>>>Josh Tynjala
>>>Bowler Hat LLC <
>>> 
>> 

Re: [Discussion] Where Nightly builds links must be located (we must remove it from download page)

[Carlos Rovira]

Hi,

I did it in pre:

https://royale.codeoscopic.com/download/
https://royale.codeoscopic.com/get-involved/

will push it tomorrow if nobody suggest any other change

thanks

Carlos



El mié., 16 oct. 2019 a las 21:27, Alex Harui ()
escribió:

> Sounds ok to me.
>
> On 10/16/19, 12:21 PM, "Carlos Rovira"  wrote:
>
> Hi,
>
> thanks all for sharing ideas on how to deal with this issue. For what I
> read I like some of them.
>
> We already have a "Get Involved" page (most of the time with forget we
> have
> menu options in the footer bar and top level menu options are only a
> subset
> of what we think "most important" for newcomers).
> With that page in mind, I think we have solve the "creation of a new
> page".
> We can use that.
>
> What I see more easy is then is to move the nightly builds section to
> that
> page, so we are done.
>
> Let me know what you think.
>
> Carlos
>
>
>
> El mié., 16 oct. 2019 a las 18:38, Alex Harui
> ()
> escribió:
>
> > The principle behind the policy is not ridiculous.  AIUI, it is
> important
> > that the general public only downloads artifacts that the PMC has
> approved
> > as an act of the foundation, otherwise the foundation's ability to
> provide
> > a legal shield for release managers is weakened.
> >
> > I mostly agree that the way the word "might" in the policy is being
> > interpreted is "ridiculous".  I really don't think the general
> public is
> > being encouraged to download our nightly builds the way the current
> site
> > reads.  However, both Justin and I warned about the wording on the
> download
> > page [1] before it went live because we've seen other projects get
> > disrupted by similar nitpicking.  AFAICT, the trend at the ASF is to
> > continue to be more restrictive about the word "might" and make it
> harder
> > to find links to nightly builds on project websites.  Other projects
> that
> > used to have links or links "below the fold" no longer do when I went
> > looking just now.  It won't be worth it to fight it, so let's just
> plan on
> > changing.
> >
> > I see other projects with separate pages, but there is always a
> chance
> > that someday the word "might" will be restricted even more to include
> > separate pages.  I'm not making the changes to the site, so I'll
> leave it
> > up to those who are doing the work to decide.
> >
> > IMO, with that in mind, when I look at the current site, it is almost
> > entirely tuned towards our users.  The only place we invite folks to
> > contribute is way down on the landing page.  And the page that takes
> you to
> > is about mailing lists.  I guess you could say that the GitHub link
> is an
> > implied indicator that we're an open source project and that you
> should
> > contribute.
> >
> > So, here are my ideas.  Feel free to reject them all:
> >
> > 1) Move the nightly build portion of the download page to a wiki
> page in
> > GitHub.
> > 2) Add a "Get Involved" or "Contributing" menu item similar to what
> Harbs
> > suggested that goes to a different page like Andrew suggested
> > 3) Replace the GitHub menu item with the "Get Involved" or
> "Contributing"
> > menu item
> > 4) Add analytics to the nightly build links so we can see how many
> people
> > click it
> > 5) Add a popup to the link to the nightly build so folks must agree
> to the
> > disclaimers.
> >
> > I recommend that we just do #1 and move on.  We've got plenty of
> other
> > things to work on.
> >
> > My 2 cents,
> > -Alex
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F8564ab5687c631bd4961bf8b987a5e9d30d6673d5050f72b8a9aaa53%40%253Cdev.royale.apache.org%253Edata=02%7C01%7Caharui%40adobe.com%7C3069e9eec31c4fc643fd08d7526e02de%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068504849942445sdata=2LPwIowIFGZmQ%2FzCMYeq8xPcXKJKBQPPkqpX41U3V40%3Dreserved=0
> >
> > On 10/16/19, 7:08 AM, "Josh Tynjala" 
> wrote:
> >
> > Hopefully a separate public page is allowed. What a ridiculous
> policy!
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C3069e9eec31c4fc643fd08d7526e02de%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068504849942445sdata=NquMJTtJe9gbR1%2FnBTzhxcviBJ4YJP1gwF6vSXMBzSE%3Dreserved=0
> > >
> >
> >
> > On Wed, Oct 16, 2019 at 6:30 AM Andrew Wetmore <
> cottag...@gmail.com>
> > wrote:
> >
> > > Can they have their own dedicated page, wreathed around with
> > cautions and
> > > disclaimers to scare away folks who should not be using them?
> > >
> > > On Wed, Oct 16, 2019 at 

Re: [Discussion] Where Nightly builds links must be located (we must remove it from download page)

[Carlos Rovira]

Forgot to share the get involved page for you to check actual state:

https://royale.apache.org/get-involved/

Thanks

El mié., 16 oct. 2019 a las 21:20, Carlos Rovira ()
escribió:

> Hi,
>
> thanks all for sharing ideas on how to deal with this issue. For what I
> read I like some of them.
>
> We already have a "Get Involved" page (most of the time with forget we
> have menu options in the footer bar and top level menu options are only a
> subset of what we think "most important" for newcomers).
> With that page in mind, I think we have solve the "creation of a new
> page". We can use that.
>
> What I see more easy is then is to move the nightly builds section to that
> page, so we are done.
>
> Let me know what you think.
>
> Carlos
>
>
>
> El mié., 16 oct. 2019 a las 18:38, Alex Harui ()
> escribió:
>
>> The principle behind the policy is not ridiculous.  AIUI, it is important
>> that the general public only downloads artifacts that the PMC has approved
>> as an act of the foundation, otherwise the foundation's ability to provide
>> a legal shield for release managers is weakened.
>>
>> I mostly agree that the way the word "might" in the policy is being
>> interpreted is "ridiculous".  I really don't think the general public is
>> being encouraged to download our nightly builds the way the current site
>> reads.  However, both Justin and I warned about the wording on the download
>> page [1] before it went live because we've seen other projects get
>> disrupted by similar nitpicking.  AFAICT, the trend at the ASF is to
>> continue to be more restrictive about the word "might" and make it harder
>> to find links to nightly builds on project websites.  Other projects that
>> used to have links or links "below the fold" no longer do when I went
>> looking just now.  It won't be worth it to fight it, so let's just plan on
>> changing.
>>
>> I see other projects with separate pages, but there is always a chance
>> that someday the word "might" will be restricted even more to include
>> separate pages.  I'm not making the changes to the site, so I'll leave it
>> up to those who are doing the work to decide.
>>
>> IMO, with that in mind, when I look at the current site, it is almost
>> entirely tuned towards our users.  The only place we invite folks to
>> contribute is way down on the landing page.  And the page that takes you to
>> is about mailing lists.  I guess you could say that the GitHub link is an
>> implied indicator that we're an open source project and that you should
>> contribute.
>>
>> So, here are my ideas.  Feel free to reject them all:
>>
>> 1) Move the nightly build portion of the download page to a wiki page in
>> GitHub.
>> 2) Add a "Get Involved" or "Contributing" menu item similar to what Harbs
>> suggested that goes to a different page like Andrew suggested
>> 3) Replace the GitHub menu item with the "Get Involved" or "Contributing"
>> menu item
>> 4) Add analytics to the nightly build links so we can see how many people
>> click it
>> 5) Add a popup to the link to the nightly build so folks must agree to
>> the disclaimers.
>>
>> I recommend that we just do #1 and move on.  We've got plenty of other
>> things to work on.
>>
>> My 2 cents,
>> -Alex
>>
>> [1]
>> https://lists.apache.org/thread.html/8564ab5687c631bd4961bf8b987a5e9d30d6673d5050f72b8a9aaa53@%3Cdev.royale.apache.org%3E
>>
>> On 10/16/19, 7:08 AM, "Josh Tynjala"  wrote:
>>
>> Hopefully a separate public page is allowed. What a ridiculous policy!
>>
>> --
>> Josh Tynjala
>> Bowler Hat LLC <
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7Cc5a1640a5e5c45c5b09708d752424c48%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068317009834112sdata=KCzYsqmguuSBdHlWZEq7V%2FgPmPMOa2pw9LFaxyZBTEo%3Dreserved=0
>> >
>>
>>
>> On Wed, Oct 16, 2019 at 6:30 AM Andrew Wetmore 
>> wrote:
>>
>> > Can they have their own dedicated page, wreathed around with
>> cautions and
>> > disclaimers to scare away folks who should not be using them?
>> >
>> > On Wed, Oct 16, 2019 at 9:42 AM Carlos Rovira <
>> carlosrov...@apache.org>
>> > wrote:
>> >
>> > > Hi,
>> > >
>> > > we get request to remove Nightly builds from download page (see
>> issue in
>> > > GitHub below).
>> > > I open this thread to discuss where is better place for it.
>> > >
>> > > thanks
>> > >
>> > >
>> > > El mié., 16 oct. 2019 a las 14:26, GitBox ()
>> escribió:
>> > >
>> > > > carlosrovira commented on issue #498: Nightly builds must not be
>> > promoted
>> > > > on download pages
>> > > > URL:
>> > > >
>> >
>> 

Re: [Discussion] Where Nightly builds links must be located (we must remove it from download page)

[Alex Harui]

Sounds ok to me.

On 10/16/19, 12:21 PM, "Carlos Rovira"  wrote:

Hi,

thanks all for sharing ideas on how to deal with this issue. For what I
read I like some of them.

We already have a "Get Involved" page (most of the time with forget we have
menu options in the footer bar and top level menu options are only a subset
of what we think "most important" for newcomers).
With that page in mind, I think we have solve the "creation of a new page".
We can use that.

What I see more easy is then is to move the nightly builds section to that
page, so we are done.

Let me know what you think.

Carlos



El mié., 16 oct. 2019 a las 18:38, Alex Harui ()
escribió:

> The principle behind the policy is not ridiculous.  AIUI, it is important
> that the general public only downloads artifacts that the PMC has approved
> as an act of the foundation, otherwise the foundation's ability to provide
> a legal shield for release managers is weakened.
>
> I mostly agree that the way the word "might" in the policy is being
> interpreted is "ridiculous".  I really don't think the general public is
> being encouraged to download our nightly builds the way the current site
> reads.  However, both Justin and I warned about the wording on the 
download
> page [1] before it went live because we've seen other projects get
> disrupted by similar nitpicking.  AFAICT, the trend at the ASF is to
> continue to be more restrictive about the word "might" and make it harder
> to find links to nightly builds on project websites.  Other projects that
> used to have links or links "below the fold" no longer do when I went
> looking just now.  It won't be worth it to fight it, so let's just plan on
> changing.
>
> I see other projects with separate pages, but there is always a chance
> that someday the word "might" will be restricted even more to include
> separate pages.  I'm not making the changes to the site, so I'll leave it
> up to those who are doing the work to decide.
>
> IMO, with that in mind, when I look at the current site, it is almost
> entirely tuned towards our users.  The only place we invite folks to
> contribute is way down on the landing page.  And the page that takes you 
to
> is about mailing lists.  I guess you could say that the GitHub link is an
> implied indicator that we're an open source project and that you should
> contribute.
>
> So, here are my ideas.  Feel free to reject them all:
>
> 1) Move the nightly build portion of the download page to a wiki page in
> GitHub.
> 2) Add a "Get Involved" or "Contributing" menu item similar to what Harbs
> suggested that goes to a different page like Andrew suggested
> 3) Replace the GitHub menu item with the "Get Involved" or "Contributing"
> menu item
> 4) Add analytics to the nightly build links so we can see how many people
> click it
> 5) Add a popup to the link to the nightly build so folks must agree to the
> disclaimers.
>
> I recommend that we just do #1 and move on.  We've got plenty of other
> things to work on.
>
> My 2 cents,
> -Alex
>
> [1]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F8564ab5687c631bd4961bf8b987a5e9d30d6673d5050f72b8a9aaa53%40%253Cdev.royale.apache.org%253Edata=02%7C01%7Caharui%40adobe.com%7C3069e9eec31c4fc643fd08d7526e02de%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068504849942445sdata=2LPwIowIFGZmQ%2FzCMYeq8xPcXKJKBQPPkqpX41U3V40%3Dreserved=0
>
> On 10/16/19, 7:08 AM, "Josh Tynjala"  wrote:
>
> Hopefully a separate public page is allowed. What a ridiculous policy!
>
> --
> Josh Tynjala
> Bowler Hat LLC <
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7C3069e9eec31c4fc643fd08d7526e02de%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068504849942445sdata=NquMJTtJe9gbR1%2FnBTzhxcviBJ4YJP1gwF6vSXMBzSE%3Dreserved=0
> >
>
>
> On Wed, Oct 16, 2019 at 6:30 AM Andrew Wetmore 
> wrote:
>
> > Can they have their own dedicated page, wreathed around with
> cautions and
> > disclaimers to scare away folks who should not be using them?
> >
> > On Wed, Oct 16, 2019 at 9:42 AM Carlos Rovira <
> carlosrov...@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > we get request to remove Nightly builds from download page (see
> issue in
> > > GitHub below).
> > > I open this thread to discuss where is better place for it.
> > >
> > > thanks
> > >
> > >
> > > El mié., 16 oct. 2019 a las 14:26, GitBox ()
> escribió:
> > >
>  

Re: [Discussion] Where Nightly builds links must be located (we must remove it from download page)

[Carlos Rovira]

Hi,

thanks all for sharing ideas on how to deal with this issue. For what I
read I like some of them.

We already have a "Get Involved" page (most of the time with forget we have
menu options in the footer bar and top level menu options are only a subset
of what we think "most important" for newcomers).
With that page in mind, I think we have solve the "creation of a new page".
We can use that.

What I see more easy is then is to move the nightly builds section to that
page, so we are done.

Let me know what you think.

Carlos



El mié., 16 oct. 2019 a las 18:38, Alex Harui ()
escribió:

> The principle behind the policy is not ridiculous.  AIUI, it is important
> that the general public only downloads artifacts that the PMC has approved
> as an act of the foundation, otherwise the foundation's ability to provide
> a legal shield for release managers is weakened.
>
> I mostly agree that the way the word "might" in the policy is being
> interpreted is "ridiculous".  I really don't think the general public is
> being encouraged to download our nightly builds the way the current site
> reads.  However, both Justin and I warned about the wording on the download
> page [1] before it went live because we've seen other projects get
> disrupted by similar nitpicking.  AFAICT, the trend at the ASF is to
> continue to be more restrictive about the word "might" and make it harder
> to find links to nightly builds on project websites.  Other projects that
> used to have links or links "below the fold" no longer do when I went
> looking just now.  It won't be worth it to fight it, so let's just plan on
> changing.
>
> I see other projects with separate pages, but there is always a chance
> that someday the word "might" will be restricted even more to include
> separate pages.  I'm not making the changes to the site, so I'll leave it
> up to those who are doing the work to decide.
>
> IMO, with that in mind, when I look at the current site, it is almost
> entirely tuned towards our users.  The only place we invite folks to
> contribute is way down on the landing page.  And the page that takes you to
> is about mailing lists.  I guess you could say that the GitHub link is an
> implied indicator that we're an open source project and that you should
> contribute.
>
> So, here are my ideas.  Feel free to reject them all:
>
> 1) Move the nightly build portion of the download page to a wiki page in
> GitHub.
> 2) Add a "Get Involved" or "Contributing" menu item similar to what Harbs
> suggested that goes to a different page like Andrew suggested
> 3) Replace the GitHub menu item with the "Get Involved" or "Contributing"
> menu item
> 4) Add analytics to the nightly build links so we can see how many people
> click it
> 5) Add a popup to the link to the nightly build so folks must agree to the
> disclaimers.
>
> I recommend that we just do #1 and move on.  We've got plenty of other
> things to work on.
>
> My 2 cents,
> -Alex
>
> [1]
> https://lists.apache.org/thread.html/8564ab5687c631bd4961bf8b987a5e9d30d6673d5050f72b8a9aaa53@%3Cdev.royale.apache.org%3E
>
> On 10/16/19, 7:08 AM, "Josh Tynjala"  wrote:
>
> Hopefully a separate public page is allowed. What a ridiculous policy!
>
> --
> Josh Tynjala
> Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.devdata=02%7C01%7Caharui%40adobe.com%7Cc5a1640a5e5c45c5b09708d752424c48%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068317009834112sdata=KCzYsqmguuSBdHlWZEq7V%2FgPmPMOa2pw9LFaxyZBTEo%3Dreserved=0
> >
>
>
> On Wed, Oct 16, 2019 at 6:30 AM Andrew Wetmore 
> wrote:
>
> > Can they have their own dedicated page, wreathed around with
> cautions and
> > disclaimers to scare away folks who should not be using them?
> >
> > On Wed, Oct 16, 2019 at 9:42 AM Carlos Rovira <
> carlosrov...@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > we get request to remove Nightly builds from download page (see
> issue in
> > > GitHub below).
> > > I open this thread to discuss where is better place for it.
> > >
> > > thanks
> > >
> > >
> > > El mié., 16 oct. 2019 a las 14:26, GitBox ()
> escribió:
> > >
> > > > carlosrovira commented on issue #498: Nightly builds must not be
> > promoted
> > > > on download pages
> > > > URL:
> > > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F498%23issuecomment-542675010data=02%7C01%7Caharui%40adobe.com%7Cc5a1640a5e5c45c5b09708d752424c48%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068317009834112sdata=%2BGvA%2BRakK5gM5gbVv%2BFVTogTh%2Bb4%2BVNpXOxYYoX%2BFH4%3Dreserved=0
> > > >
> > > >
> > > >I searched to the place in our mailing list that seems to be
> the
> > > source
> > > > of the actual state for nightly on download page:
> > > >
> > > >
> > > >
> > >
> >
> 

Build failed in Jenkins: royale-asjs_MXTests #5

[apacheroyaleci]

See 


Changes:

[piotrzarzycki21] Add Moonshine IDE file to tourdeflex

[piotrzarzycki21] Fix MX NumberFormatter to be usable in MX components

[carlosrovira] remove toString in EventDispatcher since all seems to work ok 
know

[carlosrovira] set EventDispatcher toString again using [object Object] string

[greg.dove] First cut at addressing issue #466 (support for legacy decoding 
only,

[noreply] Added MXAdvancedDataGridItemRenderer in SparkRoyale

[noreply] Added MXAdvancedDataGridItemRenderer in SparkRoyaleClasses

[noreply] Update List.as remove theme from Style BorderVisible


--
[...truncated 935.19 KB...]
 [java] public var lastEvent:Event;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var excludedCount:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var valueChanged:Boolean;
 [java] ^
 [java] 
 [java] 4.3205181 seconds
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
 [java] Java Result: 2

compile-js:

main:

basictests-compile-java:
   [delete] Deleting directory 

[mkdir] Created dir: 

[javac] 
:1317:
 warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 12 source files to 

[javac] Note: 

 uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.

basictests:
[mxmlc] MXMLJSC
[mxmlc] 
-sdk-js-lib=
[mxmlc] +env.PLAYERGLOBAL_HOME=C:\adobe\flash
[mxmlc] -compiler.debug=true
[mxmlc] 
+royalelib=
[mxmlc] 
-closure-lib=
[mxmlc] 
-compiler.library-path+=
[mxmlc] 
-compiler.js-external-library-path=
[mxmlc] 
-compiler.js-library-path=
[mxmlc] 
-compiler.js-library-path+=
[mxmlc] --
[mxmlc] 

[mxmlc] Loading configuration: 

[mxmlc] Loading configuration: 

[mxmlc] 
[mxmlc] scanning for overrides: IFlexInfo
[mxmlc] scanning for overrides: ApplicationBase
[mxmlc] scanning for overrides: IEventDispatcher
[mxmlc] scanning for overrides: IInitialViewApplication
[mxmlc] scanning for overrides: IParent
[mxmlc] scanning for overrides: IPopUpHost
[mxmlc] scanning for overrides: IPopUpHostParent
[mxmlc] scanning for overrides: IRenderedObject
[mxmlc] scanning for overrides: IStrand
[mxmlc] scanning for overrides: Application
[mxmlc] scanning for overrides: BasicTestsApp
[mxmlc] scanning for overrides: DontSendScriptComplete
[mxmlc] scanning for overrides: ExitWhenDone
[mxmlc] scanning for overrides: SendFormattedResultsToLog
[mxmlc] scanning for overrides: RoyaleContext
[mxmlc] scanning for overrides: UnitTester
[mxmlc] 

Build failed in Jenkins: royale-asjs #40

[apacheroyaleci]

See 


Changes:


--
[...truncated 2.04 MB...]
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var excludedCount:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var valueChanged:Boolean;
 [java] ^
 [java] 
 [java] 4.8816456 seconds
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
 [java] Java Result: 2

compile-js:

main:

basictests-compile-java:
   [delete] Deleting directory 

[mkdir] Created dir: 

[javac] 
:1317:
 warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 12 source files to 

[javac] Note: 

 uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.

basictests:
[mxmlc] MXMLJSC
[mxmlc] 
-sdk-js-lib=
[mxmlc] +env.PLAYERGLOBAL_HOME=C:\adobe\flash
[mxmlc] -compiler.debug=true
[mxmlc] 
+royalelib=
[mxmlc] 
-closure-lib=
[mxmlc] 
-compiler.library-path+=
[mxmlc] 
-compiler.js-external-library-path=
[mxmlc] 
-compiler.js-library-path=
[mxmlc] 
-compiler.js-library-path+=
[mxmlc] --
[mxmlc] 

[mxmlc] Loading configuration: 

[mxmlc] Loading configuration: 

[mxmlc] 
[mxmlc] scanning for overrides: IFlexInfo
[mxmlc] scanning for overrides: ApplicationBase
[mxmlc] scanning for overrides: IEventDispatcher
[mxmlc] scanning for overrides: IInitialViewApplication
[mxmlc] scanning for overrides: IParent
[mxmlc] scanning for overrides: IPopUpHost
[mxmlc] scanning for overrides: IPopUpHostParent
[mxmlc] scanning for overrides: IRenderedObject
[mxmlc] scanning for overrides: IStrand
[mxmlc] scanning for overrides: Application
[mxmlc] scanning for overrides: BasicTestsApp
[mxmlc] scanning for overrides: DontSendScriptComplete
[mxmlc] scanning for overrides: ExitWhenDone
[mxmlc] scanning for overrides: SendFormattedResultsToLog
[mxmlc] scanning for overrides: RoyaleContext
[mxmlc] scanning for overrides: UnitTester
[mxmlc] scanning for overrides: ButtonTestScript
[mxmlc] scanning for overrides: CheckBoxTestScript
[mxmlc] scanning for overrides: HTMLElementWrapper
[mxmlc] scanning for overrides: IId
[mxmlc] scanning for overrides: IChild
[mxmlc] scanning for overrides: IUIBase
[mxmlc] scanning for overrides: ILayoutChild
[mxmlc] scanning for overrides: IParentIUIBase
[mxmlc] scanning for overrides: IRoyaleElement
[mxmlc] scanning for overrides: IStrandWithModel
[mxmlc] scanning for overrides: IStrandWithModelView
[mxmlc] scanning for overrides: IStyleableObject
[mxmlc] scanning for overrides: UIBase
[mxmlc] scanning for overrides: IContainer
[mxmlc] scanning for overrides: IContentViewHost
[mxmlc] scanning for overrides: 

Build failed in Jenkins: royale-asjs #39

[apacheroyaleci]

See 


Changes:


--
[...truncated 2.05 MB...]
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var excludedCount:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var valueChanged:Boolean;
 [java] ^
 [java] 
 [java] 4.0606888 seconds
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
 [java] Java Result: 2

compile-js:

main:

basictests-compile-java:
   [delete] Deleting directory 

[mkdir] Created dir: 

[javac] 
:1317:
 warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 12 source files to 

[javac] Note: 

 uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.

basictests:
[mxmlc] MXMLJSC
[mxmlc] 
-sdk-js-lib=
[mxmlc] +env.PLAYERGLOBAL_HOME=C:\adobe\flash
[mxmlc] -compiler.debug=true
[mxmlc] 
+royalelib=
[mxmlc] 
-closure-lib=
[mxmlc] 
-compiler.library-path+=
[mxmlc] 
-compiler.js-external-library-path=
[mxmlc] 
-compiler.js-library-path=
[mxmlc] 
-compiler.js-library-path+=
[mxmlc] --
[mxmlc] 

[mxmlc] Loading configuration: 

[mxmlc] Loading configuration: 

[mxmlc] 
[mxmlc] scanning for overrides: IFlexInfo
[mxmlc] scanning for overrides: ApplicationBase
[mxmlc] scanning for overrides: IEventDispatcher
[mxmlc] scanning for overrides: IInitialViewApplication
[mxmlc] scanning for overrides: IParent
[mxmlc] scanning for overrides: IPopUpHost
[mxmlc] scanning for overrides: IPopUpHostParent
[mxmlc] scanning for overrides: IRenderedObject
[mxmlc] scanning for overrides: IStrand
[mxmlc] scanning for overrides: Application
[mxmlc] scanning for overrides: BasicTestsApp
[mxmlc] scanning for overrides: DontSendScriptComplete
[mxmlc] scanning for overrides: ExitWhenDone
[mxmlc] scanning for overrides: SendFormattedResultsToLog
[mxmlc] scanning for overrides: RoyaleContext
[mxmlc] scanning for overrides: UnitTester
[mxmlc] scanning for overrides: ButtonTestScript
[mxmlc] scanning for overrides: CheckBoxTestScript
[mxmlc] scanning for overrides: HTMLElementWrapper
[mxmlc] scanning for overrides: IId
[mxmlc] scanning for overrides: IChild
[mxmlc] scanning for overrides: IUIBase
[mxmlc] scanning for overrides: ILayoutChild
[mxmlc] scanning for overrides: IParentIUIBase
[mxmlc] scanning for overrides: IRoyaleElement
[mxmlc] scanning for overrides: IStrandWithModel
[mxmlc] scanning for overrides: IStrandWithModelView
[mxmlc] scanning for overrides: IStyleableObject
[mxmlc] scanning for overrides: UIBase
[mxmlc] scanning for overrides: IContainer
[mxmlc] scanning for overrides: IContentViewHost
[mxmlc] scanning for overrides: 

Re: [Discussion] Where Nightly builds links must be located (we must remove it from download page)

[Alex Harui]

The principle behind the policy is not ridiculous.  AIUI, it is important that 
the general public only downloads artifacts that the PMC has approved as an act 
of the foundation, otherwise the foundation's ability to provide a legal shield 
for release managers is weakened.

I mostly agree that the way the word "might" in the policy is being interpreted 
is "ridiculous".  I really don't think the general public is being encouraged 
to download our nightly builds the way the current site reads.  However, both 
Justin and I warned about the wording on the download page [1] before it went 
live because we've seen other projects get disrupted by similar nitpicking.  
AFAICT, the trend at the ASF is to continue to be more restrictive about the 
word "might" and make it harder to find links to nightly builds on project 
websites.  Other projects that used to have links or links "below the fold" no 
longer do when I went looking just now.  It won't be worth it to fight it, so 
let's just plan on changing.

I see other projects with separate pages, but there is always a chance that 
someday the word "might" will be restricted even more to include separate 
pages.  I'm not making the changes to the site, so I'll leave it up to those 
who are doing the work to decide.

IMO, with that in mind, when I look at the current site, it is almost entirely 
tuned towards our users.  The only place we invite folks to contribute is way 
down on the landing page.  And the page that takes you to is about mailing 
lists.  I guess you could say that the GitHub link is an implied indicator that 
we're an open source project and that you should contribute.

So, here are my ideas.  Feel free to reject them all:

1) Move the nightly build portion of the download page to a wiki page in GitHub.
2) Add a "Get Involved" or "Contributing" menu item similar to what Harbs 
suggested that goes to a different page like Andrew suggested
3) Replace the GitHub menu item with the "Get Involved" or "Contributing" menu 
item
4) Add analytics to the nightly build links so we can see how many people click 
it
5) Add a popup to the link to the nightly build so folks must agree to the 
disclaimers.

I recommend that we just do #1 and move on.  We've got plenty of other things 
to work on.

My 2 cents,
-Alex

[1] 
https://lists.apache.org/thread.html/8564ab5687c631bd4961bf8b987a5e9d30d6673d5050f72b8a9aaa53@%3Cdev.royale.apache.org%3E

On 10/16/19, 7:08 AM, "Josh Tynjala"  wrote:

Hopefully a separate public page is allowed. What a ridiculous policy!

--
Josh Tynjala
Bowler Hat LLC 



On Wed, Oct 16, 2019 at 6:30 AM Andrew Wetmore  wrote:

> Can they have their own dedicated page, wreathed around with cautions and
> disclaimers to scare away folks who should not be using them?
>
> On Wed, Oct 16, 2019 at 9:42 AM Carlos Rovira 
> wrote:
>
> > Hi,
> >
> > we get request to remove Nightly builds from download page (see issue in
> > GitHub below).
> > I open this thread to discuss where is better place for it.
> >
> > thanks
> >
> >
> > El mié., 16 oct. 2019 a las 14:26, GitBox () escribió:
> >
> > > carlosrovira commented on issue #498: Nightly builds must not be
> promoted
> > > on download pages
> > > URL:
> > >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F498%23issuecomment-542675010data=02%7C01%7Caharui%40adobe.com%7Cc5a1640a5e5c45c5b09708d752424c48%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068317009834112sdata=%2BGvA%2BRakK5gM5gbVv%2BFVTogTh%2Bb4%2BVNpXOxYYoX%2BFH4%3Dreserved=0
> > >
> > >
> > >I searched to the place in our mailing list that seems to be the
> > source
> > > of the actual state for nightly on download page:
> > >
> > >
> > >
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2FNeed-help-with-CSS-class-selector-font-family-is-always-Arial-tp1418p1485.htmldata=02%7C01%7Caharui%40adobe.com%7Cc5a1640a5e5c45c5b09708d752424c48%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637068317009834112sdata=ZLZ4e9gIq62avxUPbA%2F9zVKTY1%2FjUPVGXH%2FNhF0pBMM%3Dreserved=0
> > >
> > >I think If we want to change it we need to discuss in list how we
> want
> > > it now
> > >
> > >
> > >
> > > 
> > > 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 

Re: [Discussion] Where Nightly builds links must be located (we must remove it from download page)

[Josh Tynjala]

Hopefully a separate public page is allowed. What a ridiculous policy!

--
Josh Tynjala
Bowler Hat LLC 


On Wed, Oct 16, 2019 at 6:30 AM Andrew Wetmore  wrote:

> Can they have their own dedicated page, wreathed around with cautions and
> disclaimers to scare away folks who should not be using them?
>
> On Wed, Oct 16, 2019 at 9:42 AM Carlos Rovira 
> wrote:
>
> > Hi,
> >
> > we get request to remove Nightly builds from download page (see issue in
> > GitHub below).
> > I open this thread to discuss where is better place for it.
> >
> > thanks
> >
> >
> > El mié., 16 oct. 2019 a las 14:26, GitBox () escribió:
> >
> > > carlosrovira commented on issue #498: Nightly builds must not be
> promoted
> > > on download pages
> > > URL:
> > >
> https://github.com/apache/royale-asjs/issues/498#issuecomment-542675010
> > >
> > >
> > >I searched to the place in our mailing list that seems to be the
> > source
> > > of the actual state for nightly on download page:
> > >
> > >
> > >
> >
> http://apache-royale-development.20373.n8.nabble.com/Need-help-with-CSS-class-selector-font-family-is-always-Arial-tp1418p1485.html
> > >
> > >I think If we want to change it we need to discuss in list how we
> want
> > > it now
> > >
> > >
> > >
> > > 
> > > 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
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>

Re: [Discussion] Where Nightly builds links must be located (we must remove it from download page)

[Andrew Wetmore]

Can they have their own dedicated page, wreathed around with cautions and
disclaimers to scare away folks who should not be using them?

On Wed, Oct 16, 2019 at 9:42 AM Carlos Rovira 
wrote:

> Hi,
>
> we get request to remove Nightly builds from download page (see issue in
> GitHub below).
> I open this thread to discuss where is better place for it.
>
> thanks
>
>
> El mié., 16 oct. 2019 a las 14:26, GitBox () escribió:
>
> > carlosrovira commented on issue #498: Nightly builds must not be promoted
> > on download pages
> > URL:
> > https://github.com/apache/royale-asjs/issues/498#issuecomment-542675010
> >
> >
> >I searched to the place in our mailing list that seems to be the
> source
> > of the actual state for nightly on download page:
> >
> >
> >
> http://apache-royale-development.20373.n8.nabble.com/Need-help-with-CSS-class-selector-font-family-is-always-Arial-tp1418p1485.html
> >
> >I think If we want to change it we need to discuss in list how we want
> > it now
> >
> >
> >
> > 
> > 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
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Build failed in Jenkins: royale-asjs #38

[apacheroyaleci]

See 


Changes:


--
[...truncated 2.05 MB...]
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var excludedCount:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var valueChanged:Boolean;
 [java] ^
 [java] 
 [java] 4.1594307 seconds
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
 [java] Java Result: 2

compile-js:

main:

basictests-compile-java:
   [delete] Deleting directory 

[mkdir] Created dir: 

[javac] 
:1317:
 warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 12 source files to 

[javac] Note: 

 uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.

basictests:
[mxmlc] MXMLJSC
[mxmlc] 
-sdk-js-lib=
[mxmlc] +env.PLAYERGLOBAL_HOME=C:\adobe\flash
[mxmlc] -compiler.debug=true
[mxmlc] 
+royalelib=
[mxmlc] 
-closure-lib=
[mxmlc] 
-compiler.library-path+=
[mxmlc] 
-compiler.js-external-library-path=
[mxmlc] 
-compiler.js-library-path=
[mxmlc] 
-compiler.js-library-path+=
[mxmlc] --
[mxmlc] 

[mxmlc] Loading configuration: 

[mxmlc] Loading configuration: 

[mxmlc] 
[mxmlc] scanning for overrides: IFlexInfo
[mxmlc] scanning for overrides: ApplicationBase
[mxmlc] scanning for overrides: IEventDispatcher
[mxmlc] scanning for overrides: IInitialViewApplication
[mxmlc] scanning for overrides: IParent
[mxmlc] scanning for overrides: IPopUpHost
[mxmlc] scanning for overrides: IPopUpHostParent
[mxmlc] scanning for overrides: IRenderedObject
[mxmlc] scanning for overrides: IStrand
[mxmlc] scanning for overrides: Application
[mxmlc] scanning for overrides: BasicTestsApp
[mxmlc] scanning for overrides: DontSendScriptComplete
[mxmlc] scanning for overrides: ExitWhenDone
[mxmlc] scanning for overrides: SendFormattedResultsToLog
[mxmlc] scanning for overrides: RoyaleContext
[mxmlc] scanning for overrides: UnitTester
[mxmlc] scanning for overrides: ButtonTestScript
[mxmlc] scanning for overrides: CheckBoxTestScript
[mxmlc] scanning for overrides: HTMLElementWrapper
[mxmlc] scanning for overrides: IId
[mxmlc] scanning for overrides: IChild
[mxmlc] scanning for overrides: IUIBase
[mxmlc] scanning for overrides: ILayoutChild
[mxmlc] scanning for overrides: IParentIUIBase
[mxmlc] scanning for overrides: IRoyaleElement
[mxmlc] scanning for overrides: IStrandWithModel
[mxmlc] scanning for overrides: IStrandWithModelView
[mxmlc] scanning for overrides: IStyleableObject
[mxmlc] scanning for overrides: UIBase
[mxmlc] scanning for overrides: IContainer
[mxmlc] scanning for overrides: IContentViewHost
[mxmlc] scanning for overrides: 

[Discussion] Where Nightly builds links must be located (we must remove it from download page)

[Carlos Rovira]

Hi,

we get request to remove Nightly builds from download page (see issue in
GitHub below).
I open this thread to discuss where is better place for it.

thanks


El mié., 16 oct. 2019 a las 14:26, GitBox () escribió:

> carlosrovira commented on issue #498: Nightly builds must not be promoted
> on download pages
> URL:
> https://github.com/apache/royale-asjs/issues/498#issuecomment-542675010
>
>
>I searched to the place in our mailing list that seems to be the source
> of the actual state for nightly on download page:
>
>
> http://apache-royale-development.20373.n8.nabble.com/Need-help-with-CSS-class-selector-font-family-is-always-Arial-tp1418p1485.html
>
>I think If we want to change it we need to discuss in list how we want
> it now
>
>
>
> 
> 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
>


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

Build failed in Jenkins: royale-asjs #37

[apacheroyaleci]

See 


Changes:

[noreply] Added MXAdvancedDataGridItemRenderer in SparkRoyale

[noreply] Added MXAdvancedDataGridItemRenderer in SparkRoyaleClasses

[noreply] Update List.as remove theme from Style BorderVisible


--
[...truncated 2.04 MB...]
 [java] public var lastEvent:Event;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var excludedCount:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public var valueChanged:Boolean;
 [java] ^
 [java] 
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
 [java] Java Result: 2

compile-js:

main:

basictests-compile-java:
   [delete] Deleting directory 

[mkdir] Created dir: 

[javac] 
:1317:
 warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 12 source files to 

[javac] Note: 

 uses or overrides a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.

basictests:
[mxmlc] MXMLJSC
[mxmlc] 
-sdk-js-lib=
[mxmlc] +env.PLAYERGLOBAL_HOME=C:\adobe\flash
[mxmlc] -compiler.debug=true
[mxmlc] 
+royalelib=
[mxmlc] 
-closure-lib=
[mxmlc] 
-compiler.library-path+=
[mxmlc] 
-compiler.js-external-library-path=
[mxmlc] 
-compiler.js-library-path=
[mxmlc] 
-compiler.js-library-path+=
[mxmlc] --
[mxmlc] 

[mxmlc] Loading configuration: 

[mxmlc] Loading configuration: 

[mxmlc] 
[mxmlc] scanning for overrides: IFlexInfo
[mxmlc] scanning for overrides: ApplicationBase
[mxmlc] scanning for overrides: IEventDispatcher
[mxmlc] scanning for overrides: IInitialViewApplication
[mxmlc] scanning for overrides: IParent
[mxmlc] scanning for overrides: IPopUpHost
[mxmlc] scanning for overrides: IPopUpHostParent
[mxmlc] scanning for overrides: IRenderedObject
[mxmlc] scanning for overrides: IStrand
[mxmlc] scanning for overrides: Application
[mxmlc] scanning for overrides: BasicTestsApp
[mxmlc] scanning for overrides: DontSendScriptComplete
[mxmlc] scanning for overrides: ExitWhenDone
[mxmlc] scanning for overrides: SendFormattedResultsToLog
[mxmlc] scanning for overrides: RoyaleContext
[mxmlc] scanning for overrides: UnitTester
[mxmlc] scanning for overrides: ButtonTestScript
[mxmlc] scanning for overrides: CheckBoxTestScript
[mxmlc] scanning for overrides: HTMLElementWrapper
[mxmlc] scanning for overrides: IId
[mxmlc] scanning for overrides: IChild
[mxmlc] scanning for overrides: IUIBase
[mxmlc] scanning for overrides: ILayoutChild
[mxmlc] scanning for overrides: IParentIUIBase
[mxmlc] scanning for overrides: IRoyaleElement
[mxmlc] scanning for overrides: IStrandWithModel
[mxmlc] scanning for overrides: IStrandWithModelView
[mxmlc]