[maven-bug] Created: (MAVEN-305) changelog plug-in cannot parse non-pserver remote cvs repository connections

[bo...@werken.com]

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-305


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-305
    Summary: changelog plug-in cannot parse non-pserver remote cvs repository connections
       Type: Bug

     Status: Assigned
   Priority: Minor

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: maven
  Component: None
   Versions:
             1.0-beta-8

   Assignee: Jason van Zyl
   Reporter: robert burrell donkin

    Created: Fri, 28 Feb 2003 5:58 PM
    Updated: Fri, 28 Feb 2003 5:58 PM
Environment: macOS X 
using ssh-agent and public key to connect to cvs.apache.org

Description:
when running site:generate the CVS/root file is overwritten with the repository setting from maven. 

this is a PITA since this means i have to edit this file and replace :pserver:anoncvs@... with rdonkin@... every time i want to use cvs after running site:generate. the obvious solution seemed (to me) to use rdonkin@... in the repository setting in the project.xml (well alright - i used a variable which i could set to :pserver:anoncvs@... in the project.properties files and then override in the build.xml).

anyway, the only problem with this plan was that the repository scm parser in the changelog plug-in can only parse pserver remote cvs repository connections.

i've created a patch which allows non-pserver remote repository descriptions to be parsed together with a patch for the test case.

an example of the type of connection which will work with this patch is:
    <connection>scm:cvs:rdonkin@cvs.apache.org:/home/cvs:jakarta-commons</connection>






---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.werken.com/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira