initial draft implementation is ready for feedback, description is in https://issues.apache.org/jira/browse/CB-4195 (just plugin schema now, not config schema yet).
On Jul 10, 2013, at 12:15 PM, Marcel Kinard <[email protected]> wrote: > On Jul 9, 2013, at 9:38 PM, Michal Mocny <[email protected]> wrote: > >> Seriously though, if the schema is changing isn't that all the more reason >> to support validation so devs can get early confirmation? > > That is exactly my thought. Updating the xsd is relatively easy, and it's > just one file per schema. Handling a new attribute or element is just a few > lines of work. > > On Jul 9, 2013, at 5:56 PM, Brian LeRoux <[email protected]> wrote: > >> …there is pretty strong argument brewing to move to JSON. > > If that is going to happen, it would be post 3.0, because only 9 days are > remaining, right? > > I can see why JSON would be attractive, but that would also be forcing plugin > authors to re-do their config file that they recently created for 3.0. > Potentially we could use XSL to transform config.xml to config.json > automatically for a bridge period. > > I'll start playing with an XSD and put it out for review. >
