while you are waiting for real documentation to show up here is what i did to get JIRA 
report going:

1. modify/double check that your project.xml has issue tracking url in the following 
format
  <issueTrackingUrl><jira url>/BrowseProject.jspa?id=<JIRA PROJECT 
ID></issueTrackingUrl>
 
example:

  
<issueTrackingUrl>http://igc-dev1.intgas.com/jira-extweb/BrowseProject.jspa?id=10001</issueTrackingUrl>

2. make sure that your project allows group Anyone to view jira issues 
(you may or may not need to also set your jira installation type to public - this is 
in General Configuration under administration)

3. log out of jira (if you are using Remember me feature) and test your setup by going 
to url like this one:

http://igc-dev1.intgas.com/jira-extweb/secure/IssueNavigator.jspa?view=rss&pid=10001&sorter/field=issuekey&sorter/order=DESC&sorter/field=status&sorter/order=DESC&tempMax=1000&reset=true

replace igc-dev1.intgas.com/jira-extweb with your jira installation
and pid with your project pid

4. add this to your project.xml  in reports section (i gues this is really step 1 ;-)
    <report>maven-jira-plugin</report>    
5. run site:generate and you should have jira.html in your <PROJECT>/target/docs 
directory

i hope this helps

thanks
vlad

>>> [EMAIL PROTECTED] 03/26/04 02:48AM >>>
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] 



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

Reply via email to