There is a simple workaround for this which works like so:
- Run mvn release:prepare
- After if fails run svn update
- Run mvn release:prepare again
- Success!
Aaron Zeckoski is a technology leader recognized for his expertise in educational technologies and learning systems. He has been an open source architect working on learning systems projects like Sakai. This is a technical blog about software engineering, servant leadership, and whatever else.
Delivered-To: azeckoski@gmail.com
Received: by 10.151.102.11 with SMTP id e11cs256039ybm;
Tue, 22 Jul 2008 11:02:35 -0700 (PDT)
Received: by 10.100.205.13 with SMTP id c13mr2655883ang.47.1216749755360;
Tue, 22 Jul 2008 11:02:35 -0700 (PDT)
Received: from mail2.stellaronecorp.com (mail2.stellarone.com [64.203.182.58])
by mx.google.com with ESMTP id c40si8810491anc.30.2008.07.22.11.02.34;
Tue, 22 Jul 2008 11:02:35 -0700 (PDT)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C8EC25.00DD8ED8"
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-OriginalArrivalTime: 22 Jul 2008 18:01:01.0106 (UTC) FILETIME=[E68D5920:01C8EC24]
Subject: Transfer
Date: Tue, 22 Jul 2008 14:01:45 -0400
Message-ID: <7925a85885c9454897dba459745e840d5aa877@west-exch1.stellaronecorp.com>
To: azechoski@gmail.com