From 8ea14ba594e1df2a083f28459f5cc5af808e4df1 Mon Sep 17 00:00:00 2001 From: ltheussl Date: Thu, 12 Jan 2006 23:54:06 +0000 Subject: [PATCH] Update docs git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@368519 13f79535-47bb-0310-9956-ffa450edef68 --- jira/xdocs/faq.fml | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/jira/xdocs/faq.fml b/jira/xdocs/faq.fml index 9418f347..6458dff2 100644 --- a/jira/xdocs/faq.fml +++ b/jira/xdocs/faq.fml @@ -28,12 +28,19 @@

- 1. modify/double check that your project.xml has issue tracking url in the following format : + 1. The jira plugin needs the jira id number of your project to work. Preferably, + your project.xml should have an <issueTrackingUrl> in the following format :

<issueTrackingUrl>[JIRA URL]/BrowseProject.jspa?id=[JIRA PROJECT ID]</issueTrackingUrl>

Example :

<issueTrackingUrl>http://jira.codehaus.org/secure/BrowseProject.jspa?id=10450</issueTrackingUrl> - +

+ If no id is found in <issueTrackingUrl>, like eg, in +

+ <issueTrackingUrl>http://jira.codehaus.org/browse/MPJIRA</issueTrackingUrl> +

+ an attempt is made to extract the id from the jira project page, but this is not guaranteed to work. +

2. Determine the credentials to log into the webserver, if any. The plugin supports basic authentication (and SSL). Add the credentials to the project.properties, as maven.jira.webUser and maven.jira.webPassword