> 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.xxxx.xxxx=yyyyyyyy > > Should synchronization be used? > Why not keep it a one way process? > > I think it doesn't make sense to add properties/goals in docs > which do > not exist in plugin.jelly, or does it? It can be a one-way process. We must add a report to automatically generate these files before the site. 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 Arnaud. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
