maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Clark (JIRA)" <>
Subject [jira] Created: (SCM-452) scm url not being parsed correctly for release:perform only
Date Fri, 27 Mar 2009 23:21:12 GMT
scm url not being parsed correctly for release:perform only

                 Key: SCM-452
             Project: Maven SCM
          Issue Type: Bug
          Components: maven-scm-provider-cvs
    Affects Versions: 2.0
         Environment: reproduced on Windows Vista ultimate 32bit, w/ Sun jdk 1.5.0_17, ubuntu
2.6.27-11-generic, with openjdk 1.6 (result of apt-get install maven2).  Also happens in a
windows eclipse workspace w/ m2eclipse, project checked out as maven project with from a repository
location defined with ext protocol (not extssh)
            Reporter: Ben Clark

mvn release:perform
works, except it won't really do what we need without a lot of manual intervention, because
this command:
mvn release:prepare

yields this error:
[INFO] ------------------------------------------------------------------------
[INFO] The scm url is invalid.
  - The connection string contains too few tokens.
[INFO] ------------------------------------------------------------------------

-e doesn't reveal a long enough stack trace to show anything.  It would be helpful if this
error could say what url it's parsing
the scm section of the pom is this:

We don't intend to put the user name in the pom (shared resource) which is part of why I'm
trying to override it.

and the servers section of settings.xml is like so:

but in any case I'm not sure it's even reading the scm section of the pom correctly.  After
downloading the plugin sources, one of the few unresolved items was the Xpp3Reader which might
have told me the answer.  This is not up to my experience of a high bar set by working with
this plugin in a subversion environment, but maybe it's an unfair comparison.

Any attention greatly appreciated

--Ben Clark

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message