James Strachan wrote:
On 26 Nov 2003, at 08:39, Nicola Ken Barozzi wrote:
...
Look in Forrest, we are doing just that since some time now.
http://xml.apache.org/forrest/forrest-issues.html
If you want to grab the stylesheet, go ahead, it's Apache-licensed ;-)
I took a quick look at the page - and m
On 26 Nov 2003, at 08:39, Nicola Ken Barozzi wrote:
James Strachan wrote:
On all the OS projects I work (actually on the commercial ones too :)
I'd like to do all change management & issue tracking on JIRA. I like
the changes.xml report in Maven as well; I wonder has anyone figured
out how to
James Strachan wrote:
On all the OS projects I work (actually on the commercial ones too :)
I'd like to do all change management & issue tracking on JIRA. I like
the changes.xml report in Maven as well; I wonder has anyone figured out
how to get JIRA to generate this report (i.e. something lik
Yes but how do you get the map of fixfor ids?
Thanks
-Vincent
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 26 November 2003 09:07
> To: Maven Developers List
> Subject: RE: generating changes.xml from JIRA
>
> Jira has an x
Jira has an xml format that can be accessed via URL, e.g.
http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10030&fixfor=10245&resolutionIds=-1&sorter/field=priority&sorter/order=DESC&tempMax=25&reset=true
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/pe
Hi James,
I was looking into this too! However, I don't know how to get the
information from JIRA (apart from writing our own Jelly script that is
run inside JIRA). I looked into the JIRA forums briefly and couldn't
find an answer. Maybe we should post a question? I fear the answer is
jelly which
Hi James,
I've been thinking about this a while since dion originally suggested it. As
far as we have gotten was Vincent adding in an issue number to the changes
report.
I guess the next step is to take the versions specified and suck any issues
out of JIRA's XML that are "fixed for" that version
