btw, for a change like this I think you should pass maven to ensure nothing broken:
[*INFO*] Apache Royale: Framework: Libs: GoogleMaps ......... *SUCCESS* [ 1.042 s] [*INFO*] Apache Royale: Framework: Libs: HTML ............... *FAILURE* [ 0.321 s] [*INFO*] Apache Royale: Framework: Libs: HTML5 .............. *SKIPPED* [*INFO*] Apache Royale: Framework: Libs: JQuery ............. *SKIPPED* [*INFO*] Apache Royale: Framework: Libs: Language ........... *SKIPPED* [*INFO*] Apache Royale: Framework: Libs: Material Design Lite *SKIPPED* [*INFO*] Apache Royale: Framework: Libs: Mobile ............. *SKIPPED* [*INFO*] Apache Royale: Framework: Libs: Reflection ......... *SKIPPED* [*INFO*] Apache Royale: Framework: Libs: Network ............ *SKIPPED* [*INFO*] Apache Royale: Framework: Libs: Storage ............ *SKIPPED* [*INFO*] Apache Royale: Framework: Libs: XML ................ *SKIPPED* [*INFO*] Apache Royale: Framework: Libs: Text ............... *SKIPPED* [*INFO*] Apache Royale: Framework: Libs: TLF ................ *SKIPPED* [*INFO*] Apache Royale: Framework: Libs: RoyaleSite ......... *SKIPPED* [*INFO*] Apache Royale: Framework: Libs: MXRoyale ........... *SKIPPED* [*INFO*] Apache Royale: Framework: Libs: Jewel 0.9.4-SNAPSHOT *SKIPPED* GroupBase is not a solution since doesn't have the nesting functionality. I think we have only one way: Pass Group to Core, since is really Core 2018-05-09 12:47 GMT+02:00 Carlos Rovira <carlosrov...@apache.org>: > Hi > > the problem was that HTML library was baking Basic library only due to > "NodeElementBase extends Group" > was Harbs how told me that NodeElementBase was not need to extend Group. > Then I changed it and looking into examples for this change didn't see > problems. > > Is normal something arise now, so NodeElementBase must extends some kind > of Group. Did you try to simply try to extend GroupBase that is in core? > > @Harbs, about to revert I think you refer to this concrete one? right? > > We should continue looking if more problems arise, and try to go fixing > them. Sometimes the solution I did will be not right, in other cases, can > be a matter of adapt you applications. Have in mind, that Apache Royale, > can be modeled against a single Application (yours) and must have the > general purpose in mind over the personal interest. So for me it's a matter > of balance. The key point to pursue finaly is that we need separation of > Basic ui set from the rest of Royale to avoid to make people be charged > with things that are not really Core. > > Thanks > > > > > > 2018-05-09 11:29 GMT+02:00 yishayw <yishayj...@hotmail.com>: > >> I changed it back so NodeElementBase extends Group. Let's continue this >> discussion, but we need our app to work... >> >> >> >> -- >> Sent from: http://apache-royale-development.20373.n8.nabble.com/ >> > > > > -- > Carlos Rovira > http://about.me/carlosrovira > > -- Carlos Rovira http://about.me/carlosrovira
