Would be interested in a pointer to that discussion ... cause the only benefit of leaving them away is that it makes less fuss in writing the files, but on the downside there is a large amount of downsides: - No tool support (IntelliJ can't help you detect things that are wrong) - Makes writing parsers harder (I'm currently starting to work on automated config generation ... that's difficult if there's no schema) - I don't know which options there are ... all I have are examples that I have to extract what they mean.
Chris ________________________________________ Von: Harbs <harbs.li...@gmail.com> Gesendet: Montag, 18. April 2016 15:07 An: dev@flex.apache.org Betreff: Re: [FlexJS] No Namespaces? There was discussion on the topic in the past. IIRC, it was a conscious decision to not use namespaces. I don’t remember the reason. Harbs On Apr 18, 2016, at 3:47 PM, Christofer Dutz <christofer.d...@c-ware.de> wrote: > Hi, > > > I'm currently working on migrating the build of the framework projects in the > flex-asjs project to build with the flexjs-maven-plugin. I noticed one thing, > that most of our config files don't have a single namespace declaration. Is > this just because of lazyness, or don't we have schemas for them? I'm > currently talking about the compile-config xml files and the manifest files > ... > > > Chris
