goals.xml and properties.xml are already generated but the problem is that there's no synchronization. It's only usefull for the first generation.
A dynamic goals.xml (and properties.xml if possible) should be a good idea. Arnaud > -----Message d'origine----- > De : Miguel Griffa [mailto:[EMAIL PROTECTED] > Envoy� : mercredi 23 juin 2004 14:34 > � : Maven Developers List > Objet : Re: maven-plugin-plugin generate docs improvement > (MPPLUGIN-17) > > > Hi, > I totally agree with this. Generating the goals.xml > shuold be quite > easy (a simple matter of xsl), the properties.xml may be > another story... > Having goals.xml generated would contribute to a more uniform > documentation > > > M. Sean Gilligan wrote: > > >Hello Dion, et. al., > > > >I thought I'd move some of this > >(http://jira.codehaus.org/browse/MPPLUGIN-17) discussion off of JIRA > >and on to the dev list. (I'm not sure what the correct > protocol is, so > >please forgive me if I'm breaking it. I also apologize if a JIRA > >priority of "major" seems high, I neglected to change the default.) > > > >What I'm proposing is that xdocs/goals.xml and xdocs/properties.xml > >always be auto-generated and that plugin.jelly and > plugin.properties be > >extended to allow complete documentation to be in the same > file as the > >"source code". This should make plugin developer's lives easier and > >result in more detailed and accurate plugin documentation. > (For more > >details see: http://jira.codehaus.org/browse/MPPLUGIN-17) > > > >I'm writing my first plugin and initially expected things to > work as I > >have proposed in MPPLUGIN-17. I am willing to do a certain > amount of > >leg-work to help make this happen. (Post 1.0, obviously) I > don't know > >Maven well enough to do it myself, but am willing to work > with Dion (or > >other) to design, develop, test, and debug a solution. > > > >Regards, > > > >Sean > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
