I was interested in the jira report, but the docs for that plugin are 
still empty (no goals, no properties documented).

I guess there must be some properties to map the project to a jira 
project (and maybe specify a version)?

I think this is a bit sad, maven itself being such a good tool to 
facilitate generating and deploying a site, and then a new feature 
(mentioned in the release notes) is just not documented at all...

I think maven is way beyond the stage that users have to go into the 
sources to find which properties are needed to run a certain plugin...

Any possibility to enforce or support a certain documentation standard 
for plugins, and make sure the site is up-to-date when a release takes 
place?

I just think these little things are the ones that make users 
frustrated...



Oliver


P.S.
Running "maven maven-jira-plugin:report" without specifying anything 
gives:

BUILD FAILED
File...... 
file:/C:/Programme/_dev/maven-1.0-rc2/plugins_unpacked/maven-jira-plugin-1.0/plugin.jelly
Element... jira:jira
Line...... 57
Column.... 9
String index out of range: -3
Total time: 5 seconds
Finished at: Fri Mar 26 10:31:55 CET 2004


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

Reply via email to