maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brad Szabo (JIRA)" <>
Subject [jira] Commented: (MCHANGELOG-47) Cannot find .cvspass file. Documentation not up-to-date.
Date Fri, 15 Sep 2006 22:05:11 GMT
    [ ] 
Brad Szabo commented on MCHANGELOG-47:

I take that back, you cannot just create an empty .cvspass file in your home directory to
gain anonymous access, but if you actually connect to that CVS server and login, it will create
an anonymous entry that should enable the plugin to work.
cvs -d login

> Cannot find .cvspass file.  Documentation not up-to-date.
> ---------------------------------------------------------
>                 Key: MCHANGELOG-47
>                 URL:
>             Project: Maven 2.x Changelog Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-1
>         Environment: Maven2 on Windows in Eclipse with CVS (anonymous pserver)
> Maven2 on GenToo in CruiseControl with CVS (anonymous pserver)
>            Reporter: Paul R. Saxman
> I've run into a few issues while using this plugin, which are as follows:
> - When I try to run the Maven 2 changelog plugin in Eclipse or using CruiseControl, I
get an error that the file .cvspass cannot be found.
> - I've found a reference to the .cvspass file on the Maven 1 plugin documentation, but
not in the Maven 2 documentation.
> - The Maven 2 documentation specifies to use the groupId org.apache.maven.plugins for
the plugin, which doesn't exist on ibiblio.  The plugin actually exists at org.codehaus.mojo;
HOWEVER, it is not documented as being part of Mojo at
> - When I follow the Maven 1 instructions to generate the .cvspass file, I get the error
"The plugin 'org.apache.maven.plugins:maven-changelog-plugin' does not exist or no valid version
could be found".
> - Passing in a password (which doesn't really exist since I'm using an anonymous pserver)
using the Maven 2 plugin "password" parameter has no effect, which is consistent with the
documentation.  Is there any way to not bother with a password or to specify an empty password?

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