Finally got around to catching up with the guy who reported this problem to me originally - they were running 2.0-beta-8 which I think was fixed in the master pom - adding a dependency block to use 2.0 solved the problems.. Looks like at some point they had their subversion server updated. I was running the same plugin version, but our subversion server is still 1.4.x so we never encountered the problems.
Mark -- Pull me down under... On Fri, Apr 30, 2010 at 1:32 AM, Tim O'Brien <tobr...@discursive.com> wrote: > What version of the release plugin are you using? >
