maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (WAGON-50) Add CVS support to Wagon SCM for site:deploy
Date Wed, 14 May 2008 08:04:28 GMT

     [ http://jira.codehaus.org/browse/WAGON-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter updated WAGON-50:
------------------------------

    Fix Version/s: 1.x

> Add CVS support to Wagon SCM for site:deploy
> --------------------------------------------
>
>                 Key: WAGON-50
>                 URL: http://jira.codehaus.org/browse/WAGON-50
>             Project: Maven Wagon
>          Issue Type: New Feature
>          Components: wagon-scm
>    Affects Versions: 1.0-beta-1
>            Reporter: Kohsuke Kawaguchi
>             Fix For: 1.x
>
>
> wagon-scm + site:deploy + CVS repository combo doesn't work.
> The first problem is that it tries to execute ScmWagon.mkdirs(), in which it runs:
>                 listScmResult = scmProvider.list( baseRepository, fileSet, false, null
);
> This is not supported in CVS, so it fails. I'm not sure what the proper fix would be,
but I worked around this by
> creating the module in the repository by manually doing "cvs add <directory>",
and then changed the above line to:
>             try {
>                     listScmResult = scmProvider.list( baseRepository, fileSet, false,
null );
>             } catch (NoSuchCommandScmException e) {
>                 break; // assume it's already there
>             }
> With this workaround, it then fails at the following line:
>                 relativePath = repository.getProviderRepository().getRelativePath( baseProviderRepository
);
> as this method is not implemented in CvsScmProviderRepository
> (I have no idea what this method does, but this method only seems to be implemented in
SvnScmProviderRepository.)
> Again I worked around this by changing this to:
>             String relativePath = null;
>             try {
>                 relativePath = repository.getProviderRepository().getRelativePath( baseProviderRepository
);
>             } catch (UnsupportedOperationException e) {
>                 // HACK
>             }
> which seems to make it work.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message