Brett Porter wrote:
> 
> On 17/04/2009, at 4:10 AM, Dennis Lundberg wrote:
> 
>> Brett Porter wrote:
>>> You might need to report it to the infrastructure team.
>>>
>>> However, since release:prepare picks up where it leaves off, if you
>>> don't start over (keep release.properties) and run release:prepare
>>> again, you should find that the tag is created successfully after a
>>> period in between.
>>
>> Yes, that is correct.
>>
>> I have a bunch of stuff checked out from the eu svn mirror. When I do a
>> release against that server, it usually fails the first time. Running
>> the same command again (mvn release:prepare) will pick up and finish the
>> job successfully.
> 
> Benjamin had the problem too (or something similar). It is due to the
> geo-ip as Brian mentioned.

No, I had these problems before the geo-ip thingy was introduced. I
think it happens because the svn sync between the EU mirror and the main
svn server takes too long to complete.

This happens if the svn server you are using (during a release) is a
mirror. The geo-ip solution has only meant that more people have,
unknowingly, started to use the EU mirror.

Perhaps we can introduce an option to wait for x seconds between the svn
actions in the release plugin?

> I mentioned it to the infra team and they
> asked that someone who was experiencing it could talk to them next time
> it happens o they could try working through it with them. Would someone
> in Europe that sees this error mind filing an issue with infra along the
> lines of "commit and subsequent remote tag using the committed revision,
> such as the maven release plugin does, fails using european svn mirror"?
> 
> Thanks,
> Brett
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 


-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to