Some valid scm urls are not allowed by this plugin

Unfortunately this testcase is not complete. The class ChangeLog that I am trying to test is really hard to test because of its private methods. I am trying to test the method createFactory() but cannot access it directly as it is private.

Anyway, put this test file into a fresh checkout and run it. This will throw exceptions, because I have not managed to set up a correct environment to run the complete doExecute method in.

You will see that there are warnings for two of the tree tests, claiming that there is something wrong with the scm connections. The upcoming patch will fix both of these warnings.

This patch fixes the issues higlighted by the previous testcase. After this patch has been applied there should no long be any warnings when the previous testcase is run.

Are you sure this is a valid connection string (from RepositoryTest.java):

scm:cvs|pserver|anoncvs@cvs.apache.org|/home/cvspublic|module

Shouldn't the separator be set to the character after the 'scm'?

That is a valid question. At the moment it does not have to be the same.
I ran this set of commands:
mvn scm:validate -DconnectionUrl="scm:cvs:pserver:anoncvs@cvs.apache.org:/home/cvspublic:module"
mvn scm:validate -DconnectionUrl="scm:cvs|pserver|anoncvs@cvs.apache.org|/home/cvspublic|module"
mvn scm:validate -DconnectionUrl="scm|cvs|pserver|anoncvs@cvs.apache.org|/home/cvspublic|module"

Using maven-scm-alpha-2 (couldn't find alpha-1 anywhere) produced these results:
VALID
VALID
INVALID

Using maven-scm-beta-3-SNAPSHOT produced these results:
VALID
VALID
VALID

As you can see this is consistent with what is in RepositoryTest. In both versions a url starting with "scm:" can use "|" as separator.

The only difference is in the third case, which I indicated is something that is coming in the next version of maven-scm.

Updated version of the test case that illuminates the problem. This is not to be checked in since it throws exceptions. When you run it you will receive one warning. That warning will disappear when the updated version of the patch is applied.

Updated version of the patch. This patch affects a more files than the previous one. I had to tweak a few tests to successfully run "maven test".

There is one part of the code in RepositoryUtils.splitSCMConnection() that is not very pretty, but it get's the job done. I've added a comment in the code to explain what is going on there.

Patch applied. Thanks!
For the record: we agreed on the scm-dev list that the format for a valid scm url should be scm:<provider><delimiter><provider-parameters>, ie it has to start with 'scm:', but <delimiter> can be either ':' or '|'.