Worked it out.
Eclipse 3 or the mevenide plugin in eclipse 3 is holding a lock on project.xml.
The plugin merrily goes on its way when the copy back fails AFAICT.
On Fri, 9 Jul 2004 09:56:37 +1000, Dion Gillard <[EMAIL PROTECTED]> wrote:
> Not yetits as annoying as all hell.
>
> I'll try t
Not yetits as annoying as all hell.
I'll try to work it out next time I do a release.
On Fri, 9 Jul 2004 09:30:38 +1000, Brett Porter <[EMAIL PROTECTED]> wrote:
> Have you narrowed down the problem. I use this all the time on Maven and at work
> and it never fails...
>
> - Brett
>
>
>
>
On Thu, 8 Jul 2004 16:22:40 +0200, Vincent Massol <[EMAIL PROTECTED]> wrote:
> Hi dIon,
>
> Just a question: when you do some changes like this, are you also making the
> equivalent change in JIRA?
Not usually.
> I've found that lots of people make change to versions in project.xml but
> JIRA is
Have you narrowed down the problem. I use this all the time on Maven and at work
and it never fails...
- Brett
Quoting [EMAIL PROTECTED]:
> dion2004/07/08 07:38:57
>
> Modified:plugin project.xml
> Log:
> scm:prepare-release fails again
>
> Revision ChangesPath
>
Changing JIRA is very labour intensive. We should be more diligent (myself in
particular).
I think bob said he could enable SOAP on localhost, so if we wanted to add a
function to the JIRA plugin and do the releases from codehaus we could automate
it. This might be a good idea anyway - we could se
For future reference, you can just do this at the point of release.
- Brett
Quoting [EMAIL PROTECTED]:
> dion2004/07/08 07:12:16
>
> Modified:plugin/xdocs changes.xml
>plugin project.xml
> Log:
> Use 1.5.1 instead of 1.6
>
> Revision ChangesPath
>
Hi dIon,
Just a question: when you do some changes like this, are you also making the
equivalent change in JIRA?
I've found that lots of people make change to versions in project.xml but
JIRA is often neglected. Like for example when a plugin is released.
Thanks
-Vincent
> -Original Message
