shillner / unleash-scm-provider-svn Goto Github PK

Implementation of the history features of API version 1.2.0

Reported as shillner/unleash-maven-plugin#64:

After starting a release on a multi module Maven project the SCM connection and url tag are not the expected ones (sub modules).

Example:
Trunk:
scm:svn:svn://.../sample-project/trunk/core
After Release:
scm:svn:svn://.../sample-project/tags/1.0.0
The right one should be:
scm:svn:svn://.../sample-project/tags/1.0.0/core

A crash of the JVM happened caused by libc.so:

• installed SVN 1.8 with some kind of credentials caching
• library checks out with 1.7
• crash happens when trying to commit changes

SVNKit seems to use JNA for credentials cache access. The following system property flag can prevent SVNKit from using JNA:
-Dsvnkit.useJNA=false

So what is the real cause for this error?
Found some similar errors:
https://bugs.openjdk.java.net/browse/JDK-8129839
http://stackoverflow.com/questions/39342816/jre-getting-crashed-when-using-svnkit-inside-a-web-app-on-tomcat-server

Deleted files and folders of a checked-out repository are not handled. Instead, the provider ignores them and finishes with a message that there was nothing to commit.

The current implementation needs some refactorings and cleanups since most things are concentrated in the provider's main class.

• extract parameterized log statements, eventually to the API for uniform logging
• extract helpers
• implement test cases