[jira] Created: (MAVENUPLOAD-654) please upload retrotranslator jars for 0.9.5

2005-12-29 Thread james strachan (JIRA)
please upload retrotranslator jars for 0.9.5 Key: MAVENUPLOAD-654 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-654 Project: maven-upload-requests Type: Task Reporter: james strachan Attachments: retrotranslator

[jira] Created: (CONTINUUM-430) build failure emails should ideally include a URL link so we can click on the failed build and see the details

2005-11-09 Thread james strachan (JIRA)
/CONTINUUM-430 Project: Continuum Type: Improvement Reporter: james strachan We've got lots of CI installs on different boxes and different projects; it'd be nice to be able to click on the URL on a first line to take us to the detail of the build rather than having t

Re: generating changes.xml from JIRA

2003-11-26 Thread James Strachan
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 o

generating changes.xml from JIRA

2003-11-25 Thread James Strachan
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 like changes.xml) - as I

Re: cvs lock in maven-plugins?

2003-09-30 Thread James Strachan
I've got the same problem. maven-plugins is a new CVS module - I'm wondering if we've got the necessary karma to access it? On Tuesday, September 30, 2003, at 12:04 pm, Vincent Massol wrote: Hi, I'm trying to update my local copy of the maven-plugins CVS module but it fails with a lock problem

Re: cvs commit: maven/src/plugins-build/faq plugin.jelly

2003-03-19 Thread James Strachan
From: <[EMAIL PROTECTED]> > This will have no runtime effect, right? Since Maven's lib directory has > an older version of maven, that will be loaded and used first. > > Or am I missing something? The new Jelly version only comes into effect if you do a full rebuild of Maven which then copies