Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

This may all be moot if we decide to postpone any changes until m2 as suggested by Brett, but I'll update the proposal with Dion's comments (and my responses) just in case people want to go ahead with it: > > 1) Ensure backward-compatibility. One solution is to create a property setting > >

Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

On Wed, 23 Jun 2004 11:02:05 -0700, M. Sean Gilligan <[EMAIL PROTECTED]> wrote: > > Hi Everyone, > > Thanks for the positive feedback and brainstorming. I made some specific > suggestions on JIRA, I'll repeat them here and incorporate/respond-to some > suggestions made on the list. > > 1) E

Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

All, These are all good ideas, however it is probably not worth the effort at this point. m2's plugins are self documenting in the fashion you are talking about, and there is a clear direction to start pushing them in to use in maven 1 in the near future. Hope this helps! Cheers, Brett Quoting

Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

I'd really like to contribute to this task, but I'm not aware of the protocol (for non commiters) to follow since submiting patches to the plugin post 1.0 is not an options, as I guess, and there's no 1.1 brach, or is it? M. Sean Gilligan wrote: Hi Everyone, Thanks for the positive feedback and

RE: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

Hi Everyone, Thanks for the positive feedback and brainstorming. I made some specific suggestions on JIRA, I'll repeat them here and incorporate/respond-to some suggestions made on the list. 1) Ensure backward-compatibility. One solution is to create a property setting to cause properties.

Re: RE : RE : maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

Heritier Arnaud wrote: The problem is that in some plugins, the documentation of goals is very more detailled in the doc than in the plugin.jelly. In the goal's description you can't use HTML tags. For example : http://maven.apache.org/reference/plugins/dist/goals.html HTML in goal documentation

RE : RE : maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

> the properties.xml could be generated with a more advanced > parsing and > maybe assuming all properties begin with the plugin name > followed by a '.' The problem will be to standardize the properties documentation and to parse the file. # MY DOC xxx..= > > Should synchro

Re: RE : maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

elly, or does it? 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 b

RE : maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

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 >

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