Michal Maczka wrote:


I think we should go step further and get rid of plugin.properties file...
in favour of metadata file. It can look like:
[snip]
BTW: We anyway need plugin metadata file which can be used by IDEs.

Agree 100%.


We also need it for documentation. Its quite common for people to ask 'what property do I set to do....' because there are so many undocumented properties. If there was a metadata file that described plugin properties, it could be used to generate the xdocs.

However it isn't just plugins that need this - normal projects use additional properties to configure things in their maven.xml. So properties should appear as a standard report.

-Baz




Privacy and Confidentiality Notice


------------------------------------------------

The information contained in this E-Mail message is intended only for the person or persons to whom it is addressed. Such information is confidential and privileged and no mistake in transmission is intended to waive or compromise such privilege. If you have received it in error, please destroy it and notify us on the telephone number printed above. If you do not receive complete and legible copies, please telephone us immediately. Any opinions expressed herein including attachments are those of the author only. i-documentsystems Ltd. does not accept responsibility for the accuracy or completeness of the information provided or for any changes to this Email, however made, after it was sent. (Please note that it is your responsibility to scan this message for viruses).


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to