there are interesting discussion happening on github, but they are not routed to any mailing-list, so they stay completely personal: this is not good for community, IMHO
is there a way to have such discussions sent to dev@? Regards, Hervé ---------- Message transmit ---------- Sujet : Re: [maven] removed XSD generation since it is not published (19247f3) Date : dimanche 25 mai 2014, 02:29:12 De : Dave Moten <notificati...@github.com> À : apache/maven <ma...@noreply.github.com> CC : Hervé Boutemy <herve.bout...@free.fr> I was interested in writing tooling around composing plugins maximising type safety for example but was disappointed that the definition of a plugin's configuration was not something I could reverse engineer satisfactorily from the plugin.xml and in the process discovered that the plugin.XML didn't have an xsd making more guesswork out of the process. I used xpath to get stuff out of it in the end but I stopped work when I realised that my only hope was parsing plugins' source code. I'm a big fan of XML always having an xsd but I probably won't be able to check out modello and get an xsd happening in the near future and I'm assuming for my interests that it won't help much either. I wonder if real type information for configuration will turn up in plugin.xml sometime? Thanks for chasing it. D On 25 May 2014 18:14, "Hervé Boutemy" <notificati...@github.com> wrote: > on a pure principle, I know it looks awkward > on a practical one: > 1. did you ever try to write a plugin descriptor by hand? or do you always > let plugin-tools generate the descriptor (like the vast majority of plugin > developers)? > 2. are you able to give us a xsd description for the configuration element > content? and that fits into Modello descriptor, since Modello generates the > xsd from .mdo? > > I'm not a big xsd expert: any help appreciated to fix the plugin.mdo I > wrote to at least document the descriptor "from a human point of view" (ie > not seeing in general that I had to cheat with configuration element) > > — > Reply to this email directly or view it on GitHub<https://github.com/apache/maven/commit/19247f363bee07d1afc6f8902f4083fd890fc47a#commitcomment-6439921> > . > --- Reply to this email directly or view it on GitHub: https://github.com/apache/maven/commit/19247f363bee07d1afc6f8902f4083fd890fc47a#commitcomment-6440111 ----------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
