Build failed in Jenkins: Royale_ASDoc_Example #2371

[Apache Royale CI Server]

See 


--
[...truncated 26.09 KB...]
[mxmlc] scanning for overrides: IListView
[mxmlc] scanning for overrides: DataContainerView
[mxmlc] scanning for overrides: IDataProviderItemRendererMapper
[mxmlc] scanning for overrides: DataItemRendererFactoryForArrayData
[mxmlc] scanning for overrides: IScrollBarView
[mxmlc] scanning for overrides: Strand
[mxmlc] scanning for overrides: ScrollBarView
[mxmlc] scanning for overrides: HScrollBarView
[mxmlc] scanning for overrides: ListView
[mxmlc] scanning for overrides: ITextFieldView
[mxmlc] scanning for overrides: TextFieldViewBase
[mxmlc] scanning for overrides: MultilineTextFieldView
[mxmlc] scanning for overrides: IGraphicsDrawing
[mxmlc] scanning for overrides: IBorderBead
[mxmlc] scanning for overrides: SingleLineBorderBead
[mxmlc] scanning for overrides: IBackgroundBead
[mxmlc] scanning for overrides: SolidBackgroundBead
[mxmlc] scanning for overrides: IMeasurementBead
[mxmlc] scanning for overrides: TextFieldLabelMeasurementBead
[mxmlc] scanning for overrides: TextFieldView
[mxmlc] scanning for overrides: TextInputView
[mxmlc] scanning for overrides: TextInputWithBorderView
[mxmlc] scanning for overrides: VScrollBarView
[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: ILayoutView
[mxmlc] scanning for overrides: ContainerContentArea
[mxmlc] scanning for overrides: DataGroup
[mxmlc] scanning for overrides: IViewport
[mxmlc] scanning for overrides: Viewport
[mxmlc] scanning for overrides: IScrollingViewport
[mxmlc] scanning for overrides: ScrollingViewport
[mxmlc] scanning for overrides: IItemRenderer
[mxmlc] scanning for overrides: ISelectableItemRenderer
[mxmlc] scanning for overrides: ITextItemRenderer
[mxmlc] scanning for overrides: UIItemRendererBase
[mxmlc] scanning for overrides: DataItemRenderer
[mxmlc] scanning for overrides: StringItemRenderer
[mxmlc] scanning for overrides: IStatesObject
[mxmlc] scanning for overrides: IApplicationView
[mxmlc] scanning for overrides: IValuesImpl
[mxmlc] scanning for overrides: IDocument
[mxmlc] scanning for overrides: IItemRendererClassFactory
[mxmlc] scanning for overrides: ItemRendererClassFactory
[mxmlc] scanning for overrides: IBorderPaddingMarginValuesImpl
[mxmlc] scanning for overrides: ICSSImpl
[mxmlc] scanning for overrides: SimpleCSSValuesImpl
[mxmlc] scanning for overrides: CSSClass
[mxmlc] scanning for overrides: CSSFactory
[mxmlc] scanning for overrides: CSSDataType
[mxmlc] scanning for overrides: IStatesImpl
[mxmlc] scanning for overrides: SimpleStatesImpl
[mxmlc] scanning for overrides: ValuesManager
[mxmlc] scanning for overrides: MouseEventConverter
[mxmlc] scanning for overrides: IRoyaleEvent
[mxmlc] scanning for overrides: Event
[mxmlc] scanning for overrides: ValueChangeEvent
[mxmlc] scanning for overrides: MXMLDataInterpreter
[mxmlc] scanning for overrides: ViewSourceContextMenuOption
[mxmlc] scanning for overrides: HTTPServiceBase
[mxmlc] scanning for overrides: HTTPService
[mxmlc] scanning for overrides: JSONReviver
[mxmlc] scanning for overrides: ASDocController
[mxmlc] scanning for overrides: IContainer
[mxmlc] scanning for overrides: IContentViewHost
[mxmlc] scanning for overrides: ILayoutParent
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: ViewBase
[mxmlc] scanning for overrides: IMXMLDocument
[mxmlc] scanning for overrides: View
[mxmlc] scanning for overrides: DocPage
[mxmlc] scanning for overrides: HashAnchorStringItemRenderer
[mxmlc] scanning for overrides: 
AlternatingBackgroundColorHashAnchorStringItemRenderer
[mxmlc] scanning for overrides: AltBGRenderer
[mxmlc] scanning for overrides: ASDocMainView
[mxmlc] scanning for overrides: MXMLItemRenderer
[mxmlc] scanning for overrides: EventSummaryRenderer
[mxmlc] scanning for overrides: ASDocClassEvents
[mxmlc] scanning for overrides: ASDocClassFunction
[mxmlc] scanning for overrides: EventDetailRenderer
[mxmlc] scanning for overrides: MethodDetailRenderer
[mxmlc] scanning for overrides: ASDocClassData
[mxmlc] scanning for overrides: 

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

[Apache Royale CI Server]

See 

Re: Sub-Menu in royale-docs: "Fundamental Concepts", "Core Concepts" or "Technology features"

[Chris Velevitch]

As a Flex developer exploring Royale, I've come across the terms "beads",
"strands" and "pay as you go" (PAYG), but I can't find any details,
documentation or tutorials on them. How do these map into existing Flex
concepts? As for PAYG, as far as I can tell, this is just another name for
the concept of "tree-shaking" [1] that other javascript frameworks have/use.

So, where can I find more information on these?

[1] https://en.wikipedia.org/wiki/Tree_shaking

On Thu, 22 Aug 2019 at 18:35, Carlos Rovira  wrote:

> Hi,
>
> while adding yesterday all "Where to go from here" sections in all blog
> examples, I found that Royale docs need a sub menu in the sidebar with some
> royale important concepts.
>
> So after "*Get Started*" and before "*Component Sets*" I think we need
> something like a "*Fundamental Concepts*" (maybe this title is not the best
> and others can get other that match better, I'll try to think in other that
> fits better too. I try to refer to "Core Concepts" or a "Technology
> features" here).
>
> Is what a user should need to know just after finish "Get Started" guide
> and a hello world...know the tools avaialble in the royale arsenal, know
> that they have available things like binding, states, modules...
>
> In this submenu we need to cover the things that are still not covered in
> the docs and others that are covered but seems a bit lost in places
> difficult to find or that are not the best way where a user should find it,
> or try to search for it.
>
> Options will be all core concepts:
>
>  - *Fundamental Concepts *
>   - *View States* (just created an empty page yesterday)
>   - *Data Binding* (page exists too but is empty now and needs to be
> relocated)
>   - *Modules* (This already exist, I think just need to be relocated)
>   - *Externs* (this one was created yesterday by Andrew, again the
> problem is still not referenced in menu, and is under "user-interface", but
> is more a "core concept" or a "technology feature").
>   - *Loading Data* or *Data Access*: This should have a sub menu with
> the main ways to access data :
>- *HTTPService*
>- *JSON*
>- *AMF*
>- ...
>   - *Metadata*
>   - *Styles and CSS*
>   - ...  I'm sure there are more to bring here...
>
> For me this is the main missing piece we need to address, and of course
> completing not only that menu but many other pages still to fill.
>
> Just one thing to end: In each page after main title the template expect
> the next line to be a short subtitle. For example, in the new "Externs"
> page y added a new line after title "Use external javascript libraries in
> ActiopnScript" So that line is shown in blue and with a bit more size to
> match the web style. That line should help a user to quickly understand
> what's that page about, since just "Externs" probably will not be of much
> help for a beginner.
>
> many pages are still without subtitle, but as we go over all docs, we
> should add this lines to help users reaching that pages.
>
> Thanks
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 


Chris
--
Chris Velevitch
m: 0415 469 095

Release Step 007 Succeeded

[Apache Royale CI Server]

>From the royale-typedefs repo:
1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.6
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign 
-Drelease.version=0.9.6
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_007_Upload 
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging.  Do not "Close" 
the staging repository until the other repos have been added.

Release Step 006 Succeeded

[Apache Royale CI Server]

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

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

Release Step 005a Succeeded

[Apache Royale CI Server]

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

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

Release Step 005 Succeeded

[Apache Royale CI Server]

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

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

Release Step 004 Succeeded

[Apache Royale CI Server]

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

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

Release Step 003 Succeeded

[Apache Royale CI Server]

>From the royale-compiler repo:
1. If you are releasing the utils jars (compiler-jburg-types and 
compiler-build-tools) - you have set in previous step for mentioned projects 
version ex. 1.1.0 not snapshot, Run:
  ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
Otherwise, Run:
 ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign 
-Drelease.version=0.9.6
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload 
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging.  Do not "Close" 
the staging repository until the other repos have been added.

Royale_Release_Step_003 - Build # 40 - Failure!

[Apache Royale CI Server]

Royale_Release_Step_003 - Build # 40 - Failure:

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

Release Step 002a Succeeded

[Apache Royale CI Server]

Continue on to Release Step 003

Royale_Release_Step_002a_If_Utils - Build # 28 - Failure!

[Apache Royale CI Server]

Royale_Release_Step_002a_If_Utils - Build # 28 - Failure:

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

Release Step 002 Succeeded

[Apache Royale CI Server]

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

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

Release Step 001a Succeeded

[Apache Royale CI Server]

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

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

Release Step 001 Succeeded

[Apache Royale CI Server]

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

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

Trying abstract classes in Jewel

[Carlos Rovira]

Hi Josh,

after cleaning Jewel TextInput classes, I tried to change TextInputBase
from public to abstract class.

The reason is that while Simple** classes (like Jewel SimpleButton or
SimpleRemoteObject), are a reduced case of a class named without "Simple"
(in the example "Button", and most users would want to use just "Button",
so this name strategy seems very good to me, exposing the most used class
with the expected name and a simple one with that prefix).

Others like TextInputBase (with suffix **Base) are just a base class for
other classes like TextInput and TextArea and should not be used as a
component,
so in this way of thinking seems reasonable to mark it as "abstract".

When doing that little change (switch public for abstract at level class in
TextInputBase), when compile Jewel SWC, a bunch of errors appear,
so is not clear to me if I'm doing something wrong, or I'm missing
something.

Hope you can give some light on this.

Thanks.

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