SVN repository error

In the process of creating a maven release for OpenPatrician the SVN repository got currupted. Though I have no idea how. There were two different error messages:

svn: Checksum mismatch for ‚.svn/text-base/blah.ext‘;
expected: ‚f8d45250f7df5561635854165862fdd8‘,
actual: ‚644f85c4befa671150c5c6ec5fad9885‘

svn: Reading one svndiff window read beyond the end of the representation

The one side which had something to say about this was Andrew Hedges blog. As a result I checkout the version previous to the corruption, commited all the changes to a new revision save the corrupt file. Then I checked the pom.xml which apparently was corrupt in the repository. There I saw that the file was empty. Seems that svn commits do not really follow ACID. I deleted the file in the repo and forced the commit from my workspace, which worked.

Publishing Artifact to maven repository

Since some time I set up new Java projects with Maven. Additionally I migrated some old ones to Maven. The main issue was dependency handling and building. No more manual writting/copying of Ant build.xml’s. This works well as long you need libraries/artefacts that can be found in maven repository and/or the ones not available are your own. In the latter case they reside in your local repository and are accessible by other projects. Up until now this worked well since such dependencies only existed inside one project and could be resolved. However in the OpenSource world there comes a time where this is no longer possible. This happened, when I wanted to use ch.sahits.sahitsUtils in my game project OpenPatrician. The logical conclusion was to publish the artefact to a maven repository. This however proved a little more difficult. „Publishing Artifact to maven repository“ weiterlesen