I like the idea.. Would the next logical step be to verify as well that anything in plugin.properties was listed in the properties.xml file? It seems that pretty much anything in plugin.properties should be documented. You could also apply the same logic to goals as well.
Eric > -----Original Message----- > From: Carlos Sanchez [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 29, 2004 12:25 PM > To: 'Maven Developers List' > Subject: Plugin properties suggestion > > > Hi, > > This is a suggestion of how to create and document plugin > properties easier. > > - Create an xml file called properties.xml with the following DTD. > In the plugin project: > - Process it to generate the properties.xml xdoc using > <report>maven-plugin-plugin</report> > - Process it to generate the plugin.properties file, maybe in the future > there will be support for reading properties directly from it. > > Here is the DTD > > <?xml version="1.0" encoding="ISO-8859-1"?> > <!ELEMENT properties ( > property*)> > > <!ELEMENT property (#PCDATA)> > > <!ATTLIST property > name CDATA #REQUIRED > default CDATA #IMPLIED "" > required (true|false) #IMPLIED "false" > > > > > > And an example > > <?xml version="1.0" encoding="ISO-8859-1"?> > <!DOCTYPE properties SYSTEM "properties.dtd"> > <properties> > <property name="maven.aspectj.debug" default="false"> > If true, run in debug mode > </property> > </properties> > > > What do you think? > > > Regards > > Carlos Sanchez > A Coruņa, Spain > > Oness Project > http://oness.sourceforge.net > > > > > --------------------------------------------------------------------- > 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]
